VST Plugin Not Showing in Your DAW? Fix Paths, Formats & Rescan

Why Your Plugin Disappears After Install

You ran the installer, the progress bar finished, and the plugin still is not in the browser or "Add plugin" menu. That is normal host behavior — not proof the install failed. DAWs keep an internal plugin database. They do not watch your drive in real time, so a new .dll, .vst3, or .component only appears after a rescan or restart once the file is in a folder the host actually scans.

Before you reinstall for the third time, walk the failure modes in order: wrong path, wrong format, architecture mismatch, blacklist / failed scan, then rescan procedure. Full folder maps live in where VST plugins are stored; pure rescan menus live in how to rescan VST plugins. This guide is the diagnostic path between those two.

Also confirm you installed the OS-correct build. Windows and macOS VST binaries are not interchangeable — Image-Line states they are separate installers and not cross-compatible^[2].

• Path problem Plugin landed in a custom or wrong folder; VST3 must follow fixed system locations^[1].
• Format problem You installed VST for a host that only loads AU (Logic), or only enabled VST2 while the product shipped VST3.
• Architecture problem 32-bit-only plugin in a 64-bit host without bridging, or Intel-only binary under native Apple Silicon without a compatible bridge path.
• Database problem Host never rescanned, or a crash during scan blacklisted the plugin until you force a clean rescan^[3].

Format Mismatches: VST2, VST3, AU, CLAP

Hosts only load formats they implement. If the installer offered checkboxes and you left AU unchecked on a Logic Mac, or only installed VST2 while Ableton's VST3 system folders are enabled and VST2 is off, the plugin will never appear no matter how many times you rescan. Background on the standards: plugin formats VST, AU, and AAX and what is a VST plugin.

Quick format checks

Look at the file extension: .dll (Windows VST2), .vst bundle (macOS VST2), .vst3 (VST3), .component (AU), .clap (CLAP).

Logic users: open the vendor installer again and select the AU option, or download the AU package if it was separate.

Ableton users: in Preferences → Plug-Ins, confirm the toggles match what you installed (VST2 custom folder, VST3 system folders, Audio Units on macOS)^[3].

FL Studio users who share projects with Windows: prefer VST over AU so both platforms can match the same plugin identity^[2].

Install Paths Hosts Actually Scan

VST3 is strict. Steinberg defines dedicated global and user folders; hosts scan those paths in priority order (user before global when both exist)^[1]. FL Studio adds that VST3 must sit in the documented locations or the scan will not find it, and warns not to install third-party plugins inside FL Studio's own application plugin folder^[2].

If the installer asked for a destination and you pointed it at Desktop, a random samples drive, or the DAW program folder, move or reinstall into the standard paths below — then rescan. Detailed path tables: where are VST plugins stored.

• VST3 Windows priority User %LOCALAPPDATA%\Programs\Common\VST3, then global Common Files VST3 (and x86 for 32-bit plugins)^[1].
• VST3 macOS priority User ~/Library/Audio/Plug-Ins/VST3/, then /Library/Audio/Plug-Ins/VST3/^[1].
• VST2 flexibility No single enforced path; add custom folders in the DAW plugin manager (FL Studio Plugin Manager search paths; Ableton VST custom folder)^[2][3].
• FL Studio extras Also documents Program Files\VST3 and x86 equivalents as valid VST3 locations alongside Common Files^[2].

Architecture Mismatch: 64-Bit, 32-Bit, Apple Silicon

Modern DAWs are 64-bit. Bit depth here is about memory addressing, not audio quality. Image-Line notes that FL Studio has been 64-bit-only for a long stretch of versions, that macOS FL Studio only supports 64-bit plugins with no 32-bit bridge, and that on Windows a bit-depth mismatch uses an automatic bridge that costs roughly 2% extra CPU per bridged plugin^[2].

Apple Silicon adds another axis. Under native Apple Silicon, FL Studio bridges Intel VST plugins; under Rosetta 2, Apple handles Intel VST/AU. You must rescan once the first time you switch modes — the plugin database is not shared across modes^[2].

1. Confirm 64-bit installer
   Re-download the 64-bit (x64 / "Windows 64-bit" / universal) package. Many old free plugins are 32-bit-only and will not appear on FL Studio macOS at all.
2. Match host runtime on Mac
   If the plugin is Intel-only and missing under native Apple Silicon, either install a native/universal build or run the DAW under Rosetta and rescan in that mode^[2].
3. Check bridged status (Windows FL)
   In FL Studio's wrapper settings, see whether the plugin is bridged and which bit version loaded — useful when the name appears but crashes or behaves oddly^[2].
