Four plug-in formats dominate modern music production: VST2, VST3, AU, and AAX. Steinberg created the first two, Apple owns the third, and Avid controls the fourth. Which one a producer installs depends entirely on the host software, because a DAW can only load formats it was built to recognize.
That single fact resolves most of the confusion around installers that offer four checkboxes for what appears to be one product. A plug-in format is not a quality tier or a sound upgrade. It is a technical agreement between the plug-in and the host, and picking the wrong one simply means the software never shows up in the DAW's browser.
This is why one product from a developer such as FabFilter or Native Instruments can ship as VST3, AU, and AAX at the same time. The company writes the audio engine once, then wraps it in each connector its customers need. Understanding this DAW plug-in architecture makes every installation decision easier, because the question stops being "which version sounds best" and becomes "which socket does my host expose."
Each format also lives in a fixed location on the drive. On Windows, VST3 files sit in a shared Program Files folder, while macOS keeps VST3, AU, and AAX components in separate Library directories. The host scans those folders on launch, which is why a plug-in installed to the wrong path appears to vanish.
The consequences are already visible inside Steinberg's own products. Since the release of Cubase 14 in November 2024, both Cubase and Nuendo disable VST2 plug-ins by default, and users must manually re-enable them through the VST Plug-in Manager. On Apple Silicon Macs, the situation is stricter still: VST2 plug-ins only run when the DAW launches in Rosetta translation mode, and they cannot run at all on ARM-based Windows machines.
None of this means VST2 stopped working overnight. Many third-party hosts, including Reaper, Ableton Live, and FL Studio, continue to load VST2 builds, and thousands of older sessions depend on them. The risk is directional rather than immediate: every operating system update and every DAW release moves the format closer to genuine obsolescence, so no new studio setup should rely on it.
For developers, the path is equally settled. The Steinberg SDK migration pushed the industry toward a single toolkit, since the current VST3 development kit is the only Steinberg framework that new plug-in makers can license. Companies that once maintained parallel VST2 and VST3 builds, such as u-he, have progressively dropped the older format from their updates.
For users, the practical rule is short: when an installer offers both VST2 and VST3, choose VST3. It carries active support, works natively on Apple Silicon, and matches where every major host is heading. The exception is a legacy project that saved its plug-in states under VST2, a scenario covered later in this guide.
Logic Pro instrument support illustrates how format lock-in shapes buying decisions. Virtually every commercial developer ships an AU version precisely because the Logic user base is too large to ignore, so Mac producers rarely encounter a serious product without one. Hosts such as Live and Reaper on macOS can load both AU and VST3, which gives Mac users a choice that Logic users do not have.
The newer Audio Unit extension format, known as AUv3, takes a different technical approach. Apple built it on the App Extensions system, meaning each plug-in runs as a sandboxed miniature app rather than raw code inside the host, which improves stability because a crashing plug-in no longer takes the whole DAW down with it. AUv3 also powers plug-ins on iPad and iPhone, making it the bridge between desktop and mobile production.
Getting a plug-in into that ecosystem involves more steps than the other formats demand. Developers must join the Avid developer program to access the AAX software development kit, and they need a working copy of Pro Tools to test their builds. Commercial releases must then pass through the iLok signing process, in which PACE's digital signing tools certify the plug-in before Pro Tools trusts and loads it.
That gatekeeping has a practical upside and a cultural downside. The upside is consistency: signed AAX plug-ins behave predictably across professional facilities, which matters when a session travels between studios. The downside is that hobbyists and free plug-ins often skip AAX entirely, because the licensing and testing overhead outweighs the reach for a no-budget project.
Installing every available format at once is tempting but counterproductive. Duplicate builds clutter the plug-in browser, force the DAW to scan redundant files at startup, and create confusion when a project references one format while the producer habitually loads another. A cleaner approach is to install only the connector the primary host uses, then add a second format later if a new DAW enters the workflow.
Cross-platform collaborators deserve one extra consideration. When two producers exchange project files between Windows and macOS, VST3 is the safest common ground for shared hosts such as Live or Studio One, since AU does not exist on Windows and AAX ties both parties to Pro Tools. Agreeing on a shared plug-in list and format before a collaboration starts prevents the dreaded wall of "missing plug-in" warnings.
A second misunderstanding concerns older session compatibility. A project saved with VST2 instances does not automatically remap to VST3 versions, because many hosts treat the two builds as different plug-ins with separate identifiers. Some developers and DAWs offer migration tools that swap instances while preserving settings, but producers with a deep archive should test that process before uninstalling anything.
The third trap is assuming that DAW support is permanent. Steinberg's decision to disable VST2 by default shows how quickly a "standard" can slide toward legacy status, and open-source challengers such as the CLAP format demonstrate that the landscape keeps moving. Treating any music software format guide as a snapshot rather than a permanent map is the healthiest mindset a producer can adopt.
Developers and technically curious producers face a different next step. Anyone building or porting a plug-in should study the Steinberg SDK migration path in detail, since the current toolkit defines how new instruments and effects reach almost every host outside the Apple and Avid walled gardens. Those targeting the professional post-production market will also need a working knowledge of the iLok signing process, which governs entry into Pro Tools facilities and connects directly to broader questions of copy protection and license management in audio software.
That single fact resolves most of the confusion around installers that offer four checkboxes for what appears to be one product. A plug-in format is not a quality tier or a sound upgrade. It is a technical agreement between the plug-in and the host, and picking the wrong one simply means the software never shows up in the DAW's browser.
How DAW plug-in architecture actually works
A plug-in format works like a standard power socket. The appliance is the same whether it ships with a European or an American plug, but it only draws power from a matching outlet. In audio terms, the digital signal processing code inside a compressor or synthesizer is identical across builds, while the format acts as the connector that lets the host pass audio, MIDI, and automation data in and out.This is why one product from a developer such as FabFilter or Native Instruments can ship as VST3, AU, and AAX at the same time. The company writes the audio engine once, then wraps it in each connector its customers need. Understanding this DAW plug-in architecture makes every installation decision easier, because the question stops being "which version sounds best" and becomes "which socket does my host expose."
Each format also lives in a fixed location on the drive. On Windows, VST3 files sit in a shared Program Files folder, while macOS keeps VST3, AU, and AAX components in separate Library directories. The host scans those folders on launch, which is why a plug-in installed to the wrong path appears to vanish.
VST2: a discontinued standard on borrowed time
Steinberg launched Virtual Studio Technology in 1996, and VST2 became the de facto standard for Windows studio add-ons for more than two decades. That long reign ended formally in 2022, when Steinberg announced it would phase out VST2 across all of its host applications and stop licensing the format to new developers. The VST2 compatibility status today is unambiguous: the format is discontinued, and its software development kit is no longer available to newcomers.The consequences are already visible inside Steinberg's own products. Since the release of Cubase 14 in November 2024, both Cubase and Nuendo disable VST2 plug-ins by default, and users must manually re-enable them through the VST Plug-in Manager. On Apple Silicon Macs, the situation is stricter still: VST2 plug-ins only run when the DAW launches in Rosetta translation mode, and they cannot run at all on ARM-based Windows machines.
None of this means VST2 stopped working overnight. Many third-party hosts, including Reaper, Ableton Live, and FL Studio, continue to load VST2 builds, and thousands of older sessions depend on them. The risk is directional rather than immediate: every operating system update and every DAW release moves the format closer to genuine obsolescence, so no new studio setup should rely on it.
VST3: the current default for most DAWs
VST3 arrived in 2008 as a complete redesign rather than a version bump. It separates audio processing from the user interface, supports sample-accurate automation, and allows a plug-in to switch off its processing when no audio passes through, which saves CPU on large sessions. Broad VST3 DAW support now extends across Cubase, Nuendo, Ableton Live, FL Studio, Studio One, Reaper, Bitwig Studio, and many others on both Windows and macOS.For developers, the path is equally settled. The Steinberg SDK migration pushed the industry toward a single toolkit, since the current VST3 development kit is the only Steinberg framework that new plug-in makers can license. Companies that once maintained parallel VST2 and VST3 builds, such as u-he, have progressively dropped the older format from their updates.
For users, the practical rule is short: when an installer offers both VST2 and VST3, choose VST3. It carries active support, works natively on Apple Silicon, and matches where every major host is heading. The exception is a legacy project that saved its plug-in states under VST2, a scenario covered later in this guide.
Audio Units: Apple's native standard
Audio Unit, usually shortened to AU, is the Mac audio effects standard built directly into macOS through the Core Audio framework. Because Apple maintains it at the operating system level, AU enjoys deep integration on Apple hardware, and it is the only third-party plug-in connector that Logic Pro and GarageBand accept. A producer who buys a synthesizer for Logic must install the AU build, since neither VST3 nor AAX will ever appear in that DAW.Logic Pro instrument support illustrates how format lock-in shapes buying decisions. Virtually every commercial developer ships an AU version precisely because the Logic user base is too large to ignore, so Mac producers rarely encounter a serious product without one. Hosts such as Live and Reaper on macOS can load both AU and VST3, which gives Mac users a choice that Logic users do not have.
The newer Audio Unit extension format, known as AUv3, takes a different technical approach. Apple built it on the App Extensions system, meaning each plug-in runs as a sandboxed miniature app rather than raw code inside the host, which improves stability because a crashing plug-in no longer takes the whole DAW down with it. AUv3 also powers plug-ins on iPad and iPhone, making it the bridge between desktop and mobile production.
AAX: the gatekeeper format for Pro Tools
Avid Audio eXtension, or AAX, exists for exactly one ecosystem: Pro Tools. Avid introduced it in the early 2010s to replace its older RTAS and TDM formats, and modern Pro Tools versions load nothing else. The AAX Pro Tools requirement means that a mixing engineer working in a commercial post-production facility has no format decision to make, because the host dictates it completely.Getting a plug-in into that ecosystem involves more steps than the other formats demand. Developers must join the Avid developer program to access the AAX software development kit, and they need a working copy of Pro Tools to test their builds. Commercial releases must then pass through the iLok signing process, in which PACE's digital signing tools certify the plug-in before Pro Tools trusts and loads it.
That gatekeeping has a practical upside and a cultural downside. The upside is consistency: signed AAX plug-ins behave predictably across professional facilities, which matters when a session travels between studios. The downside is that hobbyists and free plug-ins often skip AAX entirely, because the licensing and testing overhead outweighs the reach for a no-budget project.
Choosing what to install
Modern producer install choices reduce to a simple mapping between host and format. Producers working in Cubase, Live, FL Studio, Studio One, Bitwig, or Reaper should select VST3 during installation. Logic Pro and GarageBand users need AU. Pro Tools engineers need AAX, and nobody starting fresh in 2026 should tick the VST2 box unless a specific legacy need exists.Installing every available format at once is tempting but counterproductive. Duplicate builds clutter the plug-in browser, force the DAW to scan redundant files at startup, and create confusion when a project references one format while the producer habitually loads another. A cleaner approach is to install only the connector the primary host uses, then add a second format later if a new DAW enters the workflow.
Cross-platform collaborators deserve one extra consideration. When two producers exchange project files between Windows and macOS, VST3 is the safest common ground for shared hosts such as Live or Studio One, since AU does not exist on Windows and AAX ties both parties to Pro Tools. Agreeing on a shared plug-in list and format before a collaboration starts prevents the dreaded wall of "missing plug-in" warnings.
Common misconceptions among producers
The most persistent myth holds that VST3 sounds better than VST2, or that AAX carries some professional sonic advantage. In reality, the audio engine is the same across builds of the same product, so a compressor renders identical output whether the host loaded it through VST3, AU, or AAX. Any perceived difference comes from mismatched settings or unit conversion quirks, not from the connector itself.A second misunderstanding concerns older session compatibility. A project saved with VST2 instances does not automatically remap to VST3 versions, because many hosts treat the two builds as different plug-ins with separate identifiers. Some developers and DAWs offer migration tools that swap instances while preserving settings, but producers with a deep archive should test that process before uninstalling anything.
The third trap is assuming that DAW support is permanent. Steinberg's decision to disable VST2 by default shows how quickly a "standard" can slide toward legacy status, and open-source challengers such as the CLAP format demonstrate that the landscape keeps moving. Treating any music software format guide as a snapshot rather than a permanent map is the healthiest mindset a producer can adopt.
Practical applications
The immediate action for most producers is an audit: open the plug-in manager, identify anything still loading as VST2, and check each developer's site for a current build. That single afternoon of housekeeping protects future projects and reveals which products have quietly gone abandoned. From there, workflows that span Windows and macOS benefit from standardizing on cross-platform audio tools, a topic that rewards a deeper comparison of hosts and shared format strategies.Developers and technically curious producers face a different next step. Anyone building or porting a plug-in should study the Steinberg SDK migration path in detail, since the current toolkit defines how new instruments and effects reach almost every host outside the Apple and Avid walled gardens. Those targeting the professional post-production market will also need a working knowledge of the iLok signing process, which governs entry into Pro Tools facilities and connects directly to broader questions of copy protection and license management in audio software.
