Use Audio Units (AU) on a Mac if you work in Logic or GarageBand, because those apps load only AU. Use VST3 if you work in a cross-platform host or share projects with Windows users. Most other DAWs on a Mac load both.
Format basics
- VST3: the successor to VST, released in 2008. VST was created by Steinberg in 1996. The VST2 SDK stopped being distributed in 2018, so new developers can’t legally build VST2 plugins.
- AU (Audio Units): Apple’s format, for macOS only. Logic Pro and GarageBand load only AU.
- AUv3: the app-extension version of AU, used on iOS and iPadOS and supported on macOS.
- AAX: Avid’s format, required by Pro Tools.
- CLAP: an open format launched in 2022 by Bitwig and u-he.
Typical install locations:
- AU on macOS: /Library/Audio/Plug-Ins/Components
- VST3 on macOS: /Library/Audio/Plug-Ins/VST3
- VST3 on Windows: C:\Program Files\Common Files\VST3
Which DAW loads which format
- Logic Pro and GarageBand: AU only.
- Cubase and Nuendo on Mac: VST and VST3, not AU.
- Pro Tools: AAX only.
- Ableton Live, Studio One, REAPER and FL Studio on Mac: both AU and VST3. REAPER also supports CLAP, and the FAQ in the audio interface setup guide covers loading plugins there. In Ableton, Preferences > Plug-ins has a “Use Audio Units” toggle that hides duplicates.
For a Mac-focused comparison, see which is better for Mac, VST or AU.
“Updating information about Audio Unit plug-ins”
Logic and GarageBand validate AU plugins when they launch, especially after an install or an update. This message is usually harmless, but a slow or stuck scan can hold up your session.
Try these fixes in order:
- Open Logic’s Plug-in Manager and rescan.
- If the scan is still slow or stuck, delete the AudioUnitCache folder in ~/Library/Caches, then relaunch.
A plugin that fails validation stays disabled in Logic until it’s re-validated in Plug-in Manager.
Bridging plugins
Bridging runs a plugin in a separate process, so a crash in the plugin doesn’t take down the whole session. In FL Studio on Windows, bridging is used for 32-bit plugins in a 64-bit host.
FL Studio’s “Make bridged” option can isolate an unstable plugin. The cost is a small amount of extra CPU and latency. If you bridge a plugin and the bridged setting doesn’t stick between instances, check the current FL Studio version, as this has been reported as a bug.
Bridging is a compatibility workaround, not a speed boost. If a plugin is unstable, the developer’s update is usually the real fix.
Apple Silicon and old plugins
Intel-only plugins on Apple Silicon usually need the host to run under Rosetta 2. Whether bridging works this way depends on the DAW. Also, 32-bit plugins don’t run on macOS Catalina (10.15) and later. If you depend on an old 32-bit plugin, look for a 64-bit update or a replacement.
Common misconceptions
- VST3 and AU versions of the same plugin normally sound identical. They share the same DSP code in most cases.
- Switching a plugin’s format breaks saved projects. Unless the host maps the settings, the instance’s settings won’t carry over.
- Cubase doesn’t load AU, and Logic doesn’t load VST. Check your DAW’s format support before buying.
- Bridging makes a plugin faster. It’s for compatibility and stability.
- Installing both formats is harmless. It is, but it clutters your plugin list.