How to add plugins to FL Studio, and what to do when one does not show up

To add a plugin to FL Studio, run its installer with the default folders, then open Options > Manage plugins, switch on Verify plugins and run Find installed plugins. New plugins appear in the Browser under Plugin database > Installed, in Effects > New and Generators > New. Tick a plugin’s F column to make it a favourite.

Updated 10 November 2026 by Sonisto, which makes the plugin manager this guide mentions. Every menu and folder below is from Image-Line’s FL Studio manual, read on 10 November 2026, when its change log named FL Studio 26.1.7.5 (12 October 2026) as the latest version.

Where FL Studio looks for plugins

VST3 and Audio Units plugins must be in these system folders, or FL Studio’s scan does not find them. Only VST2 plugins can live in a folder of your own, which you add in the Plugin Manager. On a Mac a few installers use your user Library (~/Library/Audio/Plug-Ins/) instead; Image-Line calls that rarely used. For every format and DAW, see where every plugin format installs.

Five steps

1. Install the plugin with its installer

Image-Line recommends the plugin’s own installer and its default install location. Copy files by hand only for an old plugin that has no installer. Never install into FL Studio’s own folder (…\Image-Line\FL Studio\Plugins\VST): that one is for FL Studio’s legacy native plugins.

2. Open the Plugin Manager

Choose Options > Manage plugins. The Add menu has the same Manage plugins command, and Image-Line’s install page reaches it through Options > File settings > Manage plugins. All three open the same window.

3. Scan with Verify plugins on

Switch on Verify plugins and run Find installed plugins. Verifying is slower: it opens each plugin, files it as an effect or a generator and notes whether it is 32 or 64 bit. Click away any pop-ups a plugin shows. After you update a plugin, also switch on Rescan previously verified plugins.

4. Find the plugin in the Browser

New plugins appear in the Browser under Plugin database > Installed, in Effects > New and Generators > New, and in the VST, VST3 or Audio Units subfolder for their format.

5. Make it a favourite

Tick the F (Favorite) column in the Plugin Manager. Favourites show in the Channel Rack + button, the Add menu and the plugin picker. You can also load the plugin, open its wrapper menu and choose Add to plugin database (flag as favorite), which saves it with the preset you set first.

When a plugin does not show up in FL Studio

Work down this list. The first two cover most cases.

• The scan did not verify. A fast scan (Browser > Plugin database, right-click, Refresh plugin list) only knows a plugin by its file name, so a renamed or updated plugin can go missing. Scan again with Verify plugins and Rescan previously verified plugins switched on.
• It is in a folder FL Studio does not search. A VST3 or AU plugin outside the system folders above is not found, and Plugin search paths cannot fix that: reinstall it to the default folder. A VST2 plugin in its own folder needs that folder added under Plugin search paths.
• The scan gave it an error. The Plugin Manager’s Plugins tab shows a Status of OK or Error for each plugin. Switch on Rescan plugins with errors and scan again; if it still fails, ask the plugin’s maker.
• It is the wrong format. FL Studio loads VST and VST3, and Audio Units on a Mac. An AAX download is for Pro Tools and never shows up. Windows and Mac VST files are not interchangeable either.
• It is 32-bit. FL Studio for Mac loads only 64-bit plugins, with no bridging. On Windows FL Studio bridges a 32-bit plugin by itself, at about 2% extra CPU per plugin.
• You switched mode on an Apple silicon Mac. FL Studio runs natively or under Rosetta 2, and you have to scan once in each mode.

Where did the installer put it?

None of this helps until you know which folder the plugin went to, and an installer can pick its own. Sonisto’s free scan lists the VST2, VST3, AU and AAX plugins on your computer, and a plugin’s Files table shows the Location of each format, with a button that opens it in Finder or Explorer. A VST3 copy outside the VST3 folder means a reinstall; a VST2 copy in its own folder goes under Plugin search paths. On a Mac, add /Library/Audio/Plug-Ins/VST in Sonisto’s Scanner with + Add path so VST2 plugins are listed too. The scan only reads what is installed. See every plugin and where it is installed: scan with Sonisto, free.

The Free plan covers one computer, one scan a month and update notices for 10 plugins. Basic and Pro show updates for every plugin and add the export and the comparison between computers. See the plans side by side.

Questions

Why are my plugins not showing up in FL Studio?

Usually the scan has not run since the install, ran without Verify plugins, or the plugin sits outside the folders FL Studio searches. Open Options > Manage plugins, switch on Verify plugins and Rescan previously verified plugins, and scan again. Then check the format: FL Studio does not load AAX, and on a Mac it loads no 32-bit plugins.

Where do I put VST plugins for FL Studio?

Let the installer use its default folder. VST3 plugins go in Program Files\Common Files\VST3 on Windows and /Library/Audio/Plug-Ins/VST3 on a Mac, and must stay there. VST2 plugins go in Common Files\VST2 on Windows or /Library/Audio/Plug-Ins/VST on a Mac, or in a folder you add under Plugin search paths.

How do I rescan plugins in FL Studio?

Open Options > Manage plugins, switch on Verify plugins, and Rescan previously verified plugins if you have updated some, then run the scan. For a quick check for new VST plugins only, right-click Plugin database in the Browser and choose Refresh plugin list (fast scan), which does not sort plugins into effects and generators.

Why does a plugin show up twice in FL Studio?

Often because its installer added both the VST2 and the VST3 version, and FL Studio lists each one. A fast scan can also put the same plugin under both Effects and Generators, because it does not open the plugin to check. A scan with Verify plugins files each plugin in the right place.

Does FL Studio work with 32-bit plugins?

On Windows, yes: FL Studio bridges a 32-bit plugin by itself, at about 2% extra CPU each, so ten or more bridged plugins start to cost you. FL Studio has been 64-bit only since version 20.9. On a Mac it loads only 64-bit plugins and does not bridge, so a 32-bit plugin never shows up.

More: how every DAW finds your plugins, how to add plugins to Ableton Live, VST, VST3, AU and AAX explained and installing a batch of new plugins after a sale. All guides.