The most common question about browser DAWs: can I use my plugins? The honest answer is "not directly, and here's why."
A VST or AU plugin is compiled native code — machine instructions for a specific processor and operating system. It expects to be loaded into a host application's memory, call operating system functions, and open its own window.
Browsers deliberately prevent all of that. The entire security model of the web rests on the assumption that visiting a page cannot execute arbitrary native code on your machine. Loading a VST would require breaking that, and no browser vendor will.
This isn't a limitation that gets fixed with a better browser. It's a design boundary.
If a plugin maker has the source code, the audio processing can be compiled to WebAssembly and run in the browser at near-native speed. The interface gets rebuilt in web technologies.
This produces genuinely equivalent audio — same algorithms, same quality. It requires the developer to do the work, so it applies to the browser DAW's own instruments and effects, not your existing collection.
A small companion application runs on your machine, hosts your installed plugins natively, and streams audio and control data to and from the browser. Your plugins run where they always did; the browser drives them.
This is how browser DAWs that support third-party plugins generally do it. Veena supports hosting your own VST and AU plugins this way, which matters if you have a collection you depend on.
Tradeoff: it adds latency and requires the companion app, so it's not the zero-install experience the browser otherwise offers.
Emerging standards aim to define plugins built for the web from the start — sandboxed, portable, no install. Promising, but the ecosystem is small compared with thirty years of VST development.
Built-in instruments and effects compiled from the same class of DSP code as desktop plugins. In practice, a modern browser DAW's stock EQ, compressor, and reverb are comparable to a desktop DAW's stock plugins — the difference is catalogue breadth, not quality per unit.
If your workflow depends on specific plugins — a particular saturation unit, a specific orchestral library — a browser DAW alone won't replace your setup, and a bridge adds complexity.
If you work mostly with stock plugins, or you want to produce on a machine where you can't install anything, the built-in tooling is genuinely sufficient.
Related reading: WebAssembly in browser DAWs, browser vs installed music software, and the Web Audio API explained.
Start making music in Veena
Free, browser-based, no downloads required.
Try Veena Free