Yes, you can use third-party audio plugins in Final Cut Pro. The confusion is that Final Cut takes one plugin format and ignores the other, and when a plugin does not appear there is no error message telling you why.
Everything here applies to Final Cut Pro on macOS, Apple Silicon and Intel.
The same answer in two and a half minutes, if you would rather watch it. Everything in the video is written out below.
Final Cut Pro loads Audio Units. It does not load VST or VST3, ever, and there is no setting that changes that. Audio Units is Apple's own plugin format, so anything that works in Logic Pro or GarageBand will generally work in Final Cut too.
If a developer sells you a VST3 and nothing else, it cannot be used in Final Cut. If they ship an AU as well, and most Mac developers do, you already have what you need.
Premiere Pro and DaVinci Resolve both host AU and VST on macOS. Final Cut is the strict one. So when you are buying, the format to check for is AU, and it covers you across all three.
An installer will put them in one of two places. Both are valid and Final Cut reads both.
| Location | Path | Applies to |
|---|---|---|
| System wide | /Library/Audio/Plug-Ins/Components |
Every user on the Mac. Needs an admin password to install |
| Just you | ~/Library/Audio/Plug-Ins/Components |
Your account only. No password needed |
The file itself ends in .component. If you want to check a plugin actually
landed, open Finder, press Shift+Cmd+G, paste one of those paths and look. The
~/Library folder is hidden by default, which is why people often think an install
failed when it did not.
Select an audio clip, open the Effects browser (Cmd+5), and choose the Audio category. Third-party Audio Units are grouped by manufacturer name, not by product name. That trips people up constantly: you bought a plugin called Halo and you are scrolling for H, but it is filed under the company that made it.
Final Cut validates every Audio Unit before it will list it. A plugin that fails validation is silently hidden. Work through these in order.
Final Cut scans for Audio Units at launch. Installing a plugin while it is running does nothing until you restart it. This alone fixes most cases.
Look for the .component file in one of the two paths above. If all you can find
is a .vst3, that is the whole problem and no amount of rescanning will help.
Final Cut runs natively on Apple Silicon. An Intel-only plugin will not load into it, even
though the same plugin works fine in an app running under Rosetta. Select the
.component in Finder and press Cmd+I: under General it will say Universal, Apple
Silicon, or Intel. You want Universal or Apple Silicon.
macOS ships a command line tool that tells you exactly why an Audio Unit was rejected. Open
Terminal and run auval -a to list every Audio Unit the system can see. If your
plugin is not in that list, the problem is the install or the architecture, not Final Cut. If
it is in the list but still missing from Final Cut, copy its four-character codes from that
output and run auval -v aufx CODE MANU to see the failure in full.
macOS caches Audio Unit registrations, and a bad cache entry survives reinstalls. Quit
Final Cut, then in Finder use Shift+Cmd+G to go to
~/Library/Caches/AudioUnitCache and move that folder to the Trash. It rebuilds
itself on next launch. Nothing is lost.
Since macOS Catalina, an unsigned or unnotarized plugin can be blocked by Gatekeeper before Final Cut ever sees it. If you got a security warning during install, that is the cause. Any plugin from a real developer will be signed and notarized and will install silently.
Final Cut has no aux or bus structure the way a DAW does. Audio effects go on clips. If you want one instance of a plugin treating several clips, select them and make a compound clip (Option+G), then put the effect on the compound. That is the closest thing to a bus you get, and it is the single most useful workaround in this list.
Final Cut does not route MIDI to plugins and does not offer sidechain inputs. So a MIDI-controlled instrument or a ducking compressor that needs to listen to the dialogue track will not work as designed. Effects that just process the audio in front of them are fine, which covers EQ, reverb, compression, saturation and spatial tools.
You can keyframe an Audio Unit's parameters in the inspector, but it is one lane at a time and it is drawn by hand. There is no plugin-side automation recording. Worth knowing before you plan an effect that needs three parameters moving together.
Some plugins store presets in their own format inside the plugin rather than in the Final Cut project. Moving a project to another machine can lose them. If a plugin has an option to save its state with the host, use it.
Final Cut's built-in audio effects cover more than people assume. Channel EQ, the compressor, Space Designer and the noise reduction are all inherited from Logic and they are good. Before buying anything, the honest answer is that most editors need one or two things Final Cut genuinely lacks rather than a whole bundle.
The gaps that come up most often: proper dialogue repair, a de-esser you can actually see, loudness metering that matches broadcast delivery, and anything spatial beyond a reverb.
THALM is an Audio Unit that puts music into a real space: the next room, down the hall, out on the street, inside a passing car. You set a place on a building cutaway rather than dialling filters, and the walls, floors, distance and doorway do the work. It also handles the thing described above as a limitation: instead of keyframing three parameters, you arm a record mode, press play, and drag the music through the building while the scene runs.
Universal binary, signed and notarized, so it installs and validates without any of the trouble on this page. If you want the technique rather than the plugin, the manual method is written up here, free.
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