How to Install a Plugin in FL Studio

Where FL Studio Looks for Plugins

FL Studio finds plugins in specific folders on your computer. When you install a plugin, it goes into one of these folders, and FL Studio scans them automatically the next time you open the program. The two main locations are the Plugins folder inside your FL Studio installation directory, and your system's default VST folder — usually C:\Program Files\Common Files\VST3 on Windows or Library/Audio/Plug-Ins on Mac.

Most third-party plugins come with an installer that puts files in the right place for you. If you're installing manually or the installer didn't work, you'll need to move the plugin files yourself. FL Studio recognizes VST, VST3, and AU formats depending on your operating system.

Key Takeaways

Most plugins install automatically through their own installer program, which puts files in the correct folder for FL Studio to find them.
If a plugin doesn't appear after installation, restart FL Studio completely — it only scans for new plugins when it starts up.
You can point FL Studio to additional plugin folders through Settings, so you don't have to move files if you prefer to keep them organized elsewhere.
On Windows, 32-bit plugins require a separate bridging tool to work in 64-bit FL Studio, while Mac users should use AU or VST3 formats for best compatibility.

Installing a Plugin Using Its Installer

Most commercial and many free plugins come with an installer — usually a .exe file on Windows or a .dmg file on Mac. Download the installer from the plugin maker's website, then run it. The installer will ask you where to put the files and usually defaults to the correct location. Accept the default unless you have a specific reason to change it.

After the installer finishes, close FL Studio completely if it's open, then reopen it. FL Studio scans for new plugins only when it starts, so restarting is necessary. Open the browser panel on the left side of FL Studio and look under the Plugins section — your new plugin should appear there. If it doesn't, check the plugin maker's website for troubleshooting steps specific to that plugin.

Manual Installation When There's No Installer

Some plugins, especially older or open-source ones, come as a folder or single file with no installer. In this case, you'll move the files manually. On Windows, locate your FL Studio installation folder (usually C:\Program Files\Image-Line\FL Studio), then open the Plugins folder inside it. Create a new subfolder with the plugin's name, then copy the plugin files into that subfolder.

On Mac, the process is similar but the path is different — look in Applications/FL Studio, then navigate to Contents > Plugins. Create a subfolder for your plugin and paste the files there. After moving the files, close and reopen FL Studio. The plugin should now appear in your browser.

Adding Custom Plugin Folders

If you want to keep plugins organized in a separate location instead of moving them into FL Studio's folder, you can tell FL Studio where to look. Open FL Studio and go to Options > Preferences. Click on the Plugins tab, then look for the Plugin search paths section. Click the plus icon to add a new path, then browse to the folder where your plugins are stored.

FL Studio will now scan that folder for plugins every time it starts. This method is useful if you have many plugins or if you want to share a plugin folder between FL Studio and another DAW. After adding a custom path, restart FL Studio to make sure it finds everything.

Handling 32-Bit Plugins on 64-Bit FL Studio

FL Studio on Windows comes in 64-bit by default, but some older plugins are only available in 32-bit. A 64-bit program cannot directly load a 32-bit plugin — they're incompatible architectures. To use a 32-bit plugin in 64-bit FL Studio, you need a bridging tool like Blue Cat's PatchWork or ddmf Metaplugin, which acts as a translator between the two.

Install the bridging tool first, then install your 32-bit plugin normally. The bridging tool will appear in your FL Studio plugins list. Open it, and it will let you load the 32-bit plugin inside it. This adds a small amount of processing overhead but allows you to use plugins that would otherwise be unavailable. Mac users generally don't face this issue because Apple discontinued 32-bit support earlier and plugin makers adapted accordingly.

Troubleshooting Plugins That Don't Appear

If you installed a plugin but it doesn't show up in FL Studio, start by restarting the program — this is the most common fix. If it still doesn't appear, check that you put the files in the right location. On Windows, verify the files are in C:\Program Files\Common Files\VST3 or inside FL Studio's Plugins folder. On Mac, check Library/Audio/Plug-Ins or FL Studio's Contents > Plugins folder.

Next, make sure the plugin format matches your FL Studio version. FL Studio on Windows accepts VST and VST3 plugins. FL Studio on Mac accepts AU and VST3 plugins — VST2 plugins will not work on Mac. If the plugin is very old, it may not be compatible with your version of FL Studio at all. Check the plugin maker's website for system requirements and compatibility notes. Some plugins also require additional software or licenses to run — read the installation instructions carefully.

Frequently Asked Questions

Do I need to restart FL Studio every time I install a plugin?

Yes. FL Studio only scans for new plugins when it starts up, so you must close and reopen the program after installing anything. If you don't restart, the plugin won't appear in your browser even though the files are in the right place.

Can I use the same plugin in multiple DAWs?

Yes, if the plugin is in a shared system folder like the VST folder. Both FL Studio and other DAWs will find it there. However, some plugins require separate licenses for each DAW, so check the plugin maker's terms before assuming you can use it everywhere.

What's the difference between VST, VST3, and AU?

These are plugin formats — different ways plugins communicate with your DAW. VST and VST3 work on Windows and Mac. AU only works on Mac. FL Studio supports all three, but you need the right format for your operating system. Most modern plugins come in multiple formats, so you can usually choose.

Why does my plugin sound different in FL Studio than in other programs?

Some plugins behave slightly differently depending on the DAW's settings. Check the plugin's documentation and FL Studio's audio settings. Also verify that the plugin is using the same sample rate and buffer size in both programs — mismatches can cause subtle audio differences.

Can I move a plugin to a different folder after installing it?

Yes, but FL Studio needs to find it again. If you move a plugin folder, restart FL Studio and it will rescan. If FL Studio can't find the plugin in its old location, it may remove it from your projects. To avoid this, either use FL Studio's custom plugin paths feature or reinstall the plugin in its new location.

This guide is for general information only and is not medical, financial, legal, or other professional advice. For decisions specific to your situation, consult a qualified professional. See our Editorial Policy.