What Is a VST3 Plugin? VST3 vs VST2 and All Plugin Formats Explained

What Is a VST3 Plugin?

VST3 stands for Virtual Studio Technology 3. It is the third major version of the VST plugin standard, developed by Steinberg — the company behind Cubase — and first released in 2008. VST3 defines how virtual instruments and audio effects plug into a Digital Audio Workstation (DAW) and communicate with it: how audio passes through the plugin, how the DAW sends MIDI or control signals to the plugin, how automation is recorded and played back, and how the plugin's user interface is displayed within the DAW's window.

The VST format itself originated in 1996 with VST1 (also called VST), which was released alongside Cubase. VST2 followed in 1999 and became the dominant plugin format for over a decade — virtually every plugin and every DAW (except Pro Tools and Logic Pro) used VST2. When Steinberg released VST3 in 2008, adoption was slow because DAWs were reluctant to migrate and developers had to maintain two plugin versions simultaneously. By the mid-2010s, VST3 had become broadly supported, and by the early 2020s it became the primary format for new plugin development.

Today, if you are using any major DAW other than Logic Pro (which uses AU) or Pro Tools (which uses AAX), VST3 is the format you should prefer for plugins that offer both VST2 and VST3 versions. Steinberg officially discontinued VST2 licensing in 2018, meaning new plugin developers cannot release new VST2 plugins without using a legacy license — a further push toward VST3 adoption.

VST3 vs VST2: What Actually Changed

The improvements in VST3 over VST2 fall into several categories, each addressing real limitations that engineers and developers encountered with the older format.

Context-Aware Processing (The Biggest Practical Improvement)

The most significant improvement in VST3 for CPU efficiency is context-aware processing. In VST2, every plugin instance in your session runs continuously, consuming CPU resources even when no audio is passing through it. If you have 50 plugin instances in a session but only 10 are actively receiving audio at a given moment, all 50 are still consuming CPU. In VST3, plugins can signal to the DAW when they have nothing to process, and the DAW can suspend their processing — they use zero CPU until audio arrives. For sessions with many plugins, this can result in meaningful CPU savings, especially on tracks that are silent for extended periods.

Multiple Audio and MIDI Buses

VST2 was fundamentally designed around a simple model: audio goes in, audio comes out. Implementing features like sidechain inputs — where a compressor reads a sidechain signal from a separate audio source — required workarounds in VST2 that were DAW-specific and not universally compatible. VST3 natively supports multiple input and output audio buses, making sidechain inputs, auxiliary outputs, and complex routing scenarios straightforward to implement and use across all VST3-compatible DAWs in a consistent way.

Sample-Accurate Automation

VST2 automation was processed at the block level — the DAW would send automation parameter values at the start of each audio processing buffer (typically 128–2048 samples), and changes within that buffer were applied at the buffer boundary. VST3 supports sample-accurate automation, meaning parameter changes can be applied to any individual sample within a buffer. The practical difference is most audible for fast automations on dynamic effects — a sidechain compression duck or a fast filter sweep sounds smoother and more precise with sample-accurate automation.

Better MIDI Handling and Note Expression

VST3 introduced Note Expression, a feature that allows per-note control of plugin parameters in polyphonic contexts. With Note Expression, you can, for example, apply pitch bend, vibrato, or filter cutoff changes to individual notes in a chord independently — not just the entire plugin instance. This is particularly powerful for expressive virtual instrument performance and is used in Cubase and Bitwig for detailed MIDI expression editing.

VST3 also provides improved MIDI channel handling, supporting instruments that need to receive MIDI on specific channels (useful for multi-timbral instruments) in a more standardized way than VST2's more limited MIDI routing.

Resizable Interfaces

VST3 officially standardizes GUI resizing — the ability for the user to scale the plugin interface to different sizes. While some VST2 plugins implemented proprietary resizing, it was not part of the standard. VST3's standardized resizing support means that most VST3 plugins can be scaled, which is particularly important on high-resolution displays where small plugin UIs become difficult to read.

Improved Preset Management

VST3 defines a standardized preset file format (.vstpreset) with a standardized location on disk. This means presets are organized consistently across DAWs and can be shared between users without compatibility issues. VST2 preset formats varied by plugin and DAW, leading to inconsistencies in how presets were saved, loaded, and shared.

AU and AAX: The Other Major Plugin Formats

