How to Rescan VST Plugins in Your DAW (FL Studio, Ableton, Logic, Reaper)

Why You Need to Rescan After Installing Plugins

DAWs do not watch your hard drive in real time. They build an internal plugin database on first launch and update it when you trigger a rescan or restart. Install a new compressor, move a folder to an external SSD, or copy a free synth from /software — if the host never rescans, the plugin simply will not appear in browser menus.

A rescan is not the same as reinstalling. You are telling the DAW to re-index files already on disk. The exact menu differs per host, but the logic is identical: confirm the install path, run the scan, then load the plugin on a track to verify it opens.

Before you blame the DAW, read plugin formats VST, AU, and AAX and what is a VST plugin — format mismatches cause more "missing plugin" reports than broken installers.

Rescan Methods Compared Across DAWs

Every major DAW exposes a rescan command, but naming and depth vary. Some hosts distinguish a fast file listing from a full verification pass that opens each plugin and classifies it as instrument or effect.

• Fast scan Lists filenames without opening plugins. Quick, but may mislabel instruments as effects.
• Verify scan Opens each plugin, checks bit depth, and sorts into correct categories. Slower but more reliable.
• Clean database reset Deletes the host's plugin index and rebuilds from scratch — use when plugins vanish after an OS update.

Before You Rescan: Install Path and Format Checklist

Rescanning a plugin that was never installed correctly wastes time. Run through this checklist once — it solves most "plugin not showing" tickets before you touch DAW settings.

VST3 hosts expect bundles in fixed system folders. Steinberg defines C:\Program Files\Common Files\VST3 on Windows and /Library/Audio/Plug-Ins/VST3/ on macOS as primary scan targets^[1]. FL Studio also checks alternate Windows paths including Program Files\VST3^[2].

1. Confirm the installer finished
   Run the vendor installer and accept the default location. Manual drag-and-drop only if no installer exists.
2. Match format to DAW
   Ableton, FL Studio, and Reaper load VST2/VST3. Logic Pro loads Audio Units — a VST-only build will never appear there[3].
3. Match bit depth
   Modern DAWs are 64-bit. A 32-bit-only VST may need bridging (FL Studio Windows) or will not load at all (FL Studio macOS, Logic Pro).
4. Quit and relaunch the DAW
   Ableton does not detect install/uninstall changes until restart unless you manually rescan[4].
5. Then run the DAW-specific rescan
   Follow the steps for your host below — order matters: install first, rescan second.

How to Rescan VST Plugins in FL Studio

FL Studio centralizes all third-party plugin scanning in the Plugin Manager, reachable from File settings (F10). Image-Line recommends Find plugins + Verify plugins so instruments land in Generator lists and effects in FX slots — not both^[2].

New plugins appear under Browser > Plugin database > Installed > Effects > New or Generators > New. For a faster pass without opening each plugin, right-click the Plugin database and choose Refresh plugin list (fast scan) — equivalent to scanning with Verify plugins off^[5].

1. Open Plugin Manager
   Press F10 (Options > File settings) and click Manage plugins under the Plugins section.
2. Set search paths
   Under Plugin search paths, add custom VST2 folders with the + Folder button. VST3 and AU must use default system locations[5].
3. Enable Verify plugins
   Check Verify plugins on the Options tab. Also enable Rescan previously verified plugins after an update.
4. Run Find plugins
   Click Find plugins. Dismiss any vendor authorization pop-ups that appear during the scan.
5. Check the Browser
   Look in Plugin database > Installed for your plugin under Generators or Effects. Flag favorites with the F column for quick access.

FL Studio fast scan alternative

Right-click Plugin database in the Browser sidebar and choose Refresh plugin list (fast scan). Use this when you only added one plugin and do not need reclassification. Enable Rescan plugins with errors if a previous scan marked a working plugin as failed^[5].

How to Rescan VST Plugins in Ableton Live

Ableton Live 12 scans VST2, VST3, and Audio Units. On first launch you must activate plugin sources in the Browser's Plug-Ins panel before anything appears^[4]. After that, the Rescan button in Plug-Ins Settings handles new installs without a full restart.

Hold Alt (Win) / Option (Mac) while launching Live to skip plugin scanning during crash troubleshooting. Once you isolate the problem plugin, run a normal rescan with that plugin disabled or removed.

1. Open Plug-Ins Settings
   Press Cmd+, (Mac) / Ctrl+, (Win) or click Activate in the Browser's Plug-Ins label.
2. Configure VST folders
   Under Plug-In Sources, set the VST custom folder (Windows) or enable system VST folders (macOS: /Library/Audio/Plug-Ins/VST)[4].
