Soundtrap has added VST instrument support to its cloud-based production platform, expanding the sound sources available inside browser-based projects. The update arrives alongside a partnership with Arturia, bringing Pigments and Efx MOTIONS into the launch offering for 30 days.
The development gives Soundtrap users a route to work with third-party virtual instruments within collaborative sessions rather than relying solely on the platform’s built-in sounds. The partnership was reported by Bedroom Producers Blog ↗ (opens in a new tab).
Key Takeaways
- Soundtrap has announced VST instrument support for its cloud-based music-production platform.
- Arturia’s Pigments and Efx MOTIONS are included as part of the launch partnership.
- Soundtrap users can access those Arturia tools for 30 days.
- The update could make Soundtrap a more practical writing and collaboration environment for producers who work with software instruments.
What VST instrument support changes in Soundtrap
VST instruments are software sound generators played and programmed from MIDI: synthesizers, sampled instruments and other virtual sound sources. They are central to many modern production workflows, whether a producer is sketching chords, programming basslines or building a beat around a synth patch.
Adding support for them potentially gives Soundtrap projects access to a broader palette than a closed, browser-only instrument library. It also moves the platform closer to the workflow many producers expect from a conventional DAW: choose an instrument, record or programme MIDI, then develop the part inside the arrangement.
That is particularly relevant in remote sessions. A collaborator can contribute a musical idea directly to a shared project rather than exporting a rough audio bounce, sending files separately and waiting for somebody else to rebuild the MIDI arrangement. Producers new to the format can find a broader explanation of the distinction between instruments and processing tools in Product London’s guide to VST plugins.
The announcement does not specify which VST formats, operating systems, account tiers or third-party instruments are supported, nor does it set out how projects behave when a collaborator does not have access to the same plugin. Those details will determine how useful the feature is for sessions that move between Soundtrap and desktop DAWs.
Arturia Pigments and Efx MOTIONS join the launch
Arturia’s Pigments and Efx MOTIONS are the named products in Soundtrap’s initial partnership, with users able to access them for 30 days. Pigments gives the announcement an identifiable instrument option for synth-led production, while Efx MOTIONS broadens the initial Arturia selection beyond a single sound source.
For beatmakers and electronic producers, the immediate appeal is less about replacing a full desktop setup than getting more distinctive sounds into quick ideas, topline sessions and collaborative drafts. If an arrangement survives the writing stage, the producer can then decide whether it needs further sound design, recording or mix work elsewhere.
The 30-day period should be treated as an access window rather than a permanent licence. The available information does not state what happens after it ends, whether projects using the tools remain editable, or what continued access will cost. Anyone beginning a client project with either product should check those terms before committing essential parts to the session.
Why cloud-based collaborators should watch this update
Soundtrap’s appeal has long been its accessibility: a project can be opened and developed without every contributor needing the same locally installed DAW. Third-party instrument support could make that convenience more viable for producers who want to retain a familiar plugin-led writing process.
It may also help bridge the gap between a simple writing room and a more developed production environment. A producer can capture MIDI ideas, audition virtual instruments and keep arrangement decisions attached to the project rather than flattening everything to audio at the earliest stage. For a refresher on how virtual instruments fit into a typical production setup, see Product London’s beginner guide to virtual instruments.
The practical next step is to check Soundtrap’s implementation details before relying on the feature for shared releases or paid work. Plugin availability, collaboration permissions and project portability matter as much as the presence of a recognisable instrument name.