VST2 and VST3 are two generations of the same plugin format, which defines how a plugin communicates with your DAW. VST3 is the current standard and the better default for new installations when your DAW supports it. VST2 is the earlier generation, still supported by many plugins and DAWs, and still useful for older projects and plugins that never received a VST3 version.
This guide covers what actually changes between the two formats, which of the two is better, and how to decide what to install.
VST2 vs VST3 at a Glance
VST stands for Virtual Studio Technology, the plugin standard Steinberg introduced in 1996. VST2 arrived in 1999, and VST3 followed in 2008 as a redesigned version of the standard. VST2 is an older plugin format used for virtual instruments and audio effects in DAWs.
VST3 is a newer plugin format designed to offer more flexible audio routing, processing, and parameter control. For musicians and producers, it can support features such as efficient processing, flexible sidechain routing, and advanced automation.
VST2 vs VST3: What's the Difference?
VST3 gives plugin developers more options for CPU processing, sidechain routing, and automation. However, the features available to producers depend on how the plugin developer implements the standard. Some functionality may also be available in VST2 plugins through their own implementations.
What a producer actually gets from a VST3 plugin depends on how the plugin developer implements the standard and whether the DAW supports the relevant feature. Here are the key differences you are most likely to notice:
CPU Processing
The VST3 standard allows a plugin to stop processing when it is not receiving audio. This prevents inactive plugins from continuously using processing resources. If you work with large projects containing many virtual instruments and effects, VST3's ability to use less CPU processing can help your computer handle inactive plugins more efficiently. VST2 plugins can also skip processing during silence, but only if the developer builds it in.
For example, if you have a reverb or delay plugin on a track that is currently silent, the feature can suspend CPU processing until audio reaches the plugin. This leaves more CPU resources available for other instruments and effects.
Sidechain and Audio Routing
VST3 includes dedicated sidechain inputs as part of the standard, which can make certain routing setups easier to use. One common example is sidechain compression.
For instance, you can use a kick drum to control a compressor on a bass track. When the kick hits, the compressor briefly reduces the bass level, creating space for the kick.
VST2 can also support sidechain processing, but the setup can depend more heavily on how the DAW handles additional plugin inputs. VST3 was designed with more flexible routing capabilities.
Automation and Parameter Control
Both VST2 and VST3 plugins can support automation, allowing you to change plugin settings automatically during playback. VST3 adds sample-accurate automation, which VST2 does not offer.
For example, you can automate a filter cutoff during a buildup, gradually increase a reverb mix before a chorus, or change an effect's settings at specific points in a song.
VST3 can give you more flexibility when automating plugin parameters, which is useful for creating transitions, dynamic effects, and detailed changes throughout a track.
Does VST3 Sound Better Than VST2?
No. The plugin format doesn't determine sound quality, because it isn't what processes your audio. The VST format controls how a plugin communicates with the DAW. It does not, by itself, determine the sound of the audio processing.
Think of it as the connection between your plugin and your DAW. The plugin's actual processing is what determines how the audio is changed. If a developer provides VST2 and VST3 versions of the same plugin with equivalent processing, switching between formats does not improve the sound quality.
VST2 vs VST3 Compatibility and Installation
File Format
VST2 and VST3 plugins can use different file types. VST2 plugins are .dll files on Windows and .vst bundles on macOS, while VST3 plugins use the .vst3 extension on both platforms.
Installation
Install locations differ too. For VST3, Steinberg defines recommended folders that plugins should install to and DAWs should scan:
on Windows:- Global (for all users): C:\\Program Files\\Common Files\\VST3
- User (mainly used by developers): %LOCALAPPDATA%/Programs/Common/VST3/
- User folder: /Users/username/Library/Audio/Plug-ins/VST3/
- Global (for all users): /Library/Audio/Plug-Ins/VST3
A DAW can also have its own application-specific VST3 folder. Because VST3 hosts are expected to scan these locations at startup, you usually don’t need to set a plugin path manually.
VST2 has no format-wide set of locations. The folder depends on the installer, operating system, and DAW. Common VST2 paths include:
On Windows:C:\\Program Files\\VSTPlugins
C:\\Program Files\\Steinberg\\VSTPlugins
C:\\Program Files\\Common Files\\VST2
C:\\Program Files\\Common Files\\Steinberg\\VST2
On macOS:/Library/Audio/Plug-Ins/VST
/Users/username/Library/Audio/Plug-ins/VST
If your DAW doesn’t find a VST2 plugin, you may need to add its folder in the DAW’s plugin settings.
Compatibility
DAW support varies more than most producers expect:
- Ableton Live, FL Studio, Fender Studio Pro, and REAPER load both VST2 and VST3 plugins, so either format works.
- Cubase and Nuendo disable VST2 scanning by default starting with version 14, and that carries into Cubase 15. You can turn them back on in the VST Plug-in Manager.
- Pro Tools uses Avid's AAX format and doesn't load VST plugins in either generation.
- Logic Pro uses Apple's Audio Units (AU) format, so VST plugins do not appear there.
Should You Install VST2, VST3, or Both?
For most producers starting fresh, VST3 alone is the cleaner choice. It's the format developers are actively supporting, it installs where your DAW already looks, and it avoids duplicate entries cluttering your plugin browser.
A few situations make keeping VST2 worthwhile:
- Existing projects: If older sessions loaded VST2 instances, removing those plugins can leave gaps when you reopen the project. Keep them installed until you've finished or rebuilt that work.
- VST2-only plugins: Some older or discontinued plugins never received a VST3 version, and VST2 is the only way to run them.
- Troubleshooting: If a VST3 version behaves unexpectedly in your DAW, having the VST2 version available gives you something to fall back on while you work out what's wrong.
- DAW limitations: If your DAW's VST3 support is limited or you're on an older version, VST2 may still be the more reliable option.
Keeping Both Versions
Installing both VST2 and VST3 can make sense when you work with older projects while also creating new ones.
The main drawback of installing two versions of the same plugin: this can make your plugin list more confusing. If you keep both, pay attention to the format when choosing a plugin instance so you know which version you are using.
Overall, VST3 is a good default for new installations, while VST2 remains valuable for compatibility.
Yamaha Creator Growth and Pro Pass include Cubase 15 AI, plus Output Arcade with 80,000 samples and LANDR's library of more than 3 million loops and one-shots. Start a 7-day free trial and find the plan that fits your workflow.
Frequently Asked Questions
Do VST2 and VST3 plugins use the same presets?
It depends on the plugin. Many developers use a shared preset format and location, so presets you save in one version show up in the other. Others store presets separately per format, in which case you'll need to re-save or re-import them.
Why do some plugins still only come as VST2?
Some plugins are available only as VST2 because their developers have not released a VST3 version or continue to maintain VST2 for compatibility with existing projects. Steinberg stopped issuing new VST2 licenses in October 2018, but developers who signed the VST2 license agreement before that cutoff can still distribute VST2 plugins.
Can you have multiple versions of the same plugin installed?
Yes, you can install both VST2 and VST3 when you need VST2 for older projects while using VST3 for newer ones. This lets you maintain compatibility with legacy sessions while using newer plugin formats.
Does VST3 work on Mac and Windows?
Yes. VST3 supports macOS, Windows, and Linux. Format support isn't the same as plugin support. Whether a specific VST3 plugin works on your system depends on the plugin's compatibility with your operating system and DAW.
