How to make a VST plugin without coding

Making a plugin used to mean C++, a framework, and a few months. That is no longer the only route, but the alternatives are not equivalent, and the differences show up later — usually at the point where you want to sell the thing or change it.

Four routes exist. Here is what each one actually costs.

1. A visual DSP environment

Tools in this family let you build the signal path as a graph — oscillators, filters, envelopes wired together — and export the result as a plugin. They are genuinely powerful, and the ceiling is high: people ship commercial products built this way.

The cost is the learning curve, and it is front-loaded. You are not writing C++, but you are still doing DSP: you need to know why a one-pole filter is not the same as a biquad, what happens when a delay line reads a fractional index, and why your reverb rings at one particular frequency. The first working plugin is days away, not minutes.

Worth it if you intend to keep making plugins. Expensive if you have one idea and want to hear it.

2. Describe it and have the DSP written for you

The newest route: you describe the effect in plain language, and the tool writes the DSP, compiles it, and hands you something you can hear. This is what Sonorie does — you type “a vintage tape echo that darkens as it repeats” and about a minute later you are turning its knobs in the browser.

The honest limits: it is bounded by what the generator can express, so a conventional effect goes better than an idea nobody has built before, and a request that is really a research project comes back as a plausible approximation rather than the thing you imagined. It is very good at the large middle — delays, reverbs, compressors, filters, saturation, choruses, simple synths — which is most of what most people want.

The thing to check is what you keep. Ask whether you get the source, whether the export drags a third-party framework licence along with it, and whether you may sell the result.

3. Pay a developer

No ceiling and no learning curve, but a real budget and a real calendar: weeks for something modest, and every change is another round trip. It makes sense when the plugin is a product you have already validated, not when you are still finding out whether the idea is any good.

4. Wrap presets around something that exists

Not building a plugin at all, but it is how a lot of products ship: a curated preset library, a skin, a name. Perfectly legitimate, and constrained to what the host plugin can already do.

What separates a real plugin from a toy

Whichever route you take, the same four things decide whether the result is real.

• It loads in a DAW. Not a web demo — a compiled VST3, AU, CLAP or LV2 that a host scans and opens.
• It passes the validators.pluginval and clap-validator for VST3 and CLAP, Apple’s auval for Audio Units. These check the parts nobody thinks about until they break: state save and reload, parameter automation, silence handling, odd sample rates and buffer sizes.
• It behaves on the audio thread.No allocation, no locks, no file access inside the process callback. Get this wrong and it works on your machine and clicks on somebody else’s.
• Its state survives. Close the session, reopen it, and every control is where you left it.

How Sonorie does it

You describe an effect or an instrument. A model writes C++ against an in-house DSP toolkit, and that source is compiled twice: to WebAssembly, which is what you hear while you work, and to native binaries when you export. Because both come from the same source, what you hear in the browser is the plugin, not a preview of it.

Before you hear anything, the compiled result is measured — response, harmonics, latency, loudness, aliasing — and rejected if it allocates on the audio thread or does not do what it claimed. The export produces VST3, AU, CLAP, LV2 and a standalone application for Windows, macOS and Linux, along with the full source project, and you can sell what you make.

If you want the underlying comparison in more depth, there is a companion piece on what chat-built plugins have in common with chat-built websites, and one on which plugin formats you actually need.