A plugin format is the interface through which a host loads a plugin. It is not a quality rating. The letters on the installer are less exciting than a new sound, but checking them first can save an evening of wondering why the new sound is missing.
Start with your DAW
Apple documents third-party Audio Units in Logic Pro. Ableton Live on macOS supports AU and VST formats, with details that depend on the Live and macOS versions. Its AU and VST guide explains the differences and installation locations.
For another host, use its own documentation. Do not choose a format because a video used it in a different DAW. Make a short compatibility note with your operating system, processor, DAW version and the format you intend to use.
Check more than the format name
A supported format is one requirement, not the whole compatibility check. Confirm the plugin's minimum OS, supported processor architecture, host requirements and available installer. An Apple Silicon build and an Intel build are not interchangeable merely because both files say VST3.
Ableton specifically notes that native Apple Silicon Live needs native Apple Silicon VST plugins. Requirements can change with updates, so check the developer's current support information for the exact version you are installing.
Before a major project deadline, keep the version that already works. Make a separate test session for updates. Open the plugin, save, close and reopen that session before changing a project you need to deliver tomorrow.
Think about the other computer
AU is a macOS format. For an Ableton project that needs to move between Mac and Windows, Ableton recommends VST and matching plugin versions on both machines. That still requires a compatible build and license on each computer.
Agree on the format before a collaboration grows to fifty tracks. Write down the plugin name, version and format in the project notes. A shared brand name alone does not describe what the session expects to load.
Send audio renders when the recipient only needs to hear or mix the part. They do not need your entire instrument collection just to hear a bass line. Our project archive guide covers keeping editable versions alongside those renders.
Install only what you need
- Download from the developer and read the install instructions for that release.
- Select the supported formats you actually use. Let the installer handle their locations.
- Open the host and enable or rescan the relevant plugin source using its documented process.
- Test in a new session before opening an important project.
- Keep the working version and your compatibility note with the project archive.
If it does not appear, check compatibility and scan results before moving random files around. Reinstalling the wrong architecture six times remains the wrong architecture, with extra clicking.
Common questions
Does VST3 automatically sound better than AU?
No format label guarantees a sonic improvement. Compare the actual implementation and features documented by the developer, then test it in your host.
Can I replace AU with VST3 in an existing project?
Do not assume the host will transfer the saved state automatically. Keep the original session, save the settings and test a replacement on a copy. Render important parts before changing the format.
