FL Studio reads plugins from specific folders on your computer, and installation means copying the plugin files into those folders so FL Studio can find them
When you download a plugin for FL Studio, it does not automatically appear in your DAW. You need to place the plugin files in the correct location, then tell FL Studio where to look for them. The process differs slightly depending on whether you have a VST plugin (the most common format), a native FL Studio plugin, or an AU plugin on Mac.
Most plugin problems come from files ending up in the wrong folder or FL Studio not knowing to scan that folder. This guide walks you through the actual steps so your plugins show up in your browser and you can use them.
Key Takeaways
- VST plugins go into a specific VST folder on your hard drive, and FL Studio must scan that folder to recognize them.
- You may need to unzip downloaded plugin files before moving them to the correct location.
- FL Studio has separate scan settings for 32-bit and 64-bit plugins, and scanning can take several minutes the first time.
- If a plugin does not appear after scanning, check that you placed it in the right folder and that FL Studio is set to scan that location.
- Some plugins require additional software or a license file to work, which the plugin documentation will specify.
Where to put VST plugins on Windows
VST plugins on Windows go into one of two standard locations. FL Studio looks in both by default, but you should pick one and stick with it. The most common choice is Program Files because it keeps all your software in one place.
For 64-bit plugins (which is what most people use now), the path is: C:\Program Files\Common Files\VST3 or C:\Program Files\Common Files\VST. If you are using 32-bit plugins, use C:\Program Files (x86)\Common Files\VST. Open File Explorer, navigate to that folder, and paste your plugin files there. If the VST or VST3 folder does not exist, create it yourself by right-clicking in the Common Files folder, selecting New, then Folder, and typing the name.
Some people prefer to create their own VST folder outside of Program Files to keep things organized. You can do this, but you will need to tell FL Studio where it is later in the scanning step.
Where to put plugins on Mac
Mac users have different standard locations depending on plugin format. AU plugins go into /Library/Audio/Plug-Ins/Components. VST plugins go into /Library/Audio/Plug-Ins/VST. Open Finder, press Command+Shift+G to open the Go to Folder dialog, paste the path, and press Enter. Then drag your plugin files into that folder.
If you see a folder called Plug-Ins but no Audio subfolder, create the Audio folder yourself. Some older plugins may require VST3 instead of VST, in which case the path is /Library/Audio/Plug-Ins/VST3.
Unzip plugin files before moving them
Most plugins download as a .zip file. You must unzip this file before moving the contents to your VST folder. On Windows, right-click the .zip file and select Extract All, then choose where to extract it. On Mac, double-click the .zip file and it will unzip automatically.
After unzipping, look inside the extracted folder. You will usually see a file with a .dll extension (Windows) or .vst/.component extension (Mac). This is the actual plugin file. Some downloads contain an installer program instead — if so, run the installer and it will place the plugin in the correct folder for you. Do not move the installer itself into your VST folder.
Tell FL Studio to scan for new plugins
Once your plugin files are in the correct folder, open FL Studio and go to Options in the menu bar. Select File Settings, then click the Plugins tab. You will see a list of plugin scan paths. Make sure the folder where you placed your plugins is listed. If you used the standard Program Files location, it should already be there.
Click the Scan plugins button. FL Studio will search through all the folders in your scan paths and build a list of available plugins. This can take several minutes if you have many plugins. Do not close FL Studio while scanning is in progress. When the scan finishes, you should see your new plugins listed in the browser under the Plugins section.
If you created a custom VST folder outside of Program Files, click Add in the Plugins tab, navigate to your custom folder, and select it. Then run the scan again.
Check the 32-bit and 64-bit settings
FL Studio runs as a 64-bit application on modern computers, and it scans for 64-bit plugins by default. If you have an older 32-bit plugin, you need to enable 32-bit scanning. In the Plugins tab of File Settings, check the box next to Scan 32-bit plugins. Then scan again.
If you are not sure whether your plugin is 32-bit or 64-bit, check the plugin documentation or the file properties. On Windows, right-click the plugin file, select Properties, and look at the file type. A 64-bit VST will say VST Plugin, while a 32-bit VST will often say VST Plugin (32-bit) or similar.
Troubleshoot plugins that do not appear
If you placed a plugin in the correct folder and ran a scan but it still does not show up, check these things in order. First, verify the file is actually in the folder you think it is. Open File Explorer or Finder and navigate to your VST folder to confirm the plugin file is there. Second, make sure that folder is listed in FL Studio's scan paths. Go back to Options > File Settings > Plugins and look at the list of paths. If your folder is missing, add it and scan again.
Third, some plugins require additional files or a license to work. Check the plugin documentation to see if you need to install anything else or place a license file in a specific location. Fourth, try restarting FL Studio after scanning. Sometimes the browser does not refresh until you close and reopen the program. If the plugin still does not appear after all these steps, the plugin file itself may be corrupted — try downloading it again.
Frequently Asked Questions
Do I need to restart FL Studio after installing a plugin?
You should restart FL Studio after scanning for plugins to make sure the browser refreshes and shows the new plugins. Scanning itself does not require a restart, but restarting afterward is the safest way to ensure everything loads correctly.
Can I use both VST and VST3 plugins at the same time?
Yes. FL Studio scans both VST and VST3 folders and will load plugins from either location. You can organize your plugins however you prefer, as long as they are in one of the standard scan paths or a custom path you have added to FL Studio's settings.
What if a plugin crashes FL Studio when I try to use it?
A crashing plugin usually means the plugin is incompatible with your version of FL Studio or your operating system. Check the plugin documentation to see what versions of FL Studio it supports. If the plugin is very old, it may not work with current versions. Try updating FL Studio or the plugin, or contact the plugin developer for support.
Do I need to pay for plugins before installing them?
Some plugins are free and some require payment. Check the plugin website or documentation before downloading. Paid plugins usually come with a license file or activation code that you need to register. Free plugins typically work immediately after installation.
Can I move a plugin to a different folder after installing it?
Yes, but you will need to rescan plugins in FL Studio after moving them. If you move a plugin to a new location, FL Studio may not find it in the old location anymore. Move the files, then go to Options > File Settings > Plugins and click Scan plugins again to update the list.