ClipCraft Bridge: Use Your Real VST3 Plugins in an Online DAW

You can use VST plugins online now. The actual VST3 instruments and effects installed on your computer, Omnisphere, Massive X, Kontakt, Auto-Tune Pro, playing inside a browser DAW. The trick is a free Windows companion app called the ClipCraft Bridge: a roughly 5 MB installer that hosts your plugins locally and feeds their audio into SoundCraft, our free browser audio editor. This post explains how the whole thing works, what it does with instruments versus effects, and the limits you should know before you install anything.

Why browser DAWs can't normally load plugins

A VST3 plugin is native code, a compiled .vst3 file sitting in your Program Files folder. Browsers are sandboxed on purpose and can't execute that, which is why every online DAW before now shipped its own built-in synths and nothing else. Your plugin folder might hold thousands of dollars of instruments, and a browser tab can't see any of it.

The Bridge gets around this without breaking the sandbox. It's a small native app that sits in your Windows system tray and hosts the plugins itself, on your machine. SoundCraft talks to it over a local WebSocket on 127.0.0.1:41890, which never leaves your computer. The Bridge also checks that connections come from clipcraft.ai (or localhost), so a random website can't reach your plugins. Nothing uploads. Your plugins, sample libraries and licenses stay where they are.

How to use VST plugins online with the Bridge

1. Grab the installer from clipcraft.ai/bridge. It's free and there's no separate account for it.
2. Run it. The Bridge starts with Windows and lives in the tray; on first launch it scans the standard VST3 folder and builds a list of everything you own.
3. Sign up for ClipCraftif you haven't, open SoundCraft, then open the ☰ rack and click the Plugins tab. Your instruments show up as cards under a green Bridge connected badge. Click one and it becomes a channel.

Instrument channels: play Omnisphere from a browser tab

With the Bridge running, a plugin instrument behaves like SoundCraft's built-in ones. You get a channel, you draw MIDI notes in the piano roll (or play them in from a hardware keyboard, which the Bridge passes straight through to the plugin), and the notes render through the real plugin on your machine. Renders happen offline and get cached, so playback is just scheduled audio. In practice it's quick: a short Massive X clip renders in around 140 milliseconds on our test machine, and re-renders kick off about 300 ms after you stop editing notes.

The plugin's own window opens on your desktop too. Click Open plugin and you get the actual Omnisphere browser, audibly, so you can flip through patches and hear each one before you commit. Close the window and SoundCraft pulls the new state and re-renders your clips with it. While the window is open, the editor polls the plugin every 3 seconds, so preset tweaks flow into your project almost as you make them.

Exports are covered as well. WAV and MP3 mixdowns wait for every plugin render to finish before bouncing, so the track you post or download always includes your plugin audio, never a half-rendered placeholder. For a full session walkthrough with Omnisphere, Massive X and Auto-Tune Pro, the companion Bridge post goes further.

That screenshot shows the honest starting point: the Plugins tab with the Bridge not yet running. The download button and setup guide live right there in the editor, and once the app is installed the card swaps for your scanned plugin list.

Effects: bounce a clip through Auto-Tune Pro

Instruments were the first half. Effect plugins work in two ways, and both were verified against real iLok-licensed Antares plugins.

• One-shot processing: right-click any audio clip and pick Process with plugin. A modal lists your effect plugins; choose one and its native window opens. Apply bounces the clip through the plugin and swaps the audio in place (undoable). Analyze streams the clip through without changing it, which is how Auto-Key listens to a song and names its key.
• Persistent chain entries: a bridge effect can also sit in a channel's effects rack like a built-in, with an enable toggle and an Open plugin button. The channel's clips render through the chain, and tweaks you make in the plugin window re-process the audio near-live.

The latency story is worth a sentence. Processing is offline rendering, not real-time monitoring, so you can't yet sing through Auto-Tune live while recording. That's on the roadmap. What you get today is the studio workflow: record dry, then process the take through the real plugin.

Your project remembers the plugin state

This is the detail that makes the Bridge usable for real work. When you save a SoundCraft project, the editor pulls each plugin's full state (the same blob the plugin would save in any desktop DAW, typically 40 to 600 KB) and stores it inside the project. Close everything, come back a week later, reopen the song, and the Bridge reloads each plugin with its exact saved state. Same patch, same sound. iLok-protected plugins work here too, since licensing happens on your machine where the license already lives.

If you haven't spent time in SoundCraft itself, the free online DAW overview covers the editor the Bridge plugs into: the multi-track timeline, the 15 built-in effects, automation, and posting finished tracks.

The honest limitations

• Windows only, for now. There's no macOS build yet.
• VST3 only. This one isn't our call: Steinberg closed VST2 licensing years ago, so no new host can legally support it. If a plugin ships both formats, install the VST3.
• Plugin CPU is your CPU. The browser isn't doing the synthesis, your machine is, so a heavy Omnisphere patch costs the same locally as it would in any DAW. Spectrasonics engines also want a warm-up (about 10 seconds after loading) and the Bridge allows one Spectrasonics instance at a time.
• No live low-latency monitoring yet, and no CLAP support yet.
• The pricing wording is free for a limited time. It costs nothing today on every plan, including Free, and current plan pricing is on the pricing page if you want the storage and token tiers around it.

I'd call the Bridge the single biggest reason to pick SoundCraft over other browser DAWs. Built-in browser synths are fine for sketches, but if you already own Omnisphere or Auto-Tune, working without them never stops hurting. A 5 MB tray app is a small price for getting them back. Create a free account, install the Bridge from the download page, and your plugin folder shows up in a browser tab.