Yes, Pro Tools loads third-party audio plugins, but it takes one format and ignores every other one. The catch is that Pro Tools reads AAX only, not VST or AU, and when a plugin does not appear there is usually no error telling you why.
Paths shown are macOS unless noted; the Windows path is called out where it differs.
No. Pro Tools does not load VST, VST3 or Audio Units, and there is no setting that changes
that. It reads one format only: AAX, which stands for Avid Audio Extension and
is Avid's own plugin format. The file itself is a .aaxplugin bundle.
So if a developer sells you a VST3 or an AU and nothing else, it cannot run in Pro Tools at all. If they also ship an AAX, and most established developers do, you already have the version you need. There are a few AAX plugins that can host a VST or AU inside themselves, but that is a workaround, not Pro Tools reading those formats directly.
AAX is a Pro Tools thing and nothing else uses it. Final Cut Pro takes AU only, while Premiere Pro and DaVinci Resolve take AU and VST. So a plugin you bought for one of those does not automatically cover Pro Tools, and an AAX does not help you in them. The format that covers you in Pro Tools is AAX, full stop. If you also cut video, the Final Cut guide and the Resolve guide cover those.
Pro Tools needs AAX, and an AAX plugin installs in a single system folder that is the same on
every Mac, with one matching folder on every PC. An installer normally puts the
.aaxplugin in the right place for you. If you are copying one by hand, these are the
folders Pro Tools reads.
| Platform | File | Folder Pro Tools reads |
|---|---|---|
| macOS | .aaxplugin |
/Library/Application Support/Avid/Audio/Plug-Ins |
| Windows | .aaxplugin |
C:\Program Files\Common Files\Avid\Audio\Plug-Ins |
Do not drop a plugin into your Audio Units or VST folders and expect Pro Tools to see it.
It never will. Pro Tools looks in the Avid folder above and nowhere else, and it only accepts
the .aaxplugin file. Unlike Audio Units, there is no separate per-user version of
this folder, so it is one system-wide location and writing to it needs an admin password.
Nearly always it is one of five things: the plugin is not AAX, it has not been authorized yet, Pro Tools was open when you installed it, the file is in the wrong folder, or it is not properly signed. Pro Tools scans for AAX plugins at launch and validates each one before it will list it, and anything that fails is quietly left out. Work through these in order.
Pro Tools looks for plugins only when it starts. Installing one while it is running does nothing until you fully quit and reopen. This alone fixes most cases, so do it first.
Look for the .aaxplugin file. If all you can find is a .vst3,
a .dll, a .vst or a .component, that is the whole problem,
and no amount of rescanning will make it appear. You need a build in AAX format.
Many AAX plugins are licensed through iLok. If the licence has not been activated, Pro Tools can hide the plugin, or list it as failed to load with a message that it is "not a valid AAX plug-in". That message is misleading; the real cause is usually the missing authorization. Open iLok License Manager and confirm the licence for that plugin is present and active.
Confirm the file is in /Library/Application Support/Avid/Audio/Plug-Ins on a
Mac, or the Common Files Avid folder on Windows. A plugin sitting in any other location, or in a
home-folder plug-ins folder, will simply never be found.
Every AAX plugin has to be signed through PACE before Pro Tools will load it, whether or not it uses iLok copy protection. An unsigned or badly signed build is rejected on scan. Anything from a real developer is already signed and will install and load with no warning.
Pro Tools keeps a cache of the plugins it has already scanned, and a stale entry can survive a reinstall. A full quit and relaunch rebuilds that cache. Some plugin makers document deleting a specific AAX cache file to force a fresh scan; follow the maker's own instructions for that rather than guessing the path, since it moves between versions of Pro Tools.
Once an AAX plugin has scanned in, it lives on your track inserts. Click an empty insert slot at the top of a channel in the Mix or Edit window and pick the plugin from the menu. Pro Tools can list them grouped by category, such as EQ or Dynamics, or by manufacturer, and you can switch between those two views.
That manufacturer grouping is what trips people up most: you bought a plugin called Halo and you are scrolling for H, but it is filed under the company that made it. If you cannot find one you know installed correctly, switch the insert menu to sort by category and it usually turns up in the obvious place.
Pro Tools gives you the room to record, edit and mix, but it will not write a part for you. The thing most people actually get stuck on is not a missing effect, it is the blank track: the session is open, the drums are down, and the bassline is a flashing cursor. That is a writing problem, not a mixing one, and no reverb or compressor fixes it.
REHEAT writes basslines that write themselves. You point it at a key and it generates a line you can shape, then you drag the MIDI straight into your Pro Tools session, or play it live through your own synth with the built-in REHEAT MIDI DRIVER. It ships as an AU, a VST3 and an AAX for Pro Tools, all signed and notarized, so none of the trouble on this page applies to it.
Hear the whole thing free in your browser first, no install and no account.
We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.
Tunary