To add VST plugins to FL Studio, first run the plugin’s installer and note the folder it puts the files in. Then open Options > Manage plugins, make sure that folder is listed under your plugin search paths, and click Find installed plugins (also labelled “Start scan” or “Find plugins” depending on your version). Once the scan finishes, your new plugin shows up in the Plugin Picker and the Add menu, ready to drop onto a channel or a mixer track.
Violet Recording is reader-supported — we may earn a commission from links on this page, at no extra cost to you.
That is the short version. The rest of this guide walks through each stage slowly, so you understand why a plugin sometimes refuses to appear, how VST2 and VST3 differ, and where FL Studio actually looks on your drive. If you are still choosing a DAW, our roundup of the best free DAWs for beginners and our FL Studio review give you the wider picture. If the term VST itself is new, read what is a VST first — it will make everything below click faster.
Install the plugin before you touch FL Studio
A VST is not something you drag straight into FL Studio like a sample. It is a piece of software you install onto your computer first, exactly like any other app. When you buy or download a synth or effect, you get an installer — an .exe on Windows or a .pkg on macOS. Run it, agree to the terms, and pay attention to one screen in particular: the page that asks where to put the VST files.
Most installers offer a default location, and that default is usually correct. On Windows, VST3 plugins go to C:\Program Files\Common Files\VST3, while older VST2 plugins go to whatever folder you point them at — many people use C:\Program Files\VstPlugins or C:\Program Files\Steinberg\VstPlugins. On macOS, the standard homes are /Library/Audio/Plug-Ins/VST3 and /Library/Audio/Plug-Ins/VST. Write the path down or take a screenshot. Nine times out of ten, a plugin that “won’t show up” was simply installed into a folder FL Studio never scans.
How to add VST plugins to FL Studio step by step
With the plugin installed, open FL Studio and follow this sequence. The exact wording of a couple of buttons has changed across FL Studio 20, 21 and later, so I have flagged the alternatives.
- Open the plugin manager. Go to the top menu and choose Options > Manage plugins. This opens the Plugin Manager window, which is the control centre for every synth and effect FL Studio knows about.
- Check your plugin search paths. On the left you will see a list headed “Plugin search paths.” These are the folders FL Studio scans. The common VST3 folder is usually there by default. If you installed a VST2 plugin into a custom folder, click the folder/add icon and browse to that folder so it appears in the list.
- Run the scan. Click Find installed plugins near the top (in some versions the button reads “Find plugins” or “Start scan”). FL Studio walks through every listed folder and catalogues what it finds. Leaving the “Verify plugins” option ticked is the safe choice — it opens each plugin briefly to confirm it loads, which weeds out broken files.
- Watch the results populate. As the scan runs, freshly found plugins appear in the list, often highlighted so you can spot the new arrivals. When the scan bar completes, your plugin is registered.
- Favourite the ones you’ll use. Click the star or “favourite” icon next to a plugin to pin it. Favourited plugins show up first in the Plugin Picker, so you are not scrolling past a hundred stock devices every time.
That is the whole official process. You only need to rescan when you install something new — FL Studio remembers everything it has already found.
Loading your new VST as an instrument or an effect
Once a plugin is scanned in, there are two kinds of slots it can live in, and knowing the difference saves a lot of confusion.
Instruments (synths, samplers, drum machines) go on the Channel Rack. Open the Plugin Picker — the quickest way is the plus (+) button on the Channel Rack, or the Add menu at the top. The Picker shows every plugin as a tile; click your synth and it drops in as a new channel you can play and sequence.
Effects (EQ, compression, reverb, saturation) go on the Mixer. Select a mixer track, click an empty insert slot on the right-hand side of the Mixer, and choose your effect from the list that appears. Signal flows top to bottom through those slots, so the order you stack them in matters — an EQ before a compressor sounds different from a compressor before an EQ.
If you are new to the mixing side of this, our primers on EQ and compression fundamentals and how to use reverb and delay explain what to actually do with those effect slots once your plugins are in them.
VST2 versus VST3, and why it matters here
FL Studio loads three plugin types: its own native plugins, VST2, and VST3. VST3 is the newer standard and is generally the one to install when a plugin offers both — it handles things like automatic parameter detection more gracefully. Some older plugins only ship as VST2 (the .dll or Mac .vst format), and that is fine; FL Studio still runs them happily. The practical takeaway is simply this: if a plugin gives you a choice during installation, tick VST3, and only fall back to VST2 if that is all the developer offers. Either way, the scanning steps above are identical.
Common problems and how to fix them
The plugin scanned but won’t show in the Picker. Open the Plugin Manager and check whether it landed under a different tab, or use the search box at the top of the Plugin Picker and type its name. Also confirm you are looking in the right place — a reverb won’t appear when you open the Picker from the Channel Rack’s instrument view if FL Studio classed it as an effect.
Nothing new appeared after the scan. The folder almost certainly isn’t in your search paths. Reopen Manage plugins, add the exact install folder you noted earlier, and rescan. On a 64-bit FL Studio, a very old 32-bit-only plugin may not load at all — most modern plugins are 64-bit, so this is rare now.
FL Studio froze or crashed mid-scan. That usually means one plugin file is corrupt. Reinstall the offending plugin, or temporarily remove it from its folder and rescan the rest. Keeping “Verify plugins” on helps FL Studio flag the culprit rather than choke silently.
The demo keeps nagging or won’t make sound. Many commercial VSTs run in a limited demo state until you enter a licence, which is normal — that is the developer’s copy protection, not an FL Studio fault.
Free stock devices versus paid VSTs
Before you go hunting for third-party plugins, remember FL Studio ships with a deep set of native instruments and effects — Sytrus, Harmor, Fruity Parametric EQ 2, Fruity Limiter and more — and for a huge amount of music these are genuinely all you need. Add a VST when you want a specific sound or workflow the stock tools don’t cover: a modelled analogue synth, a convolution reverb, or a mastering-grade limiter, for example. When you reach that point, plugin marketplaces such as Plugin Boutique are a sensible place to compare options and catch sales.
You can also lean on free browser tools while you produce — our free audio tools include a metronome, BPM finder and tuner that pair nicely with any FL Studio session. And if you want to build an original track from scratch to test a new synth on, an AI sketch from Solmi can give you a starting idea to react to.
For the bigger setup picture, see our home studio gear checklist and the full home studio setup hub.
Frequently asked questions
Where does FL Studio look for VST plugins by default?
It scans the folders listed under Options > Manage plugins > Plugin search paths. On Windows that typically includes the common VST3 folder; on macOS it includes the standard Library plugin folders. If you installed to a custom folder, add it there manually so the scan can find it.
Do I have to rescan every time I open FL Studio?
No. FL Studio remembers every plugin it has already catalogued. You only run “Find installed plugins” again after you install something new or move plugin files to a different folder.
Should I install the VST2 or VST3 version?
Choose VST3 when the developer offers both — it is the current standard and integrates a little more cleanly. Only use VST2 when that is the only format available. FL Studio scans and loads both the same way.