3. Click Rescan
   Press Rescan to index newly installed plugins while Live is running.
4. Clean rescan if needed
   Hold Alt/Option while clicking Rescan to delete the plugin database and run a full clean scan[4].
5. Load from Browser
   Find the plugin under Browser > Plug-Ins. Instruments show a keyboard icon; effects do not. Drag onto a MIDI or audio track.

Ableton crash during scan

If a VST crashes Live during scanning, Live re-launches with a dialog naming the problematic plugin. You can make it unavailable so it is skipped on future scans until reinstalled^[4].

How to Rescan Plugins in Logic Pro (Audio Units)

Logic Pro does not load VST plugins — it scans Audio Units (AU) only. If you installed a Windows VST or a macOS VST3 with no AU component, Logic's Plug-in Manager will never list it. Install the .component bundle to /Library/Audio/Plug-Ins/Components/ instead^[6].

For cross-platform projects shared with Windows producers, FL Studio's manual recommends VST format on macOS to preserve compatibility^[2]. Logic users working solo should prioritize the AU build.

New to Logic? See Logic Pro 11 tutorial for track and mixer basics before diving into third-party plugins.

1. Restart your Mac
   After installing a new AU plugin on macOS High Sierra or later, restart before expecting it in Logic[3].
2. Open Plug-in Manager
   Choose Logic Pro > Settings > Plug-in Manager (or Preferences on older versions).
3. Confirm installation
   Locate the plugin in the list. Filter by manufacturer in the left column. "Not authorized" means you need to activate the license with the vendor.
4. Reset & Rescan Selection
   If the plugin shows failed validation, select it and click Reset & Rescan Selection[3].
5. Full Audio Unit Reset
   If the plugin is missing entirely, click Full Audio Unit Reset, quit Logic, reopen, and wait for the full AU rescan to finish.

Launch Logic without Audio Units

If Logic crashes on open, hold Control at launch and choose Launch Without Audio Units. Remove the offending AU from your project slot by slot, or move its .component file off the Components folder temporarily^[7].

How to Rescan VST Plugins in REAPER

REAPER scans configured VST folders on every startup by default. The Re-scan button in VST preferences makes new plugins available immediately without restarting^[8]. REAPER also supports CLAP and LV2 with separate path and rescan controls on the Plug-ins > LV2/CLAP page.

Hold Ctrl while starting REAPER to skip the startup VST scan — useful when a bad plugin hangs the launch. Remove Ctrl on the next start for a normal scan.

1. Open VST preferences
   Choose Options > Preferences, then select VST under the Plug-ins section.
2. Set plugin paths
   Click Edit path list…. Use Add system VST paths or Add path… for custom folders. Keep VST3 in a separate directory from VST2[8].
3. Click Re-scan
   Press Re-scan to index plugins immediately. REAPER also scans subfolders automatically.
4. Apply and OK
   Click Apply then OK so path changes persist across sessions.
5. Insert on a track
   Click an FX slot on any track, browse the FX browser, and search for your plugin by name.

Startup scan setting

The option Scan new/updated plug-ins on startup is enabled by default. Disable it only if startup scans slow your machine — you will need manual Re-scan after each install^[8].

Troubleshooting: Plugin Installed but Not Showing

When a rescan completes but the plugin is still invisible, the cause is almost always one of four issues: wrong format, wrong folder, blocked by the host, or bit-depth mismatch. Work through them in order before reinstalling.

• Wrong format Match plugin type to host: VST/VST3 for Ableton, FL Studio, Reaper; AU for Logic Pro and GarageBand^[3].
• Wrong path Custom installs need the folder added in the DAW's plugin manager — default installers usually land in system paths automatically^[2][8].
• Blocked plugin Ableton blacklists crash-causing VSTs after two failed scans. Logic marks AUs as failed validation. Reinstall or update before rescanning.
• Rosetta / Apple Silicon On Apple Silicon Macs running FL Studio natively, Intel VST plugins are bridged automatically — rescan separately in Apple Silicon and Rosetta modes^[2].

After the Rescan: Load, Test, and Build Your Chain

Once the plugin appears in your browser, load it on a blank track and play a note or loop to confirm audio passes through. Save a default preset or favorite entry so you are not searching the full list next session.

Browse best free VST plugins 2026 for curated synths and effects worth installing today. Pair new tools with DAW walkthroughs: FL Studio 21 tutorial, Ableton Live 12 tutorial, or Logic Pro 11 tutorial depending on your host.

If you downloaded plugins from Plugg Supply, confirm the archive extracted fully before rescanning — a partial copy leaves no valid binary for the DAW to index.