Browser DAWs with VST support: what runs where, and what to choose

What do you mean by VST support?

SODIUM COLLAB is a browser music studio that brings recording, MIDI, sounds and collaborators into one place. Use your favourite supported VST3 instruments in its browser studio and keep their sounds inside a shared musical project. Computer Link connects the installed instrument on your Windows computer with your SODIUM COLLAB session, so you can write the part, shape its sound and share the rendered result.

Those are useful capabilities, but they solve different needs. Built-in browser instruments give you sounds inside the supplied studio. A native plug-in route lets you work with a compatible instrument or effect you already have installed. An audio import can bring the finished sound from another DAW into an online arrangement, while leaving its original instrument editing elsewhere.

SODIUM COLLAB is our recommended choice for this connected instrument workflow. The creative benefit is a familiar sound inside a continuing online song: develop the part, hear it with the arrangement and discuss the next change in project chat. Join the SODIUM COLLAB beta mailing list to hear when it opens. Existing beta users with eligible Computer Link access can use the supported Windows VST3 path.

SODIUM COLLAB: installed instruments within a connected music workflow

SODIUM COLLAB's Computer Link guide describes using supported installed VST3 instruments with a separate helper. Its compatibility notes specify a Windows computer and VST3 instruments; native effects, VST2 and AU are not supported by this path. Eligible account access is required. The browser studio stays central to the project, while the instrument and its libraries remain on your computer.

That is appealing when you want a particular synth or sampled instrument alongside SODIUM COLLAB's sounds, shared arrangement and project chat. You can write or record MIDI for the part and use the installed instrument's sound. Confirm that the correct preset and any required sample library are available. An instrument name alone does not establish that a saved part will sound as intended.

Computer Link works with one live generator at a time and shares rendered audio for playback. Other collaborators can hear that audio without receiving your plug-in installation. When the musical notes or sound change, update the render before asking them to review it. Keep the original instrument state and useful audio exports so a later handoff has the sound it needs.

The installed instrument contributes to SODIUM COLLAB's wider workspace: your source sounds, arrangement, collaborators and project decisions stay connected. Desktop Chrome is recommended for the beta. Use Computer Link with an eligible account and a supported Windows VST3 instrument, then give collaborators a specific part to review. The rendered audio brings your chosen sound into the shared song.

Other ways to use installed plug-ins

Amped Studio VST Remote uses a helper that connects installed desktop plug-ins to its browser studio on Windows or Mac. One VST Remote instance is active at a time; render a part to audio before switching to another plug-in. Its VST setup supports installed VST and VST3 instruments and effects, with a Premium account requirement. These are the requirements for its browser-connected plug-in workflow.

The one-plug-in limit matters if your arrangement depends on several installed sounds. Work out which parts need to remain adjustable and which you are willing to turn into audio. Try the specific plug-in you intend to use, rather than treating a broad format claim as a guarantee for your entire collection. Check the current account requirements before scheduling the work.

Soundtrap's native plug-in workflow supports VST3 and AU effects in its downloadable desktop app, currently on Production & Vocals. Collaborators can hear the processed track through the web or mobile app. The current workflow is for effects, with VST instruments not supported. That makes it a different option: desktop-native effects in a shared ecosystem, rather than installed instruments hosted through a browser helper.

These distinctions make a more useful shortlist than a single yes-or-no VST column. A Windows songwriter with a favourite instrument, a Mac producer needing an effect and a browser-only collaborator have different requirements. Follow the work each person needs to perform and verify that particular route.

Compare the route, the sound and the access

Decide whether the collaborator needs to hear the sound or change the sound. Those are different privileges and dependencies. A shared audio render lets someone evaluate the musical part; it does not give them the original instrument, library or editable preset. If they must revise the tone themselves, discuss the required software and access before the session.

Also separate instruments from effects. A synth creates the part you play; an effect processes existing sound. A studio supporting one category may not support the other. Write your requirement as a concrete task, such as 'use this installed piano for the MIDI part', instead of 'needs VST'. That makes the comparison much harder to misread.

SODIUM COLLAB: pros and cons

Pros

• Supported installed VST3 instruments contribute their sound to the browser arrangement.
• Rendered audio lets collaborators hear the part without receiving the instrument installation.
• Sounds, shared projects and project chat keep the instrument within the wider song.

Cons

• Computer Link uses a Windows helper and eligible account access for compatible VST3 instruments.
• One live generator is active at a time; update the rendered sound after musical changes.

Amped Studio: pros and cons

Pros

• VST Remote connects installed VST/VST3 instruments and effects to the browser studio.
• A helper is available for Windows and Mac.

Cons

• Requires eligible Premium access and a desktop helper; one VST Remote instance is active at a time.

Soundtrap: pros and cons

Pros

• Installed VST3/AU effects process tracks in the desktop app.
• Collaborators can hear the processed tracks through browser or mobile.

Cons

• This workflow requires the desktop app and Production & Vocals; VST instruments are not currently supported.

Try one real part before moving the song

Prepare a short phrase using the instrument or effect that makes this workflow important to you. Establish the correct sound, save the work and return to it. Then ask the intended collaborator to hear the result from their own device. This checks the actual requirement: preserving your sound in a project the other person can use.

With SODIUM COLLAB, use that instrument part inside the shared song rather than as an isolated plug-in demonstration. Add the phrase to the arrangement, check the rendered sound and ask for a specific response in project chat. The installed instrument contributes to the same connected workspace as your other sounds and parts. That wider musical context is the reason we recommend the SODIUM COLLAB route.

• Confirm the supported operating system, format and account access.
• Use the intended plug-in and its required preset or library.
• Keep the original musical part and an audio version of the important sound.
• Verify that collaborators hear the updated material after uploads complete.
• Agree where later note and sound revisions will happen.

SODIUM COLLAB is our recommended choice for bringing supported Windows VST3 instruments into a connected browser song. Computer Link contributes the installed sound, while Sounds, shared projects and project chat keep the musical work together. Develop the part, share its rendered sound and carry the next decision into the same arrangement. Your favourite instrument becomes part of a continuing collaboration.