If your plugins not showing up in your DAW after you installed them, the cause is almost always one of a handful of ordinary things: the plugin landed in a folder your DAW doesn’t scan, it’s in a format your DAW can’t load, the plugin scan simply hasn’t been re-run, or a mismatch between 32-bit and 64-bit (or Intel and Apple Silicon) is quietly blocking it. It’s frustrating, but it’s rarely a broken plugin. This guide walks through the reasons a plugin fails to appear and how to fix each one in a few minutes.
Violet Recording is reader-supported — we may earn a commission from links on this page, at no extra cost to you.
What “plugins not showing up” actually means
A DAW doesn’t magically know about every plugin on your computer. On launch (or when you tell it to), it scans specific folders, reads each plugin file, checks that it’s a compatible format and architecture, and builds a list. Anything that isn’t in a scanned folder, isn’t a supported format, or fails validation never makes it onto that list — so it looks like the plugin vanished. When plugins are not showing up, you’re really looking at a break somewhere in that scan-and-validate chain. Once you know the links in the chain, finding the broken one is quick.
Check the plugin format your DAW actually loads
Plugins come in several formats, and no DAW loads all of them. The common ones are VST2 and VST3 (Windows and macOS), AU (Audio Units, macOS only), AAX (Pro Tools only), and Apple’s CLAP, which newer hosts are adding. Logic Pro and GarageBand only see AU plugins — install a VST-only plugin and it will never appear, no matter how many times you rescan. Pro Tools only reads AAX. Ableton Live, FL Studio, Cubase, Studio One and Reaper generally read VST2/VST3, and the Mac versions usually read AU too.
So the first question is: does the installer offer the format your DAW needs? Most paid plugins let you tick which formats to install. If you installed the VST but you’re in Logic, re-run the installer and enable AU. If a plugin is genuinely only shipped as VST and you live in Logic, it simply won’t work there — that’s a compatibility limit, not a bug.
Point your DAW at the right plugin folder
Even the right format won’t load if it isn’t where the DAW looks. Operating systems and DAWs expect plugins in standard locations, and installers usually put them there — but not always, especially if you changed the install path.
On macOS, Audio Units live in /Library/Audio/Plug-Ins/Components, VST3 in /Library/Audio/Plug-Ins/VST3, and VST2 in /Library/Audio/Plug-Ins/VST (there are matching folders inside your user Library too). On Windows, VST3 has one standard home: C:\Program Files\Common Files\VST3. VST2 has no fixed location, so you set a custom VST2 folder — commonly C:\Program Files\VSTPlugins or C:\Program Files\Steinberg\VSTPlugins — and every DAW must be told to scan it.
In your DAW’s preferences, find the plugin manager (it goes by names like “Plug-In Manager”, “VST Plug-ins”, or “Plug-In Sources”) and confirm the folders it scans include where your plugin actually installed. Add the missing folder, and make sure your custom VST2 path matches the one the installer used. A single mismatched path is the most common reason a freshly installed plugin never appears.
Re-run the plugin scan (and clear the cache)
DAWs cache their plugin list so they don’t rescan everything on every launch. Install a plugin while the DAW is open and it usually won’t show until you rescan. Look for a “Rescan”, “Scan for new plugins”, or “Reset & Scan” button in the plugin preferences and run it. If the plugin still doesn’t appear — or shows up greyed out — force a full rescan that ignores the cache. Most hosts have an option to clear the cache or re-verify all plugins; in some, holding a modifier while launching triggers a clean scan. A clean rescan fixes a surprising number of “missing” plugins, because a half-finished earlier scan had blacklisted the file.
Look in the plugin blacklist and failed-validation log
When a plugin crashes or fails validation during scanning, the DAW quarantines it on a blacklist (sometimes called “failed” or “disabled” plugins) so one bad plugin can’t take down the whole program. A blacklisted plugin won’t appear in your insert menu even though it’s installed correctly. Open the plugin manager and look for a blacklist, failed, or disabled tab. If your plugin is there, you can usually re-enable and re-validate it. On macOS, Logic and GarageBand run Apple’s auval validation — an AU that fails auval stays hidden until it passes, which typically means installing an updated version of the plugin.
Match the architecture: 64-bit, and Apple Silicon vs Intel
Modern DAWs are 64-bit and load only 64-bit plugins. Ancient 32-bit plugins won’t show up in a current host without a “bridge”, and most DAWs dropped 32-bit support entirely — so an old freebie may simply be too old. On Apple Silicon Macs there’s a second layer: a DAW running natively in Apple Silicon mode can’t load an Intel-only plugin directly. The usual fix is to run the DAW in Rosetta mode (right-click the app, Get Info, tick “Open using Rosetta”) so it can load Intel plugins, or better, install a native/universal version of the plugin if the developer offers one. If a plugin appears in one DAW but not another on the same Mac, an architecture mismatch is the prime suspect.
Finish the install: activation, dependencies and permissions
Some plugins install but stay hidden until you complete a step. Many require their own manager or licence app — such as iLok, Native Access, or a brand’s own installer — to activate the licence and drop the plugin files in place. If you skipped that, the plugin may be unauthorised and hidden. A few plugins also install a support component or runtime they depend on; if that failed, the plugin won’t load. And on macOS, a plugin downloaded outside an installer can be blocked by Gatekeeper permissions — you may need to approve it in System Settings under Privacy & Security. Reinstall with the official installer, run the licence manager, and reboot before you rescan.
Where to get plugins that install cleanly
A lot of “missing plugin” pain starts with a messy download — a cracked or repackaged installer, or a file that never registered its licence. Buying from an established store means you get the official installer, the correct formats, and a download manager that handles activation and updates, which sidesteps most of the problems above. Plugin Boutique is a well-known marketplace that carries the major developers and bundles a manager to keep everything organised, and it regularly lists genuine free plugins worth grabbing.
If you’re building out a mixing chain, it helps to know what you’re shopping for before you install. Our roundups of the best compressor plugins, best EQ plugins and best reverb plugins cover reliable options, and if you want to understand how those tools work together, start with EQ and compression fundamentals. For putting them to use on a real track, see how to mix vocals, and browse more troubleshooting and technique in our mixing and mastering hub.
Frequently asked questions
Why do my plugins show up in one DAW but not another?
Usually a format or folder difference. The DAW that can’t see the plugin either doesn’t load that format (for example Logic ignoring a VST) or isn’t scanning the folder where the plugin installed. Architecture is the other cause: a plugin missing only on Apple Silicon typically needs Rosetta mode or a native build. Check the plugin manager in the DAW that’s missing it, confirm the scanned folders and formats, then rescan.
I reinstalled the plugin and it still won’t appear — what now?
Run a full rescan that clears the cache, then check the blacklist or failed-plugins tab, because a plugin that crashed during an earlier scan stays quarantined even after reinstalling. Confirm the licence is activated in the developer’s manager app, and on macOS approve the plugin in Privacy & Security if it was blocked. If it fails validation, install the newest version — an out-of-date plugin often fails on a current OS.
Do I need to restart my DAW after installing a plugin?
Yes, in most cases. DAWs read their plugin list at launch, so a plugin installed while the program is open won’t appear until you either rescan or restart. Restarting is the simplest way to trigger a fresh scan. If it still doesn’t show after a restart, the problem is a folder, format, architecture or validation issue rather than a timing one.
