Adding a plugin to FL Studio means placing the plugin file in the right folder and then loading it into a track

FL Studio looks for plugins in specific locations on your computer. When you install a plugin, it usually goes into one of those folders automatically. If it doesn't, you move the file there by hand. Then you open FL Studio, refresh the plugin list, and the plugin appears in your browser ready to use on any track.

The exact steps depend on whether you're using Windows or Mac, and whether the plugin is a VST, VST3, or AU file. But the core idea is the same: file goes in folder, FL Studio finds it, you use it.

Key Takeaways

  • Most plugins install automatically to the correct folder, but you can check by opening FL Studio's plugin settings and looking at the scan paths.
  • Windows users typically find VST plugins in C:\Program Files\Common Files\VST3 or C:\Program Files\Steinberg\VSTPlugins, depending on the plugin type.
  • Mac users should place AU plugins in /Library/Audio/Plug-Ins/Components and VST plugins in /Library/Audio/Plug-Ins/VST.
  • After moving a plugin file to the correct folder, use FL Studio's Refresh button in the browser to make it appear in your plugin list.
  • If a plugin doesn't show up after refresh, check that the file format matches your FL Studio version (32-bit or 64-bit) and that the plugin is compatible with your operating system.

Where FL Studio looks for plugins on Windows

FL Studio scans several standard folders when it starts up. The most common locations are C:\Program Files\Common Files\VST3 for VST3 plugins and C:\Program Files\Steinberg\VSTPlugins for older VST plugins. Some plugins also go into C:\Program Files\Common Files\VST.

When you install a plugin using its installer, it usually puts itself in one of these folders automatically. You don't have to do anything. But if you download a plugin as a standalone file—a .dll file, for example—you need to move it to one of these folders by hand.

To see which folders FL Studio is actually scanning, open FL Studio and go to Options > File Settings > Plugins. You'll see a list of scan paths. If your plugin is in one of those folders but FL Studio still isn't finding it, the plugin file itself might be corrupted or incompatible with your version of FL Studio.

Where FL Studio looks for plugins on Mac

Mac uses different plugin formats than Windows. AU (Audio Unit) plugins go in /Library/Audio/Plug-Ins/Components. VST plugins go in /Library/Audio/Plug-Ins/VST. VST3 plugins go in /Library/Audio/Plug-Ins/VST3.

These folders are hidden by default in Finder. To navigate to them, open Finder, press Command + Shift + G, and type the path. Then paste the plugin file into that folder. After you've moved the file, restart FL Studio or use the refresh button in the browser to make it appear.

Some older Mac plugins use a .component file format. These also go in the Components folder. If you're unsure which format your plugin is, check the file extension or the plugin's documentation.

How to refresh the plugin list in FL Studio

After you place a plugin file in the correct folder, FL Studio doesn't automatically see it. You need to tell FL Studio to look again. Open FL Studio and look at the browser panel on the left side of the screen. Find the Plugins section. At the top of the browser, you'll see a small circular arrow icon or a Refresh button. Click it.

FL Studio will scan the plugin folders again and add any new plugins it finds. This usually takes a few seconds. If the plugin still doesn't appear, try restarting FL Studio completely. Sometimes a full restart is needed for FL Studio to register a new plugin.

If you've refreshed and restarted but the plugin still isn't showing up, check that the plugin file is actually in one of the scan paths. Open Options > File Settings > Plugins again and verify the folder location matches where you put the file.

Checking if your plugin is 32-bit or 64-bit

FL Studio comes in both 32-bit and 64-bit versions. A 32-bit plugin won't load in 64-bit FL Studio, and vice versa. Most people use 64-bit FL Studio now, so most new plugins are 64-bit. But if you're using an older plugin or an older version of FL Studio, this mismatch can cause problems.

To check which version of FL Studio you have, open FL Studio and go to Help > About. It will tell you whether you're running 32-bit or 64-bit. Then check your plugin's documentation or the plugin developer's website to confirm what bit version the plugin is. If they don't match, you either need to upgrade the plugin or switch to a different version of FL Studio.

Some plugin developers offer both versions for download. If that's the case, download the 64-bit version if you're running 64-bit FL Studio.

What to do if a plugin won't load after you add it

A plugin file in the right folder doesn't always mean FL Studio can use it. The plugin might be corrupted, incompatible with your operating system, or missing a required library file. Start by checking the plugin developer's website for known issues or updated versions. Sometimes a newer version of the plugin fixes compatibility problems.

If the plugin is brand new and you just downloaded it, try downloading it again. The file might not have transferred completely the first time. After you download it again, move it to the correct folder and refresh FL Studio.

If the plugin still won't load, check FL Studio's error log. Go to Options > File Settings > Plugins and look for any error messages related to the plugin. These messages often tell you exactly what went wrong—for example, "missing dependency" or "incompatible architecture". Search the plugin developer's support page for that specific error message.

Using a plugin once it's loaded in FL Studio

Once a plugin appears in your browser under Plugins, you can drag it onto a track or onto the master channel. When you do, a window opens showing the plugin's controls. You can adjust knobs, sliders, and buttons just like you would with FL Studio's built-in effects.

Some plugins are instruments—they make sounds when you play notes. Others are effects—they change the sound of a track. The plugin's documentation will tell you which type it is. Instrument plugins go on a new mixer track. Effect plugins go on an existing track or the master channel.

If you use the same plugin on multiple tracks, FL Studio creates a separate instance for each one. That means you can adjust the settings differently on each track without affecting the others.

Frequently Asked Questions

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

No. Using the refresh button in the browser usually finds new plugins without restarting. But if a plugin still doesn't appear after you refresh, try closing and reopening FL Studio. A full restart sometimes helps FL Studio register a plugin that the refresh button missed.

Can I put plugins in any folder I want?

No. FL Studio only looks in the standard plugin folders. If you put a plugin file anywhere else, FL Studio won't find it. You have to move it to one of the scan paths listed in Options > File Settings > Plugins.

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

These are different plugin formats. VST and VST3 work on Windows and Mac. AU only works on Mac. FL Studio supports all three. When you download a plugin, the developer tells you which format it is. Download the format that matches your operating system.

Why does my plugin show up in the browser but won't play sound?

The plugin might be loading but not working correctly. Make sure you've placed it on the right track—instrument plugins need their own mixer track, and effect plugins need to be on a track that has audio. Also check that the plugin's output volume isn't turned all the way down. If it still doesn't work, try the plugin developer's support page or download a newer version.

Can I delete a plugin after I add it to FL Studio?

Yes, but only after FL Studio is closed. If you delete the plugin file while FL Studio is running, FL Studio might crash or behave strangely. Close FL Studio first, delete the file from the plugin folder, then reopen FL Studio. The plugin will no longer appear in your browser.