4. Avoid mixed random folders
   Do not drop a 32-bit .dll into the 64-bit VST3 tree and expect hosts to invent a wrapper. Use the x86 Common Files paths for true 32-bit VST3 when the host supports them^[1].

Blacklist, Failed Scans, and Crash Quarantine

Hosts protect themselves from crashy plugins. Ableton documents that incompatible plugins can crash the scan; on relaunch Live reports the culprit and may make the plugin unavailable so it no longer appears in the browser until it is reinstalled^[3]. FL Studio can mark plugins with errors; enable rescanning plugins with errors and "Rescan previously verified plugins" after updates so fixed builds are not ignored^[2].

If the plugin appeared once, then vanished after a crash or OS update, treat it as a database/blacklist issue — not a missing installer.

• Ableton clean rescan Hold Alt (Win) / Option (Mac) while clicking Rescan to delete the plugin database and run a full clean scan^[3].
• Ableton after crash On relaunch, choose to rescan the reported plugin once; a second crash can auto-disable it until reinstall^[3].
• FL Studio error rescan In Plugin Manager, enable Rescan previously verified plugins (required after updates) and rescan with verify on so classification and IDs refresh^[2].
• Vendor auth during scan iLok, Waves Central, and similar tools can pop authorization dialogs mid-scan — dismiss or complete them or the scan may mark the plugin failed.

Rescan Steps by DAW

Install and path first; rescan second. Ableton does not detect install/uninstall changes until restart or a manual Rescan while running^[3]. Expanded per-host walkthroughs: how to rescan VST plugins in your DAW.

FL Studio

Open Options → File settings (F10) → Manage plugins. Confirm Plugin search paths cover any custom VST2 folders. Enable Find plugins + Verify plugins so instruments land under Generators and effects under Effects; enable Rescan previously verified plugins after updates. Click Find plugins. New items appear under Browser → Plugin database → Installed → Effects/Generators → New^[2]. Favorite the plugin if you need it in the standard Add menus.

Ableton Live

Open Preferences with Ctrl+, (Win) / Cmd+, (Mac) → Plug-Ins. On first use, activate Plug-In Sources (nothing shows until sources are on). Enable the folders that match your install (Windows: VST custom folder and/or VST3 system folders; macOS: VST system folders, optional custom folder, Audio Units)^[3]. Click Rescan. For a corrupted database, Alt/Option+Rescan. Load from Browser → Plug-Ins.

Logic Pro

Logic only scans Audio Units in the Components folders. Install the AU build, then open Logic Pro → Settings → Plug-in Manager. Use Reset & Rescan Selection on the missing entry, or a Full Audio Unit Reset if the registry is stale. VST-only products will never appear — that is a format limit, not a broken scan.

1. Verify the file exists
   In Finder/Explorer, open the default path for that format and confirm the plugin bundle or DLL is present.
2. Match format and bit depth
   Logic → AU; modern hosts → 64-bit VST3 preferred; FL macOS → 64-bit only^[2].
3. Enable the correct plugin source
   Ableton: toggle the source that contains the file. FL Studio: add custom VST2 path if needed; leave VST3 in system locations.
4. Force a full rescan
   FL: Find plugins + Verify + Rescan previously verified. Ableton: Rescan or Alt/Option+Rescan^[3].
5. Load once to confirm
   Drag onto a MIDI track (instruments) or audio/insert slot (effects). If it opens, the install is healthy even if browser favorites still need flagging.

Still Missing? Deeper Checks

If path, format, architecture, and rescan all check out, dig into environment and product-specific installers.

• Shell / multi-plugin installers Some suites install a shell DLL that only expands into individual plugins during a deep verify scan (common with large commercial suites). In FL Studio, verify scan is the difference between "nothing" and a full list.
• Permissions and antivirus System folders need admin rights to write. Quarantine software can block DLL load during scan — temporarily allow the DAW and rescan.
• Hidden macOS Library User Library is hidden by default. Use Go → Go to Folder and paste ~/Library/Audio/Plug-Ins/ to inspect VST3/Components.
• Aliases for extra folders Ableton allows aliases inside the VST custom (or system on macOS) folder pointing at other drives or partitions, then rescans those targets^[3].
• Reinstall with defaults Run the vendor installer again and accept default locations. Manual drag-and-drop is for legacy plugins without installers^[2].
• Fresh free plugins When testing, grab known-good free VSTs from /software so you isolate "broken host config" from "broken third-party build".

For install order and first-time setup, pair this guide with how to install VST plugins. Path reference: where VST plugins are stored. Rescan-only reference: how to rescan VST plugins.