How to Add VST Plugins in FL Studio

Web Admin Avatar

·

[vr_reading_time]

A laptop computer sitting on top of a desk

Adding third-party instruments and effects is one of the first things most producers want to do. Learning how to add VST plugins in FL Studio comes down to three steps: install the plugin file, point FL Studio at the right folder and scan, then load it from the plugin browser. If you’re new to the format, it helps to first understand what a VST actually is, but once you’ve done it once, every new plugin follows the same routine.

Step 1: Install the plugin

Download the plugin from the developer and run its installer. During installation you’ll usually be asked where to put the VST files. Note that folder location — you’ll need it for the scan. FL Studio supports VST2, VST3 and (on macOS) Audio Unit formats, so a plugin that installs in any of those will work. The general process for getting plugins onto your system is the same across hosts, so our walkthrough on how to install VST plugins covers the installer side in more depth.

If the installer lets you choose, keep all your VST3 plugins in one consistent folder. That makes future scans faster and your setup tidier, which is part of keeping a clean studio overall — see our home studio gear checklist for the bigger picture.

Step 2: Tell FL Studio where your plugins live

  1. Open the Options menu and go to Manage plugins (the Plugin Manager).
  2. Under Plugin search paths, add the folder where your VST plugins were installed. You can add several folders.
  3. Click Find more plugins (or Find plugins) to scan. FL Studio checks each folder and adds anything new to its database.

If you tick Verify plugins before scanning, FL Studio briefly loads each one to confirm it works, which catches broken installs early.

Step 3: Mark favourites so they’re easy to find

After a scan, open the Plugin Manager’s list of installed plugins. Click the star or favourite icon next to the ones you use most. Favourited plugins show up in the quick-add menus, so you don’t have to dig through every plugin each time.

Step 4: Load the plugin in your project

How you load it depends on whether it’s an instrument or an effect:

  • Instrument (synth/sampler): In the Channel Rack, click the + (add channel) button, browse to your plugin, and it loads as a new channel ready to play from the Piano Roll. See how to use the Piano Roll in FL Studio to start writing parts.
  • Effect (EQ, reverb, compressor): Open the Mixer, select a track, click an empty effect slot, and choose your plugin from the list. It now processes whatever audio runs through that mixer track.

You can also drag plugins straight from the FL Studio browser onto a channel or mixer slot once they’re scanned.

VST2 vs VST3 vs Audio Unit: which to install

Most modern plugins ship with more than one format in the same installer, and it helps to know which one to keep. VST3 is the current standard on both Windows and macOS, and it generally handles things like sample-accurate automation and dynamic input/output channels more cleanly than the older VST2. Audio Unit (AU) is Apple’s own format and only matters on macOS, where it sits alongside VST — if you work on a Mac, our breakdown of VST vs AU plugins explains when each one matters. As a rule, install VST3 if it’s offered, fall back to VST2 only when a plugin you rely on hasn’t been updated, and don’t bother scanning a folder that holds duplicate copies of the same plugin in two formats — that just clutters your browser with two entries for one instrument.

One more thing to watch: bit depth. A 64-bit version of FL Studio can only load 64-bit plugins. Almost everything released in recent years is 64-bit, but very old freeware is sometimes still 32-bit, and that won’t appear in a 64-bit scan. If a legacy plugin is essential, FL Studio can run it through a bridge, though native 64-bit versions are always the smoother choice.

Keeping your plugin folders organised

A tidy folder structure pays off the more plugins you collect. Pick one parent folder for your VST3 files and one for VST2, point FL Studio’s search paths at those, and resist the urge to let every installer scatter files wherever it likes. When a developer offers a custom install path, use the same folders every time. This keeps scans quick, makes backups simple, and means that if you move to a new computer you can copy two folders and re-scan rather than hunting down dozens of stray installs.

Inside FL Studio you can also organise the browser itself. Once plugins are scanned, you can sort them by type, hide ones you never touch, and rely on the favourites you starred in Step 3 so the synths and effects you actually use sit at the top of the add menus.

Common mistakes when adding VST plugins

  • Scanning before the installer finished: if you run a scan while files are still being written, FL Studio won’t see the plugin. Let the installer complete, then scan.
  • Forgetting to add the folder: the scan only looks inside the search paths you’ve listed. A plugin installed to a custom location you never added simply won’t show up.
  • Mismatched format or bit depth: installing a 32-bit or wrong-format build for a 64-bit FL Studio is the most common reason a plugin appears to install but never loads.
  • Skipping activation: many paid plugins need their licence registered or a serial entered before they will open, even after a clean install and successful scan.
  • Hoarding duplicates: pointing the scan at several overlapping folders can list the same plugin multiple times, which makes the browser confusing rather than complete.

If a plugin doesn’t appear

  • Re-run the scan and make sure the install folder is in your search paths.
  • Check you installed the right format for your FL Studio version (a 64-bit FL Studio needs 64-bit plugins).
  • Some plugins need their own activation or license to be completed before they’ll load.

Related FL Studio guides

Once your plugins are in, you’ll want to know where signals go: read how to route mixer tracks in FL Studio to put effects in the right place. For getting trigger-based effects working, how to sidechain in FL Studio builds on the same mixer skills. If you’re hunting for instruments and effects to scan in, our roundup of the best free VST plugins is a good place to start. More tutorials live in the mixing and mastering hub, and if you’re still choosing software, see best free DAWs for beginners.

Frequently asked questions

Where do VST plugins install on my computer?

It depends on the installer. Many default to a common VST3 folder on Windows or the system Audio Unit and VST folders on macOS, but you can usually choose a custom folder. Whatever you pick, add that folder to FL Studio’s plugin search paths before scanning.

Why won’t FL Studio find my new plugin?

Usually the install folder isn’t in your search paths, or you scanned before installing finished. Add the correct folder in the Plugin Manager and re-scan. Also confirm the plugin format and bit depth match your FL Studio version.

Do I need to rescan every time I add a plugin?

Yes — run a scan after each new install so FL Studio adds it to the database. A quick scan only checks for new files, so it’s fast once your folders are set.

Should I install the VST2 or VST3 version?

Install VST3 whenever it’s offered, since it’s the current standard and is generally better behaved with automation and routing. Only keep the VST2 build if a plugin you depend on hasn’t been updated to VST3, and avoid scanning both copies of the same plugin to keep your browser tidy.

Get the studio newsletter

New guides, gear deals and mixing tips — a couple of times a month. No spam, unsubscribe anytime.

More guides