The encyclopedia · Software & IT · Technical decision · 1996–2001
Steinberg's 1996 VST spec made software plugins the audio standard
Steinberg shipped VST inside Cubase in 1996, then opened the spec to every developer; hardware racks gave way to software plugins any DAW could host.
Steinberg Media Technologies
The solution
Before 1996 computer music production had no shared plugin format: effects and instruments came as hardware, and each software host used its own private interfaces, so developers had to rewrite plugins for every DAW or skip them.
Steinberg introduced VST inside Cubase in 1996, then released the specification and SDK to the wider development community in 1997. Any developer could now write one plugin that ran inside any compatible host, standardizing the interface between plugins and software studios.
The open interface flipped incentives: plugin makers targeted VST because major hosts supported it, and hosts supported it because it unlocked thousands of plugins. Software instruments and effects replaced racks of hardware, and VST became the default plugin format across the industry.
Why it worked
- An open, published spec let any developer build without permission.
- Hosts gained a whole plugin market by supporting one API.
- Plugin makers got one target instead of per-DAW rewrites.
- VST rode the shift from hardware studios to software production.
What can be applied
The owner of a tool can win a category by giving away the interface, not the product: once the plugin API was open, no host could afford to ignore it, and the ecosystem grew beyond Steinberg itself.
Aftermath
Thirty years on, VST is still supported by virtually every major DAW, and Steinberg's 30th-anniversary 'Steinberg Classics' line re-releases early VST plugins as free VST3 versions — a reminder that the format outgrew its owner and became the industry's common plugin language.
Sources
spotted an error? The archive wants to know.