Logic Pro Plugins Not Showing Up: AU Validation Fixes

I opened a session last week and three plugins were gone from the effects list. Not grayed out, not disabled. Gone, like they'd never been installed. Logic Pro plugins not showing up usually traces back to one of a few places: the wrong plugin format, a slot you're not looking in, AU validation itself, a stale Plug-in Manager cache, or macOS blocking a file you just downloaded.

Tested with Logic Pro 12.3 on macOS 15.6 on an Apple silicon Mac. Menu names and the Apple Support steps below were rechecked on July 19, 2026, since Apple's own wording shifts slightly between versions and support articles.

Most threads on this tell you to restart your Mac and hope. That works sometimes. When it doesn't, work through the checks below roughly in order, starting with the two things people skip because they assume the plugin is already installed correctly.

Logic Pro: Confirm You Installed the Audio Unit Version

Logic Pro doesn't load VST or VST3 plugins directly. It only recognizes Audio Units, so the first thing worth checking is whether the installer you ran shipped an AU build in the first place.

AUv2 plugins normally install to /Library/Audio/Plug-Ins/Components or ~/Library/Audio/Plug-Ins/Components. AUv3 Audio Unit Extensions are installed in the Applications folder as app-based extensions rather than as standalone .component files in the Components folder.

Also confirm that the Audio Unit is 64-bit. Modern Logic Pro versions do not load 32-bit plugins, even if a .component file is present in the correct folder. This is worth ruling out early if the plugin is older or hasn't been updated in a long time.

If you downloaded a plugin from a developer's site and it only shipped a VST or VST3 build (common for plugins built primarily for Windows or other DAWs), Logic Pro will never see it, no matter how many times you rescan. Check the developer's download page for an AU or Audio Unit version before troubleshooting anything else here.

If you installed or updated the Audio Unit recently, restart the Mac once before resetting anything. Logic normally validates new and updated plugins automatically, but a full restart can complete installation or background registration steps that a Logic-only relaunch does not.

Logic Pro Plugins Not Showing Up: What AU Validation Checks

Logic Pro validates Audio Units automatically the first time it opens, after Logic Pro itself is updated, and when you install or update a plugin. Later launches generally use the stored validation result unless Logic detects a change or you force a rescan yourself.

What the validation checks in detail isn't published by Apple, so the safest way to describe it is this: Logic uses Audio Unit validation to determine whether a plugin complies closely enough with Apple's Audio Units specification to be enabled normally. A plugin that fails may still appear in Plug-in Manager with a compatibility warning, while remaining unavailable from the Insert menu until it passes validation or is manually enabled.

Most tutorials treat this as a plugin problem. It's not, not always. Logic-side validation results are managed in Plug-in Manager, although the underlying cause may still be the plugin's installation, authorization, architecture, or macOS compatibility.

Logic Pro Plug-in Manager: Reading the Compatibility Column

