Skip to content
FL Studio for Windows
VST3 setup

Using VST Plugins in FL Studio (Windows) — VST3 Paths, Scans, Fixes

Get your plugins to show up and stay stable. Use the correct Windows VST3 folders, scan with Plugin Manager, add custom paths if needed, and fix blacklisted or crashing plugins.

Download for Windows Install guide

Recommended VST3 folders on Windows

VST3 (64‑bit)

Use the default system path: C:\\Program Files\\Common Files\\VST3

VST2 (if needed)

Common path: C:\\Program Files\\VSTPlugins or a dedicated folder like D:\\VST2

Why it matters

Keeping plugins in standard folders makes scanning reliable and avoids duplicate entries.

Always prefer 64‑bit plugin installers. Avoid mixing 32‑bit unless there is no 64‑bit version.

Scan plugins with Plugin Manager

  1. Open FL Studio → Options → Manage plugins.
  2. Add custom folders if your plugins are not in the defaults. Click the folder icon and add paths, then enable them.
  3. Click Find plugins or Scan. Wait until scanning completes.
  4. Search your plugin in the list, then click the star to favorite it so it appears in the Browser and Add menu.
Fix missing plugins Performance tips

Common issues and quick fixes

Plugin not showing up

  • Confirm a 64‑bit install and correct path.
  • Add the folder in Plugin Manager and run a full rescan.
  • Make sure you installed the VST3 variant when available.

Blacklisted plugin

  • Open Plugin Manager → Blacklist → clear/remove the entry.
  • Rescan and check for the latest plugin update.
  • Run FL Studio as admin once if the plugin needs permission to install components.

32‑bit only plugin

  • FL Studio can bridge 32‑bit, but stability may suffer.
  • Prefer official 64‑bit updates or alternatives.
  • Reduce bridges in large projects to avoid overhead.

Duplicates or wrong vendor names

  • Remove redundant custom folders that duplicate the same plugins.
  • Keep only standard VST3 + one clean VST2 folder if required.
  • Rescan afterwards and re‑favorite.

Scanning is slow

  • Temporarily disable scanning of large sample libraries.
  • Keep plugin folders tidy; avoid deep nested paths.
  • Update antivirus to reduce false positives during scanning.

Crashes on load

  • Update the plugin and your GPU/audio drivers.
  • Test in a blank project; try disabling plugin GPU acceleration if available.
  • Contact the plugin vendor with crash logs for a fix.

Best practices

Stay 64‑bit

Use 64‑bit plugins with the 64‑bit FL Studio build to avoid bridges and memory limits.

One clean VST2 folder

If you use VST2, keep a single folder (e.g., D:\\VST2) and point every installer there.

Don’t install into FL folders

Avoid placing plugins inside FL Studio’s own program directory to prevent permission issues.

Next steps

Download Windows installer Optimize performance Install guide