You installed a plugin, opened FL Studio, and it is not in the list. The file is on your drive. FL Studio just will not admit it exists.
This happens with almost every plugin at some point. The causes are the same whether it is a synth, a compressor or a free VST you grabbed last night. Here is how to find yours.
Key takeaways
- FL Studio only scans folders you have added under Plugin search paths. It does not search your drive.
- A normal rescan skips anything already logged, including plugins it once marked as failed. Tick Verify plugins.
- Most new plugins are VST3 only. Your VST2 folder will never contain them.
- Installers often default to a different folder than the one you scan.
- If a plugin scans but will not load, the fault is usually licensing or bit depth, not the file.
Quick answer
Go to Options, Manage plugins. Add the folder the plugin installed into under Plugin search paths, tick Verify plugins, then click Find installed plugins. New plugins appear in green. If yours does not show, you are scanning the wrong folder or the plugin is a different bit depth to your FL Studio install.
Find out where the plugin actually installed
Do this before changing any settings. Most failed scans are really a folder mismatch, and 30 seconds here saves you a lot of guessing.
On Windows, the standard locations are C:\Program Files\Common Files\VST3 for VST3 plugins and C:\Program Files\VSTPlugins or C:\Program Files\Steinberg\VSTPlugins for older VST2 ones. On macOS, look in /Library/Audio/Plug-Ins/VST3 and /Library/Audio/Plug-Ins/VST.
Search your whole drive for the plugin name if it is in none of those. I keep finding plugins in Documents because an installer defaulted there and I clicked through without reading. Once you know the real path, the rest of this is quick.
Cause 1: the folder is not in your search paths
This is the answer most of the time. FL Studio checks a short list of folders and ignores everything else on your system. Installing a plugin does not add to that list.
Open Options, then Manage plugins. The Plugin search paths box sits at the top. Click the folder icon, add the directory you just found, and it stays there permanently.
Add both your VST3 and VST2 folders while you are in there. Most people have plugins of both types, and having both listed means one less thing to debug later.
Pro tip
Point every installer at one folder you own, such as D:\VST3, rather than accepting the default. Program Files needs admin rights, which is where a lot of silent install failures come from. One custom folder means one search path, and your plugins survive a Windows reinstall.
Cause 2: you scanned without verifying
You added the path, ran the scan, and nothing appeared. The scan definitely ran, which is what makes this one confusing.
FL Studio keeps a cache of past scan results. Say it already saw a file and logged it as broken. A routine scan trusts that record and moves on, and never reopens the file.
Tick Verify plugins before scanning. That forces a fresh look at every file. On my library of 200 plugins it took about 2 minutes, against 15 seconds for a normal pass.
Cause 3: it is VST3 and you are looking in VST2
Most developers have dropped VST2 entirely. Steinberg stopped issuing VST2 licences, so anything released or updated recently ships as VST3 only.
If you have used the same plugin folder for years, your habit is to check for a .dll file. VST3 plugins do not use that extension. On Windows they are .vst3 files, and they live somewhere completely different by default.
This trips people up hardest on updates. The old VST2 version stays on disk, so FL Studio keeps showing you a plugin that works while the new version sits unscanned.
Serum is the classic example. Our guide to Serum not showing up in FL Studio walks through that exact case. Plenty of the free VST plugins worth having made the same switch.
Cause 4: bit depth mismatch
A 32-bit host cannot load a 64-bit plugin, and modern plugins are 64-bit only. FL Studio will scan the file, fail, and leave it out of the list without a clear warning.
Check under Help, then About. Nearly everyone is on 64-bit now. The exception is people who deliberately kept a 32-bit install to open old projects that depend on a discontinued plugin.
Install the 64-bit version alongside it if that is you. Both can coexist, so keep the old one for archive projects only. Our comparison of DAWs on Windows versus Mac covers this before you switch machines.
Cause 5: the plugin is there but not in your shortlist
FL Studio splits plugins into everything it has found and the favourites you have starred. The plus icon in the Channel Rack shows favourites only.
Open the full plugin database and search there instead. If the plugin appears in that list, nothing is broken at all. Click the star and it will show up where you expect from then on.
I noticed this only after reinstalling a plugin twice, which was an irritating way to learn it had been installed correctly all along. Worth 2 minutes of tidying your starred list, alongside the other DAW settings worth changing.
Cause 6: the install never finished
Installers report success more readily than they should. On Windows, writing to Program Files without administrator rights can leave a partial install behind. The plugin file exists but its dependencies do not.
On macOS, Gatekeeper quarantines plugins downloaded outside the App Store. The file is on disk and the system refuses to let any host open it.
Right click the installer and choose Run as administrator on Windows. On macOS, open System Settings, then Privacy and Security, and look near the bottom for a blocked item to allow. Apple Silicon adds a few more prompts, which we cover in running FL Studio on a MacBook Air.
Cause 7: it scans fine but crashes on load
Different symptom, different cause. The plugin appears in the list, then takes FL Studio down when you open it. The file is fine, but something it needs is not.
Licensing is the usual culprit. Many plugins check for a registration file or an iLok at startup, and a missing or corrupted one can crash rather than warn you politely.
Reinstall from the developer’s account rather than an old installer in your downloads folder, then load the plugin alone in an empty project. Heavy sessions can disguise this as a performance problem, and a few common DAW mixing mistakes produce similar symptoms.
Pro tip
Test a suspect plugin in a brand new empty project before you reinstall anything. It splits the problem in half in about 10 seconds. Loads fine there means your install is healthy and something in your original project is conflicting. Crashes in an empty project means the install or the licence is genuinely at fault.
If none of that worked
Run these in order. Each one rules out a different layer.
- Restart FL Studio. A scan run while the program is open does not always apply until a restart.
- Load the plugin in another host if you have one. Failing everywhere points at the install rather than FL Studio.
- Delete the plugin database cache in your FL Studio user data folder under
Presets\Plugin database, then rescan with verification on. - Reinstall from the developer’s own site, choosing the default location this time.
- Check the developer’s system requirements. A few plugins still do not support the newest macOS or Windows builds.
Still nothing after a clean reinstall and a verified scan? Contact the developer with your FL Studio version and operating system. That combination is usually enough for them to spot it.
Frequently asked questions
Why is my VST not showing up in FL Studio?
Usually because the folder it installed into was never added to FL Studio’s plugin search paths. Open Options, Manage plugins, add the folder, tick Verify plugins, then run Find installed plugins.
Where does FL Studio look for VST plugins?
Only in the folders listed under Plugin search paths in Manage plugins. It does not scan your whole drive. On Windows the common locations are C:\Program Files\Common Files\VST3 and C:\Program Files\VSTPlugins.
What is the difference between VST2 and VST3 in FL Studio?
VST2 plugins are .dll files on Windows, VST3 are .vst3 files, and they install to different folders. FL Studio supports both, but most new plugins are VST3 only because Steinberg stopped issuing VST2 licences.
Why does my plugin scan but not load?
That normally points to licensing or bit depth rather than a bad file. Reinstall from the developer’s account and test the plugin alone in an empty project to confirm it works in isolation.
Do I need to rescan after every install?
Yes, FL Studio only picks up new plugins on a scan. Use Verify plugins when something you know is installed refuses to appear, because a normal scan skips files it has already logged.
Can FL Studio use AU plugins?
No. FL Studio uses VST2 and VST3 on both Windows and macOS. AU is a Logic and GarageBand format, so an AU only plugin will never appear in FL Studio.
Where to go next
Is it specifically Serum giving you trouble? We have a dedicated walkthrough for Serum not showing up in FL Studio, plus a full guide to installing Serum from scratch.
Once your plugins are scanning properly, the next question is what to fill the folder with. Start with the best free VST plugins, then look at plugin bundles worth buying if you are ready to spend. For specific jobs, see the EQ plugins pros use, the best reverb plugins and compressors for transparent mixing.
Still choosing a DAW? Compare FL Studio against Ableton Live, or check whether FL Studio includes autotune before buying another plugin. Get your search paths right once and a VST not showing up in FL Studio stops being a problem you have to solve twice.