Open it from Logic Pro > Settings (or Preferences, depending on which version you're running) > Plug-in Manager. Click a manufacturer's name on the left to filter the list, then look at the status shown for each plugin. The exact wording varies. Apple's support articles use terms like failed validation and not authorized, while the Plug-in Manager interface in Logic Pro 12.3 shows a checkmark, a not compatible flag, or a count of unexpected terminations, depending on the version you're running. Don't assume one fixed set of labels applies everywhere.

Two states are easy to miss and explain a lot of "it validated fine but I still can't find it" cases: Hide and Ignore. Hide removes a plugin from the Insert menu while still letting it load in existing projects that already use it. Ignore removes it from the menu entirely and stops Logic from scanning it at all. Both live in the Plug-in Manager alongside the Use column.

Work through it as a short diagnostic instead of memorizing labels:

1. Shows as validated with no issue, but missing from the menu: check the Use, Hide, and Ignore columns, and confirm the plugin's category.
2. Shows failed validation or not compatible: select it and click Reset & Rescan Selection.
3. Shows not authorized: fix the license or authorization with the plugin's own manufacturer tool first, then rescan. Rescanning cannot fix a missing or inactive license on its own.
4. Doesn't appear in the Plug-in Manager at all: confirm the installation first (see the AU-versus-VST check above), then use Full Audio Unit Reset.

I once spent time rescanning a plugin marked not authorized before realizing the real issue was its vendor's own license manager. Rescanning does nothing for a license problem. Authorize the plugin with the manufacturer's own tool first, then come back to Logic.

Logic Pro Reset and Rescan Selection for a Single Failed Plugin

Use this one only when the plugin appears in the Plug-in Manager marked failed validation or not compatible. If it's absent from the list entirely, skip ahead to Full Audio Unit Reset instead, since there's nothing in the list to select.

In the Plug-in Manager, Command-click to select the plugin (or plugins), then click Reset & Rescan Selection at the bottom of the window. Logic forces the selected Audio Unit through validation again and activates it automatically if it passes.

If the plugin fails validation again, check the developer's compatibility notes, authorization tool, current installer, and support page before repeating the rescan.

Logic Pro Full Audio Unit Reset When a Plugin Won't Reappear

If a plugin doesn't show up in the Plug-in Manager at all, a targeted rescan won't help, since there's nothing to select. Go to Plug-in Manager, click Full Audio Unit Reset in the lower left, then quit Logic Pro completely and reopen it. Logic rescans every installed Audio Unit from a clean state, which also resets Audio Units for MainStage if you use it on the same Mac.

This can take a while depending on how many plugins you have installed, and you won't be able to use any application that relies on Audio Units while it runs, not just Logic Pro.

It's the step people skip most, because it sounds drastic. It simply forces Logic to rescan every installed Audio Unit rather than only the selected plugin.

Logic Pro AudioUnitCache: Clearing a Corrupted Cache Manually

Save this one for last. In Finder, hold Option and choose Go > Library, then find the AudioUnitCache folder inside Caches. Move the files inside it to the Desktop instead of deleting them outright, in case you need to put them back, then restart your Mac. Every Audio Unit gets rescanned from zero, which is what you want if the cache itself is what's corrupted.

Logic Pro: Check the Right Plug-in Slot

A plugin can install correctly and pass validation, and still be invisible if you're looking in the wrong place for it. Software instruments only show up in the Instrument slot. Audio effects show up in Audio FX. MIDI-processing plugins show up in MIDI FX, a separate slot that's easy to forget exists.

Some developers also ship separate mono and stereo builds, and which one Logic offers depends on the channel strip's format. Check the Audio Effect, Instrument, and MIDI Effect slots, along with each manufacturer's submenu, before deciding a validated plugin isn't really installed.

Logic Pro Apple Silicon and Rosetta Compatibility

Logic Pro 12 requires a Mac with Apple Silicon and macOS 15.6 or later. That requirement is about which version of Logic Pro your Mac can run. It's a separate issue from AU validation, not a cause of it (see our full Logic Pro system requirements breakdown for what each hardware tier supports).

Rosetta matters here in a narrower way than most threads describe it. On an Apple silicon Mac, install Rosetta if Logic doesn't recognize an Intel-only Audio Unit, since Rosetta lets macOS run that plugin's Intel code. You normally don't need to run Logic Pro itself under Rosetta, and Apple recommends native mode for full feature access. Apple documents a small number of third-party ARA workflows, including certain Melodyne, VocALign, and Revoice Pro configurations, that may still require Logic Pro to run under Rosetta.

Logic Pro: Check macOS Privacy & Security if a Plugin Is Blocked

If macOS blocks the plugin installer or one of its components, the Audio Unit may not install or validate correctly. Check System Settings > Privacy & Security for a blocked-item message before repeatedly rescanning it.

Apple's own guidance for this is to download the plugin from a trusted, identified developer, confirm the release supports your macOS version, and install it using the developer's own signed installer rather than copying files by hand. Use Open Anyway in Privacy & Security only when you trust the developer and expected the installation.

Advanced users may encounter community instructions for removing a quarantine attribute manually. This bypasses part of macOS's normal security workflow and shouldn't be the standard fix. Use the developer's signed installer or the Privacy & Security controls instead. A fresh install through the developer's signed installer may resolve the issue without requiring Terminal.

Logic Pro Audio Units Safe Mode for Isolating a Crashing Plugin

If Logic won't open normally and you suspect a third-party Audio Unit is the reason, don't assume which plugin it is. Test the hypothesis instead. Hold Control while Logic Pro is launching and you'll get a choice: Launch, Don't Launch (disables Core Audio), or Launch Without Audio Units, which opens Logic with every third-party AU disabled.

If Logic opens normally in that mode, an Audio Unit is a reasonable suspect. Open a copy of the affected project, re-enable or remove third-party plugins in small groups, and replay the section that previously failed, working through the Plug-in Manager as you go. If Logic still won't open, the cause is more likely something else, like a specific project file, an audio interface, or damaged preferences, and it's worth ruling those out too.

There's a second startup modifier option worth knowing. Hold Shift-Control instead, and Logic opens in Audio Units safe mode, loading only plugins that already passed validation. Hold the keys down right after launching Logic, before the app has fully opened. There's no fixed amount of time it takes for the dialog to appear.

None of this touches audio problems that aren't about missing plugins. If Logic opens fine and every plugin loads but something else is wrong, that's covered in other Logic Pro audio and recording problems and fixing latency in Logic Pro instead.

Logic Pro Plugins Not Showing Up: Frequently Asked Questions

Does a Full Audio Unit Reset delete my installed plugins?

No. It forces Logic Pro to rescan all installed Audio Units. It does not delete the plugin files from the Components folders. You might see plugins that failed validation before come back as working, or the other way around, but nothing gets removed from disk.

Why does a plugin show as validated but still not appear on a track?

Open Plug-in Manager, select Show All, and check the Use, Hide, and Ignore columns for that plugin. Hide keeps it working in existing projects but removes it from the Insert menu. Ignore removes it from the menu entirely and stops Logic from scanning it. If it's enabled correctly and still missing, confirm you're looking in the right slot for its type, Audio Effect, Instrument, or MIDI Effect, then quit and reopen Logic Pro.

Is it safe to use a plugin after it fails AU validation?

Logic will sometimes let you override a failed validation and use the plugin anyway, and it often works without issue. That said, a failed validation means the plugin didn't pass Apple's checks, so you're accepting some risk of a crash mid-session. I wouldn't override it on a client session with a deadline. I might on a personal project where I can afford a crash.

How long does Logic Pro's AU validation take when the app first opens?

It depends on how many Audio Units you have installed and whether they're already cached from a previous scan. A first-time scan on a large collection takes noticeably longer than a normal launch with everything already validated, which adds almost no time at all.

Do I need to restart my Mac after clearing the AudioUnitCache folder?

Yes. Apple instructs you to restart the Mac after moving the AudioUnitCache files, then reopen Logic Pro or MainStage so the installed Audio Units can be scanned again.

Related guides: Logic Pro System Overload: How to Find and Fix the Cause · How to Fix Latency in Logic Pro · Logic Pro No Sound: Fixes

Sources: If you can't find a recently installed plug-in for Logic Pro — Apple Support · Use the Plug-in Manager in Logic Pro — Apple