Key takeaways
- Free gives you standalone Mac synths; Pro adds VST3 export.
- VST3 export is part of the current public workflow, but Audio Unit is not.
- The format story is easiest to trust when the page states the limits plainly.
Overview
VST3 export in Studio 56 means that the current public workflow can move from a written synth concept to a DAW-ready VST3 build on the Pro tier. That is the practical user-facing promise. It is more useful to understand it that way than to think about the acronym in isolation.
The simplest distinction is between Free and Pro. Free builds standalone Mac synths that you can open and play on Apple silicon Macs. Pro adds the ability to export VST3 builds so the instrument can move into a DAW workflow that supports VST3.
That matters because a lot of product pages blur the line between “this is a synth you can use on your computer” and “this is a plugin you can insert inside your DAW.” Studio 56 is clearer when it says those are different output stages and ties them directly to the tier structure.
It also matters to say what VST3 export does not mean yet. The current public product does not claim Audio Unit export and does not claim public Windows builds. Keeping those limits explicit is important because it helps users decide whether the current scope already fits their workflow.
In practice, the VST3 question is usually a workflow question. If you only need the instrument on your Mac and are comfortable playing it standalone, Free may already be enough. If the goal is to move the instrument into a DAW session as part of a larger production workflow, Pro and VST3 export become much more relevant.
That is also why VST3 export belongs in the pricing conversation and not only the format conversation. For most users, the feature matters because it changes how the instrument fits into their day-to-day production process.
The cleanest way to think about it is this: Studio 56 is a synth-first workflow that starts with a written sound idea. Free gets you to a standalone Mac instrument. Pro extends that path into VST3 export. That is the current public promise, and it is strong precisely because it is narrow and legible.