How to Install Plugins in Logic Pro: AU Setup
Install third-party Audio Units in Logic Pro, verify the component or extension, confirm Plug-in Manager validation, and load it in the correct slot.
To install plugins in Logic Pro for Mac, use the developer’s Audio Units build. Logic has no internal “install plug-in” button: download the Mac installer from the developer, include the AU or Audio Units option, finish any license authorization, then reopen Logic. Check the new plug-in in Logic Pro > Settings > Plug-in Manager before you try to use it.
If the download offers VST, VST3, AAX and AU, Logic needs AU. Install only VST3 and the plug-in won’t show up in Logic at all. This guide covers Logic Pro for Mac. The old name “Logic Pro X” still turns up in older documentation and search results, but the installation route is the same Audio Unit workflow.
Last verified: August 26, 2026, against Apple’s current Logic Pro User Guide, the Logic Pro 12.3.1 release notes and Apple Support guidance.
Choose the right plug-in format before downloading
A vendor may package several formats in one installer. Pick the Mac build the developer says is compatible with your macOS version, your Mac processor and the current Logic Pro release. Then include AU in the format list. If you haven’t chosen the software yet, the free and paid Logic Pro plug-in guide separates useful free and paid choices from tools that duplicate strong stock options.
| Format in the installer | Will Logic Pro for Mac load it? | What to do |
|---|---|---|
| AU / Audio Units / AUv2 | Yes | Install this format for Logic. |
| AUv3 / Audio Unit Extension | Yes, when the extension supports Mac | Install the app or extension as the developer instructs. |
| VST or VST3 | No, not directly | Choose AU as well; VST3 alone is for other hosts. |
| AAX | No | This is not the Logic plug-in format. |
| Standalone app | Not by itself | Confirm the package also includes an AU component or AUv3 extension. |
Do not assume that a plug-in is compatible because the product page says “Mac.” Check that the current build is a 64-bit Audio Unit and that the developer supports your macOS version, Logic release, Mac processor and license manager. Apple’s current missing-plug-in guidance is blunt about it: 32-bit plug-ins are not compatible with Logic Pro or MainStage. Apple also tells users to follow the developer’s installation instructions and confirm compatibility with the latest Logic version in its Audio Units guide.
How to install a plug-in in Logic Pro
- Quit Logic Pro. Finish the installation before reopening the app.
- Download the installer from the plug-in developer or its authorized account page. Avoid repackaged installers from download sites.
- Choose the Mac version and include AU or Audio Units. You can omit formats you do not use unless another DAW on the Mac needs them.
- Run the vendor installer. Keep its default AU destination unless the developer documents a different method. Complete any required sign-in, serial, license-manager or hardware authorization.
- Reopen Logic Pro and let validation finish. Do not force-quit the app while the new Audio Unit is being scanned.
- Open Logic Pro > Settings > Plug-in Manager. Search by plug-in or manufacturer and confirm that the Compatibility column has a checkmark.
- Load it from the correct slot. Use an Audio Effect slot for processors such as EQ, compression, reverb and delay; use the Instrument slot for a synth, sampler or drum instrument.
- Test and save. Pass audio through an effect or play notes into an instrument, change one obvious control, save a small test project, close it and reopen it to confirm the plug-in and its setting recall correctly.
The final test matters. A plug-in can appear in the menu yet still be unauthorized, fail to produce sound or forget its state. Finding that in a disposable project is safer than discovering it inside an important mix.
If the installer gives you a .component file
Install most commercial plug-ins with the developer’s package. It may also place presets, support files and license components. Use manual placement only when the developer supplies a standalone .component file and explicitly supports that method.
Apple documents two Audio Unit component folders:
/Library/Audio/Plug-Ins/Components: the system Library, normally used when the plug-in should be available to users of that Mac.~/Library/Audio/Plug-Ins/Components: the current user’s Library. The tilde means your home folder.
In Finder, choose Go > Go to Folder, paste the exact path, then move the vendor-supplied component there. Reopen Logic and check Plug-in Manager. Apple’s Audio Unit folder reference confirms both locations, and it also notes that Logic’s built-in effects and instruments don’t appear in these folders.
Keep the AUv2 .component in one of those scanned Library folders. A vendor may let you park its sample library, presets or other content on an external drive, but that doesn’t move the component itself. Use the vendor’s content-location control instead of dragging installed plug-in files by hand.
AUv3 works differently: Apple’s current guide says Audio Unit Extensions are installed in the Applications folder, while AUv2 plug-ins use the Components directory. Do not drag an AUv3 app bundle into the Components folder.
Confirm that Logic validated the plug-in
Open Logic Pro > Settings > Plug-in Manager. Select the manufacturer on the left, or search for the plug-in name. Apple’s current Plug-in Manager guide says a checkmark in Compatibility means the scan found no issue, and not compatible means it found a problem. Two more states come from Apple’s support sequence: failed validation for an entry that should be rescanned, and not authorized when the vendor’s license step must be completed before another scan.
Also check that Hide and Ignore are not selected. Apple draws a line between them: Hide pulls a plug-in out of the channel-strip menu but still scans it, while Ignore stops it from appearing and being scanned.
Do not click Full Audio Unit Reset as part of a normal installation. If one installed entry needs another scan, select that entry and use Reset & Rescan Selection. If the plug-in is absent, unauthorized or repeatedly fails validation, follow the narrower Logic Pro missing plug-in diagnostic instead of deleting caches or bypassing macOS security at random.
Load an effect or instrument in the right place
Installation is complete only when you can load the Audio Unit on the correct kind of channel strip:
- Audio effects process a signal that already exists. Click an empty Audio Effect slot, open Audio Units, choose the manufacturer, then the plug-in.
- Software instruments create sound from MIDI. Create or select a Software Instrument track, click its Instrument slot, then choose the Audio Unit instrument.
- MIDI effects belong in a MIDI Effect slot only when the developer supplies that type of Audio Unit.
A synth won’t appear in an audio-effect menu, and a compressor won’t appear in the Instrument slot. That’s a menu-location problem rather than an installation failure. Apple’s plug-in slot reference uses the same Audio Effect and Instrument distinction.
Apple silicon, Intel plug-ins and Rosetta
Prefer a current Apple-silicon or universal build when the developer offers one. If the only supported build is an Intel Audio Unit, Apple says an Apple-silicon Mac needs Rosetta installed before Logic can recognize that plug-in. That does not mean you should run Logic itself with “Open using Rosetta” for every older plug-in.
Apple says Logic generally should not need to run under Rosetta. Some third-party ARA software is a separate exception. Check the developer’s current compatibility page first, then use Apple’s Apple-silicon Audio Unit guidance if the supported plug-in specifically requires Rosetta.
If the new plug-in does not appear
Keep the first checks narrow:
- Confirm that the AU build was installed rather than a VST3-only or AAX-only build.
- Check the Audio Effect slot for an effect and the Instrument slot for an instrument.
- Search the correct manufacturer in Plug-in Manager.
- Finish the vendor’s authorization and confirm current macOS and Logic compatibility.
- Restart the Mac once. Apple’s recently installed plug-in support page puts a restart before rescans and full resets.
- If the entry exists but failed, select only that plug-in and use Reset & Rescan Selection.
Stop there before broad resets. The complete missing Audio Unit troubleshooting path covers validation states, authorization, Full Audio Unit Reset, startup isolation and cache removal in the order that limits collateral damage.
Logic Pro plug-in installation FAQ
Can Logic Pro use VST or VST3 plug-ins?
Logic Pro for Mac does not load VST or VST3 directly. Install the Audio Units version supplied by the same developer. A multi-format installer can place AU for Logic and VST3 for another DAW on the same Mac.
Where is the Logic Pro plug-in folder?
Third-party AUv2 components can be in /Library/Audio/Plug-Ins/Components or ~/Library/Audio/Plug-Ins/Components. AUv3 Audio Unit Extensions are installed in Applications. Logic’s built-in effects and instruments are not stored as removable files in those third-party Components folders.
Do I need to restart Logic or the Mac after installing a plug-in?
Finish the installation with Logic closed, then reopen it so the new Audio Unit can be validated. A full Mac restart is not required after every successful installation, but Apple recommends restarting as the first check when a recently installed plug-in does not appear.
Why does my synth not appear in the Audio Effect menu?
A synth is an instrument, so load it on a Software Instrument track from the Instrument slot. Audio Effect slots list processors such as EQ, compression, saturation, reverb and delay.
Should I put a .component file in the system Library or user Library?
Follow the developer’s supported installation method. When manual placement is explicitly supported, /Library/Audio/Plug-Ins/Components makes the component available at the system level, while ~/Library/Audio/Plug-Ins/Components is inside the current user’s home Library. Do not manually split a vendor package unless its documentation tells you to.
How do I know whether Logic accepted the plug-in?
Open Logic Pro > Settings > Plug-in Manager, find the manufacturer or plug-in, and check Compatibility. A checkmark means Logic’s scan found no issue. Then load the plug-in in a small test project, pass audio or MIDI through it, save, close and reopen the project to confirm recall.
If this is your first third-party Audio Unit, the Logic Pro beginner project gives you a clean test session with audio and software-instrument tracks already explained. The ordered Logic Pro tutorials hub connects installation to recording, editing, mixing and export without turning this page into a generic plug-in list.
