What FL Studio plugins are and where to find them

FL Studio plugins are software instruments and effects that expand what you can do in the DAW (Digital Audio Workstation). They come in two main formats: VST (the most common) and FL Studio's native format. You can get them from the official Image-Line store, third-party developers like Serum or Sylenth1, or free repositories like Splice.

Before you install anything, check whether the plugin matches your system. Most plugins come in 64-bit and 32-bit versions — FL Studio 20 and newer run 64-bit by default, so download the 64-bit version unless you have a specific reason not to. On Windows, you'll also see some plugins marked AU (Audio Units), which are for Mac only.

Key Takeaways

  • VST plugins go into a folder on your hard drive, and FL Studio scans that folder automatically when you restart the program.
  • Most installers handle the file placement for you, but you can also manually copy plugin files into your VST folder if an installer doesn't work.
  • FL Studio looks for plugins in the default VST folder for your operating system, but you can add custom folders in FL Studio's settings.
  • After installing a plugin, restart FL Studio completely — reloading the plugin list from the menu is not enough to make new plugins appear.
  • If a plugin doesn't show up after restart, check that the bit version matches (64-bit plugin in 64-bit FL Studio) and that the file is in a folder FL Studio is scanning.

Installing plugins using the official installer

Most commercial plugins come with an installer file (.exe on Windows, .dmg on Mac). Download the installer from the developer's website or your account page, then run it. The installer will ask you where to place the plugin files — it usually defaults to the correct VST folder for your system.

On Windows, the default VST folder is C:\Program Files\Common Files\VST3 for VST3 plugins or C:\Program Files\Common Files\Steinberg\VST2 for older VST2 plugins. On Mac, it's /Library/Audio/Plug-Ins/VST. If the installer asks where to put the files and you're unsure, accept the default location — it's almost always correct.

After the installer finishes, close FL Studio completely if it's open, then restart it. FL Studio scans for new plugins when it launches. The plugin should appear in your browser under the Plugins tab.

Manual installation when an installer doesn't work

Some plugins, especially free ones or older tools, come as a .zip file or a single .dll file with no installer. In that case, you place the files yourself. Extract the .zip file if needed, then locate the plugin file — it will be a .dll (Windows) or .vst (Mac) file, or sometimes a folder containing multiple files.

Copy the plugin file or folder into your VST folder. On Windows, that's usually C:\Program Files\Common Files\Steinberg\VST2 for VST2 or C:\Program Files\Common Files\VST3 for VST3. On Mac, use /Library/Audio/Plug-Ins/VST. If you're not sure which folder to use, VST2 is the safer choice for older plugins.

After copying the files, restart FL Studio. The plugin should scan and appear in your browser. If it doesn't, check that the file extension matches the VST version you're using and that you copied it to the right folder.

Adding custom plugin folders in FL Studio

If you want to keep plugins in a folder other than the default VST location, you can tell FL Studio where to look. Open FL Studio and go to Options > File Settings. Under the Plugins tab, you'll see a list of folders that FL Studio scans. Click the folder icon to add a new path.

Navigate to the folder where your plugins are stored and select it. FL Studio will scan that folder the next time you restart. This is useful if you have plugins on an external drive or organized in a custom location on your computer.

You can add as many custom folders as you want. FL Studio will scan all of them when it starts up, so keep the number reasonable — scanning too many folders can slow down startup time.

Troubleshooting plugins that don't appear

If you installed a plugin but it doesn't show up in FL Studio, the most common cause is a mismatch between the plugin's bit version and FL Studio's bit version. Check whether you're running 64-bit or 32-bit FL Studio by going to Help > About. Then check the plugin's documentation or filename — it should say 64-bit or x64 if it's for 64-bit systems.

The second most common issue is that the plugin file is in a folder FL Studio isn't scanning. Open Options > File Settings > Plugins and verify that the folder where you placed the plugin is listed. If it's not, add it manually using the folder icon.

A third possibility is that FL Studio hasn't rescanned for new plugins. Simply reloading the plugin list from the menu is not enough — you must close FL Studio completely and restart it. If you've done that and the plugin still doesn't appear, try restarting your computer, which sometimes clears cached plugin information.

Understanding VST2 vs. VST3 and native FL Studio plugins

VST2 is the older, more widely supported format. Most plugins you'll find are VST2, and they work reliably in FL Studio. VST3 is newer and offers some technical improvements, but not all developers have released VST3 versions of their plugins yet.

FL Studio also supports its own native plugin format, which you'll see labeled as "FL" in the browser. Native plugins are optimized for FL Studio and sometimes offer features that VST versions don't. They install the same way — through an installer or by copying files to the VST folder — and FL Studio recognizes them automatically.

If a plugin comes in multiple formats, VST2 is usually the safest choice unless the developer specifically recommends VST3. Check the plugin's documentation or the developer's website to see which version they suggest for your version of FL Studio.

Frequently Asked Questions

Do I need to restart FL Studio after installing a plugin?

Yes, you must close FL Studio completely and restart it. Reloading the plugin list from the menu or refreshing the browser is not enough. FL Studio scans for new plugins only when it launches.

What if the plugin installer asks for administrator permission?

Grant it. The installer needs administrator access to write files to the Program Files folder, which is a protected system location. This is normal and safe for legitimate plugins from known developers.

Can I use Mac VST plugins in FL Studio on Windows?

No. Mac plugins (.vst or .component files) only work on Mac, and Windows plugins (.dll files) only work on Windows. Check the plugin's system requirements before downloading.

Why does FL Studio take longer to start after I install plugins?

FL Studio scans every plugin file in your VST folders when it launches. More plugins mean longer scan time. If startup is very slow, you can move unused plugins to a separate folder that FL Studio doesn't scan.

Can I install plugins in any folder I want?

You can store them anywhere, but FL Studio only finds them if that folder is in your plugin scan list. The default VST folders are the easiest option because FL Studio checks them automatically.