You installed Serum, you opened FL Studio, and it is not there. Almost always the plugin is sitting on your drive exactly where it should be. FL Studio just has not been told to look there.
I’ve hit this on three machines now, a different cause every time. Here are the seven reasons, ordered by how often each one is to blame. Most people are fixed by number three.
Key takeaways
- Nine times out of ten the VST folder was never added to FL Studio’s plugin search paths.
- A plain rescan finds nothing if the plugin was already scanned and marked as failed. You need Verify plugins ticked.
- Serum 2 installs as VST3 only. If you are searching for a .dll in your old VST2 folder, it will never appear.
- A 32-bit FL Studio install cannot load 64-bit Serum. This still catches people running very old projects.
- If Serum scans but crashes on load, the problem is usually the licence file, not the plugin.
Quick answer
Open Options, Manage plugins in FL Studio. Add the folder Serum installed into under Plugin search paths, tick Verify plugins, then click Find installed plugins. Serum appears under Xfer Records once the scan finishes. If it still does not, your FL Studio and Serum builds are different bit depths, or the VST3 file never made it to disk.
First, confirm Serum actually installed
Before touching any FL Studio settings, check the file exists. This takes twenty seconds and saves you from troubleshooting a scan problem that is really a download problem.
On Windows, open File Explorer and go to C:\Program Files\Common Files\VST3. You are looking for Serum2.vst3, or Serum.vst3 if you are on version 1. On macOS, go to /Library/Audio/Plug-Ins/VST3 and look for the same file.
If the file is not there, the installer either failed or you pointed it somewhere unusual during setup.
Run the installer again and write down the destination folder this time. Our full walkthrough on how to install Serum in FL Studio covers the setup screens in order if you want to start clean.
Reason 1: the VST folder is not in your plugin search paths
This is the answer for most people. FL Studio does not scan your whole drive. It only looks in folders you have explicitly listed, and the list does not update itself when a new plugin installs.
Open Options, then Manage plugins. At the top you will see Plugin search paths with a short list of folders. Click the folder icon and add the directory you confirmed Serum was in a moment ago.
Add the VST3 folder itself, not its parent. I pointed FL Studio at the whole of Program Files once and the scan sat there for four minutes before giving up. Narrow paths scan in seconds.
Pro tip
Keep every third party plugin in one folder you control, such as D:\VST3, and point FL Studio there once. Installers default to Program Files, which needs admin rights and gets messy fast. A single custom folder means you add one search path and never think about it again, even after reinstalling Windows.
Reason 2: you rescanned without verifying
You added the path, hit Find installed plugins, and Serum still is not listed. This one confuses people because the scan clearly ran.
FL Studio caches its scan results. If it has already seen a plugin and logged it as broken, or it recorded the folder as empty on a previous pass, a normal scan skips straight over it. The cache is treated as truth.
Tick Verify plugins before you scan. That forces FL Studio to open every file again from scratch rather than trusting what it already has. When we ran this on a machine with roughly 200 plugins, the verified scan took just over two minutes against about fifteen seconds for a normal one. The wait is the point.
Reason 3: you are looking for a VST2 file that no longer exists
Serum 2 ships as VST3, AU and AAX. There is no VST2 version. If you have used Serum for years, your muscle memory says to check the VST2 folder for a .dll file, and that file is simply not part of the download any more.
This bites hardest when you are upgrading. Serum 1 left a .dll behind in your old VST2 folder, so FL Studio keeps showing you a plugin called Serum while the new version sits unscanned in VST3.
I spent a good ten minutes convinced the Serum 2 update had failed, when what had actually happened was that my project kept loading the old version 1 .dll.
Add your VST3 folder as a search path and rescan with verification on. Both versions can coexist safely. FL Studio lists them separately, so check which one a project loaded before assuming an update failed. The same VST2 to VST3 shift is worth knowing about generally, since it affects plenty of the free VST plugins that have been updated recently.
Reason 4: bit depth mismatch
A 32-bit host cannot load a 64-bit plugin. Serum has been 64-bit only for years, so if you are running a 32-bit copy of FL Studio, it will scan the file, fail to load it, and leave it out of the list without much explanation.
Check which build you are running under Help, then About. Most people on a current install are already on 64-bit. The ones who are not usually kept the 32-bit version deliberately to open an old project that depends on a discontinued plugin.
If that is you, install the 64-bit version alongside it. FL Studio allows both, and you can keep the old one purely for archive projects. This is also worth checking if you are weighing up a platform move, which we cover in our comparison of DAWs on Windows versus Mac.
Reason 5: Serum scans but crashes when you load it
Different symptom, different cause. If Serum appears in the plugin list but takes FL Studio down when you open it, the plugin file is fine. Something it depends on is not.
The usual culprit is the licence. Serum looks for its registration file at startup, and if that file is missing, corrupted, or was copied from another machine, the plugin can fail hard rather than showing you a polite warning.
Reinstall Serum from your Xfer account rather than from an old installer sitting in your downloads folder. Then open it as the only plugin in an empty project.
If it loads there but crashes in your real project, the conflict is with something else in that project. Heavy sessions can also mask this as a performance issue, and a few of the common DAW mixing mistakes produce similar symptoms.
Pro tip
Before you reinstall anything, open FL Studio and load Serum into a completely empty project. It sounds obvious, but it splits the problem in half in about ten seconds. If it loads there, your install is healthy and the fault is a conflict inside one project. If it crashes even in an empty session, the licence or the install is the issue and reinstalling is worth your time.
Reason 6: the plugin is hidden rather than missing
FL Studio has a favourites system that trips people up. Plugins you have not marked as favourites do not show in the shortlist you see when you click the plus icon in the Channel Rack.
Open the full plugin database instead and search there. If Serum appears in that list but not in your quick menu, nothing is broken. Click the star next to it and it will start appearing where you expect.
Worth checking before you reinstall anything. I noticed this one only after uninstalling and reinstalling Serum twice, which was a genuinely annoying way to learn that the plugin had been there the whole time. Tidying up which plugins are starred is one of several DAW settings worth changing right now.
Reason 7: permissions blocked the install
On Windows, installing to Program Files without administrator rights can leave you with a partial install. The installer reports success, and some of the files never arrive.
On macOS, Gatekeeper can quarantine a plugin downloaded outside the App Store. The file exists, but the system will not let a host open it.
On Windows, right click the installer and choose Run as administrator. On macOS, open System Settings, then Privacy and Security, and look for a message about a blocked item near the bottom. Allow it, then rescan. If you are on Apple Silicon, our notes on running FL Studio on a MacBook Air cover the extra permission prompts you will see.
If none of that worked
Run through these in order before contacting support. Each rules out a different layer.
- Restart FL Studio completely. A scan that ran while the program was open does not always take effect until a restart.
- Load Serum in a different host if you have one. If it fails everywhere, the problem is the install, not FL Studio.
- Delete the plugin cache. In FL Studio this lives in your user data folder under
Presets\Plugin database. Removing it forces a full rebuild on the next scan. - Reinstall from your Xfer Records account, choosing the default install location this time.
If Serum still refuses to appear after a clean reinstall and a verified scan, contact Xfer support with your FL Studio version and operating system. That combination is rare enough to need a look at your specific setup.
Frequently asked questions
Why is Serum not showing up in FL Studio?
In most cases the folder Serum installed into was never added to FL Studio’s plugin search paths. Open Options, Manage plugins, add your VST3 folder, tick Verify plugins, then run Find installed plugins.
Where does Serum install by default?
On Windows it installs to C:\Program Files\Common Files\VST3. On macOS it installs to /Library/Audio/Plug-Ins/VST3. You can change this during installation, which is why some people cannot find it later.
Does Serum 2 still have a VST2 version?
No. Serum 2 ships as VST3, AU and AAX only. If you are searching your VST2 folder for a .dll file, you will not find one. Serum 1 did include VST2, which is why upgraders often end up loading the old version by accident.
Why does FL Studio crash when I load Serum?
A crash on load usually points to the licence file rather than the plugin. Reinstall Serum from your Xfer Records account, then open it in an empty project to confirm it works in isolation.
Do I need to rescan plugins every time?
Only after installing or updating something. FL Studio caches results, so a routine scan skips files it has already logged. Tick Verify plugins when a plugin you know is installed refuses to appear.
Is Serum included with FL Studio?
No. Serum is a separate purchase from Xfer Records at $249, or $9.99 a month through Splice rent-to-own. No FL Studio edition bundles it, including All Plugins Edition.
Where to go next
If you have not installed Serum yet, or you want the full setup walkthrough including licensing and performance tuning, read our guide on how to install Serum in FL Studio.
Building out the rest of your plugin folder is worth doing properly. We have picks for the best free VST plugins, and if you are weighing a paid purchase, plugin bundles worth the money covers what you actually get for your money. For specific tools, our roundups of the best reverb plugins and the EQ plugins pros actually use are a good next stop.
Still deciding on your setup? Compare FL Studio against Ableton Live, or see whether FL Studio has autotune built in before buying anything extra.