VST3 is the dominant cross-platform format, but two other formats are important to understand: AU (Audio Units) and AAX (Avid Audio eXtension).

AU (Audio Units) — macOS and Logic Pro

AU is Apple's plugin format, developed alongside macOS and deeply integrated with Core Audio, Apple's audio infrastructure. AU is the native plugin format for Logic Pro and GarageBand. All plugins that run in Logic Pro must be AU — VST plugins of any version do not work in Logic Pro. Most major plugin developers release macOS versions of their plugins as both VST3 and AU, so you can use your favorite plugins in any DAW on a Mac.

AU offers capabilities broadly similar to VST3. The performance, quality, and feature set are comparable for the vast majority of use cases. The choice between AU and VST3 is primarily determined by which DAW you use — Logic Pro users use AU; everyone else on macOS uses VST3 or AU depending on DAW support.

AAX — Pro Tools

AAX is Avid's proprietary plugin format for Pro Tools. VST3 plugins cannot be used in Pro Tools, and AAX plugins cannot be used in non-Pro Tools DAWs. AAX has two sub-types: AAX Native (for software-only processing) and AAX DSP (for Avid's hardware DSP cards). Most plugin developers targeting the professional studio market release AAX versions alongside VST3 and AU, but smaller independent developers may not offer AAX versions due to the higher development and certification costs involved.

For producers who use Pro Tools, this means checking that a plugin is available in AAX format before purchasing, since VST3 and AU versions will not work in Pro Tools regardless of the DAW settings.

CLAP: The Open-Source Alternative

CLAP (CLever Audio Plugin) is an open-source, royalty-free plugin format developed by Bitwig and u-he as an alternative to the VST/VST3 ecosystem. Released in 2022, CLAP offers many of the same technical capabilities as VST3 — efficient processing, multiple audio buses, sample-accurate automation, per-note expression — while being entirely open-source and free to implement without licensing restrictions.

CLAP support is growing among DAWs and plugin developers. Bitwig Studio, Reaper, FL Studio, and several others now support CLAP alongside VST3. Major plugin developers including FabFilter, u-he, and Arturia have released CLAP versions of their plugins. For most producers, CLAP is not a format you need to actively seek out — if your DAW supports it and a plugin offers it, it may offer performance advantages, but VST3 remains the broader standard with the widest DAW compatibility.

Installing and Using VST3 Plugins

VST3 plugins use the .vst3 file extension and are installed to standard system locations. On Windows, the default installation path is C:\Program Files\Common Files\VST3. On macOS, VST3 plugins install to /Library/Audio/Plug-Ins/VST3. Most plugin installers handle this automatically — you run the installer, the plugin files are placed in the correct location, and your DAW finds them the next time it scans for plugins.

When you open your DAW after installing a new VST3 plugin, the DAW typically prompts you to rescan plugins or does so automatically. After the scan, the new plugin appears in your instrument or effects browser. If a plugin doesn't appear after installation, manually triggering a plugin rescan in your DAW's preferences usually resolves the issue.

For producers who have both VST2 and VST3 versions of the same plugin installed — which was common during the transition period when developers shipped both — you should select the VST3 version in your DAW settings and remove the VST2 version to avoid confusion. Most DAW plugin browsers let you filter by format, making it easy to identify which version of a plugin you're using.

VST3 in Practice: Does the Format Actually Matter?

For most day-to-day music production, the choice between VST3 and VST2 has minimal audible impact — the same plugin algorithm sounds the same in both formats. The practical differences show up in session size and complexity. In large sessions with 50+ plugin instances, the CPU savings from VST3's context-aware processing can be meaningful, particularly on tracks with significant silent sections. For small sessions, the difference is negligible.

The areas where VST3 makes a real and audible difference are the automation improvements (sample-accurate automation is genuinely more precise for fast parameter changes) and the sidechain routing improvements (sidechain inputs work more consistently across DAWs in VST3). For producers who rely heavily on sidechain compression or complex signal routing, VST3's native multiple bus support makes workflows significantly cleaner.

The most important practical consideration is compatibility: if you're using Logic Pro, you need AU plugins and VST3 is irrelevant. If you're using Pro Tools, you need AAX. For every other major DAW, VST3 is the preferred format for new plugin purchases and installations. When a plugin offers both formats, VST3 is the one to choose.

Frequently Asked Questions