Plugin Formats Explained: VST2, VST3, and AU
Before installing anything, you need to understand the three plugin formats that Ableton Live supports. Each format has different file types, installation locations, and capabilities.
VST2 (Virtual Studio Technology 2)
VST2 is the legacy plugin format created by Steinberg. On Windows, VST2 plugins are .dll files. On Mac, they are .vst bundles. VST2 plugins install to a folder you specify, and Ableton scans that folder to find them. While VST2 is still widely supported, it is being phased out by most developers in favor of VST3.
VST3 (Virtual Studio Technology 3)
VST3 is the modern standard. On Windows, VST3 plugins are .vst3 files installed to C:\Program Files\Common Files\VST3\. On Mac, they are .vst3 bundles installed to /Library/Audio/Plug-Ins/VST3/. VST3 plugins are more CPU-efficient, support resizable interfaces, handle silence intelligently, and install to standardized locations. Always prefer VST3 when available.
AU (Audio Units) - Mac Only
Audio Units is Apple's native plugin format, exclusive to macOS. AU plugins are .component files installed to /Library/Audio/Plug-Ins/Components/. They are validated by Apple's auval tool and tend to be very stable on Mac. If you produce exclusively on Mac, AU is an excellent choice alongside or instead of VST3.
Installing Plugins on Mac
Step 1: Download the Plugin Installer
Visit the plugin developer's website and download the Mac installer. It will typically be a
.dmg(disk image) or.pkg(installer package) file. Save it to your Downloads folder.Step 2: Run the Installer
Double-click the downloaded file. If it is a
.dmg, a window opens with the installer inside it. Double-click the installer application. If it is a.pkg, it launches the macOS installer wizard directly.The installer will ask which formats to install. Select VST3 and/or AU. You can deselect VST2 unless you specifically need it. Some installers also offer AAX (for Pro Tools), which you can skip.
Step 3: Choose Installation Location
Most Mac plugin installers automatically place files in the correct system locations:
- VST3:
/Library/Audio/Plug-Ins/VST3/ - AU:
/Library/Audio/Plug-Ins/Components/ - VST2:
/Library/Audio/Plug-Ins/VST/
Do not change these paths unless you have a specific reason. Ableton expects plugins in these standard locations.
- VST3:
Step 4: Authorize the Plugin
Many plugins require authorization after installation. This may involve entering a serial number, logging into a developer account, or using an authorization manager like iLok, Native Access, or Plugin Alliance's Installation Manager. Complete the authorization before opening Ableton.
Step 5: Rescan in Ableton
Open Ableton Live. Navigate to Live > Settings (Cmd+,). Go to the Plug-ins tab (called "Plugins" in Live 12). Make sure Use Audio Units is enabled if you installed AU format, and Use VST3 Plug-In System Folder is enabled for VST3. Click Rescan to find newly installed plugins. They will appear in your browser under the Plug-ins section.
Installing Plugins on Windows
Step 1: Download the Plugin Installer
Visit the developer's website and download the Windows installer. It will be a
.exefile or occasionally a.zipcontaining the installer.Step 2: Run the Installer
Right-click the
.exefile and select Run as administrator if prompted. This ensures the installer has permission to write to system plugin folders. Follow the installer wizard.When the installer asks which formats to install, select VST3. You can also install VST2 if you want a fallback, but VST3 is preferred.
Step 3: Set the VST2 Install Path (If Using VST2)
VST3 plugins automatically install to
C:\Program Files\Common Files\VST3\and Ableton finds them there. VST2 plugins need a specific folder. When the installer asks for the VST2 path, use a consistent location like:C:\Program Files\VSTPlugins\orC:\VST Plugins\Use the same folder for every VST2 plugin you install. This makes configuration in Ableton simple since you only need to point Ableton to one folder.
Step 4: Authorize the Plugin
Complete any required authorization: serial number entry, online activation, iLok, Native Access, or other license managers. Do this before launching Ableton.
Step 5: Configure Ableton and Rescan
Open Ableton Live. Go to Options > Settings (Ctrl+,). Click the Plug-ins tab. Under VST2 Plug-In Custom Folder, click Browse and select the folder where you installed your VST2 plugins. Make sure Use VST3 Plug-In System Folder is enabled. Click Rescan Plug-ins. Your new plugins will appear in the browser.
Configuring Ableton to Find Your Plugins
After installing plugins on your system, you need to tell Ableton where to look. This is done in Ableton's Preferences (Settings in Live 12).
Mac Configuration
Open Plugin Settings
Go to Live > Settings (Cmd+,) and click the Plug-ins tab.
Enable Plugin Sources
Toggle on the sources you want Ableton to scan:
- Use VST3 Plug-In System Folder: Scans
/Library/Audio/Plug-Ins/VST3/ - Use Audio Units: Scans
/Library/Audio/Plug-Ins/Components/ - VST2 Plug-In Custom Folder: Set this to
/Library/Audio/Plug-Ins/VST/or wherever your VST2 plugins live
- Use VST3 Plug-In System Folder: Scans
Windows Configuration
Open Plugin Settings
Go to Options > Settings (Ctrl+,) and click the Plug-ins tab.
Set Plugin Folders
- Use VST3 Plug-In System Folder: Enable this. Ableton scans
C:\Program Files\Common Files\VST3\automatically. - VST2 Plug-In Custom Folder: Click Browse and navigate to your VST2 folder (e.g.,
C:\Program Files\VSTPlugins\).
- Use VST3 Plug-In System Folder: Enable this. Ableton scans
Scanning Plugins
After configuring your paths, click the Rescan Plug-ins button. Ableton will scan all configured folders and index every compatible plugin it finds. This process can take a few seconds to a few minutes depending on how many plugins you have installed.
Once scanning completes, find your plugins in the browser sidebar. On the left side of Ableton's browser, look for the Plug-ins section. Expand it to see categories or search by name using Ableton's search bar (Cmd+F on Mac, Ctrl+F on Windows).
Troubleshooting Missing or Crashed Plugins
Plugins sometimes fail to appear after installation. Here are the most common causes and fixes.
Plugin Does Not Appear in Browser
| Cause | Fix |
|---|---|
| Wrong plugin folder path in Preferences | Verify the folder path in Plug-ins settings matches where the plugin is installed. Use your file manager to confirm the plugin file exists in that folder. |
| Plugin format not enabled | Make sure the corresponding toggle is on (Use VST3, Use Audio Units, or VST2 Custom Folder). |
| Plugin not rescanned | Click Rescan Plug-ins in Preferences after installing new plugins. |
| 32-bit plugin on 64-bit Ableton | Download and install the 64-bit version of the plugin from the developer. |
| Plugin requires authorization | Open the plugin's license manager and complete authorization before rescanning in Ableton. |
Plugin Crashed During Scan
If a plugin crashes during Ableton's scan, it gets added to a blocklist and will not appear. To fix this:
Step 1: Find the Crashed Plugin Info
In Ableton's Plug-ins settings, look for a section showing crashed or blocked plugins. In Live 12, this is displayed directly in the Preferences window.
Step 2: Fix the Root Cause
Update the plugin to the latest version from the developer's website. Reinstall it if the file may be corrupted. Make sure any required authorization is complete.
Step 3: Rescan
Click Rescan Plug-ins in Ableton's Preferences. Ableton will attempt to load the previously crashed plugin again. If the issue is resolved, the plugin will appear normally in the browser.
Plugin Appears but Will Not Load
If a plugin shows in the browser but gives an error when you drag it onto a track, the most common cause is an expired trial or missing authorization. Open the plugin's standalone application or license manager, verify your license status, and try loading it in Ableton again.
Organizing Your Plugin Library
As your plugin collection grows, finding the right tool quickly becomes important, especially in time-pressured battle scenarios.
Use Ableton's Collections
In Ableton Live's browser, you can assign plugins to colored Collections. Right-click any plugin in the browser and assign it to one of seven Collections. Create a system that works for your workflow:
- Collection 1 (Red): Synths and instruments
- Collection 2 (Orange): Distortion and saturation
- Collection 3 (Yellow): EQ and dynamics
- Collection 4 (Green): Reverb and delay
- Collection 5 (Blue): Creative effects
- Collection 6 (Purple): Utilities and analysis
- Collection 7 (Gray): Battle favorites (your go-to chain)
Create Audio Effect Racks
Group your most-used plugin chains into Ableton Audio Effect Racks. Select multiple plugins on a track, right-click, and choose Group to Audio Effect Rack (Cmd+G on Mac, Ctrl+G on Windows). Save the rack to your User Library. Now you can load an entire processing chain with a single drag-and-drop.
Plugin Setup for Battle-Ready Sessions
When a beat battle starts, every second counts. Your plugin setup should be optimized so you never waste time searching for or configuring plugins during a session.
Build a Battle Template
Create a default Ableton Live Set with your most-used plugins pre-loaded on tracks. Include a drum rack with your favorite kit, a bass track with your preferred synth, a melody track, and a sample track. Pre-load your standard plugin chain on each track. Save this as your default template by going to File > Save Live Set as Default Set on Mac or File > Save Live Set as Default Set on Windows.
Pre-Scan Before Battle Day
Run a full plugin rescan a day before any battle session. This ensures all your plugins are indexed and no scan delays slow down your start. Scanning mid-session because you installed a new plugin breaks your creative flow.
Frequently Asked Questions
Where does Ableton look for VST plugins by default?
On Mac, Ableton scans /Library/Audio/Plug-Ins/VST/ for VST2 and /Library/Audio/Plug-Ins/VST3/ for VST3. Audio Units are in /Library/Audio/Plug-Ins/Components/. On Windows, Ableton scans the custom folder path you set in Preferences > Plugins for VST2, and C:\Program Files\Common Files\VST3\ for VST3 by default. You can add a custom VST2 folder in Preferences.
Should I use VST2 or VST3 in Ableton?
Use VST3 whenever available. VST3 plugins are more CPU-efficient because they stop processing when receiving silence, they support dynamic I/O configurations, and they install to standardized folder locations. VST2 is a legacy format that some older plugins still use. If a plugin offers both formats, install VST3 and ignore VST2.
Why did Ableton block my plugin during scanning?
Ableton blocks plugins that crash during the scan process. This usually happens with 32-bit plugins in 64-bit Ableton, corrupted plugin files, or plugins with copy protection that fails to validate. Check Preferences > Plugins and look for a Crashed Plugins list. Try reinstalling the plugin, updating it to the latest version, or contacting the developer for a compatible build.
Can I use the same plugins in Ableton on both Mac and Windows?
Most plugin licenses cover both platforms. You install the Mac version (VST3 or AU) on your Mac and the Windows version (VST3 or VST2) on your PC. Your Ableton projects will load the correct format automatically as long as the same plugin is installed on both systems. Presets and settings are generally cross-compatible.
How many plugins can I install before Ableton slows down?
The number of installed plugins does not slow down Ableton. Only plugins that are actively loaded on tracks in your current session use CPU and RAM. Having 200 plugins installed but only using 10 in your project is fine. The plugin scan at startup may take longer with many plugins installed, but this only happens once per session or when you manually rescan.
