VST3 vs AU vs AAX vs CLAP: Which Plugin Format Do You Need?

Audio plug-in format guide

VST3, AU, AAX and CLAP are plug-in formats—the connection layer between a plug-in and your DAW. The right choice depends mainly on the DAW and operating system you use, not on which format “sounds better.” Use the quick table below to choose the installer options you actually need.

Which plug-in format does your DAW need?

This is the practical answer for common production setups. Always check the current requirements for your exact DAW version before buying or installing, especially on an older operating system.

VST3 vs AU vs AAX vs CLAP

VST3: the broad cross-platform default

VST3 is Steinberg’s current plug-in format and the most useful default for many Windows and cross-platform setups. It is supported by major DAWs including Cubase, FL Studio, Ableton Live and REAPER. On macOS, many of those same DAWs can load VST3 as well.

A VST3 file normally ends in .vst3. Modern installers place it in a standard system folder, so accepting the developer’s default location is usually safer than inventing a custom path. VST3 is not the native choice for Logic Pro or Pro Tools: those hosts require AU and AAX respectively.

AU: Apple’s Audio Unit format

Audio Units are Apple’s plug-in standard for macOS. Choose AU for Logic Pro and GarageBand. Ableton Live and some other Mac DAWs can also host AU, which is useful in an all-Mac workflow.

Traditional macOS Audio Unit plug-ins commonly use the .component extension. AU is not a Windows format, so a collaborator on Windows cannot load that AU instance. If the same project must move between Mac and Windows in a DAW such as FL Studio, a matching VST3 build is often the more portable choice.

AAX: the Pro Tools format

AAX is Avid’s plug-in format for Pro Tools and other Avid environments. If Pro Tools is your DAW, install the AAX version. AAX files commonly use the .aaxplugin extension on macOS and Windows.

Installing only VST3 will not make a plug-in appear in Pro Tools. Likewise, installing AAX does not make it available inside Logic, Ableton Live or FL Studio. Many commercial installers include several format checkboxes because the underlying product is shipped in multiple wrappers.

CLAP: open, modern and growing

CLAP—CLever Audio Plugin—is an open audio plug-in interface designed around a stable application binary interface and an extension system. Its specification includes facilities for parameter handling, note ports, preset discovery and deeper host integration.

Hosts including Bitwig Studio, REAPER and current FL Studio versions support CLAP. But support is not universal, so do not choose CLAP simply because it is newer. Your DAW and the specific plug-in must both provide compatible CLAP support. When they do, CLAP can be an excellent choice; when they do not, VST3 remains the practical cross-platform default.

Does VST3 sound better than AU, AAX or CLAP?

No format is inherently “higher quality.” The format defines how the plug-in communicates with its host. When a developer uses equivalent processing code and settings across formats, the audio result should be equivalent. A difference you hear is more likely to come from a changed preset, oversampling setting, channel configuration, DAW gain structure, automation or a format-specific implementation issue—not from the letters in the filename.

On Mac, should you install AU or VST3?

Also check Apple silicon support. AU versus VST3 does not tell you whether the plug-in runs natively on Apple silicon. Look for a current universal or native Apple silicon build from the developer; otherwise the DAW may require a compatibility mode.

What about VST2?

VST2 remains relevant for older products and sessions, but VST3 is the better default for a new installation when both are available and your DAW supports it. Do not remove an old VST2 build before opening and checking important archived projects. A DAW may treat VST2 and VST3 as different plug-ins, so swapping formats does not always restore the saved state automatically.

This matters in collaboration too. Two producers can own the same synth, yet the session may still report it missing if one person used AU and the other installed only VST3. Agree on the same format, version and architecture before exchanging active sessions.

Should you install every format?

Usually no. Install the format or formats required by the DAWs you actually use. A smaller, deliberate installation reduces duplicate browser entries and makes troubleshooting easier.

• One DAW: install its preferred format only.
• Logic plus Ableton on Mac: AU can cover both, or use AU in Logic and VST3 in Ableton if that is your established workflow.
• Pro Tools plus another DAW: install AAX plus the other DAW’s preferred format.
• Mac/Windows collaboration: use VST3 where both versions of the DAW support it.
• Legacy sessions: keep the older format until the projects and saved states have been verified.

Preset and sample-library installation is a separate question. A Serum bank, for example, belongs in Serum’s content folder rather than any VST3, AU or AAX directory. See how to install Serum 2 presets and banks for the correct workflow.

Why is an installed plug-in missing from your DAW?

Check these in order; the first three solve a large share of missing plug-in reports.

1. Format: confirm that you installed one your DAW hosts. Logic needs AU; Pro Tools needs AAX.
2. Operating system: a Windows installer will not work on macOS, and AU is Mac-only.
3. Architecture: confirm 64-bit and, on modern Macs, Apple silicon or a supported compatibility path.
4. Install location: rerun the official installer and accept its standard format folder.
5. Scan: use the DAW’s plug-in manager to rescan. A failed validation may appear in a blocked or excluded list.
6. License: finish authorization in the developer’s app or license manager if required.
7. Version compatibility: verify the minimum DAW and operating-system requirements on the product page.

A custom scan folder is mainly relevant to older VST2 plug-ins. VST3, AU, AAX and CLAP generally have established system locations, and moving their files by hand can make updates and uninstallers unreliable.

See plug-in formats on real products

These ProducerSources products list their supported systems and formats on their individual pages. Use those compatibility sections as your final pre-purchase check.

Frequently asked questions

Official references