Plug'n Script tutorial

So, it’s a tool to prototype and develop audio or MIDI plugins in various formats (VST2, VST3, AU, AAX, or standalone apps).

How are such plugins usually developed?

As of 2025, most developers use frameworks like JUCE or iPlug2. Alternatively, you can download the VST3 SDK from Steinberg directly (VST2 has been deprecated since 2018) and build plugins using Visual Studio (Windows) or Xcode (Mac). For AudioUnits (AU) or Avid Audio eXtension (AAX), original SDKs are available from Apple and Avid.

However, creating a plugin that targets all these formats and platforms is complex and time-consuming, even for experienced C++ developers. That’s why most developers rely on frameworks like JUCE or iPlug, which let you focus on the plugin’s functionality while producing multiple formats with much less effort.

Still, C++ knowledge is required. Without it, building even a simple plugin and understanding the process can be challenging. GUI design can also take more time than the DSP part.

Additionally, JUCE can be costly. Free use requires your plugin to be open-source or to display the JUCE splash screen, and plugins may send analytics data to JUCE servers. These licensing policies can motivate developers to look for alternatives.

Is there something less complicated?

Yes. You can try some of the software mentioned in this KVR post. Some tools let you learn DSP by building a synth or plugin from “blocks.” For example, RackAFX by Will Pirkle can help you learn plugin development. Other tools and frameworks exist, but they may be outdated, less popular, or still in development. Spend some time experimenting to see what works for you.

I just want to make a normal plugin!

If you want to create a VST (VST3, AU, AAX) audio or MIDI plugin with a good-looking GUI and start quickly, Plug’n Script by Blue Cat Audio is a great option—especially if C++ feels too complicated to start with.