Where VST files go and how FL Studio finds them

FL Studio looks for VST plugins in specific folders on your computer. When you install a VST, it usually goes into one of these locations automatically — but if it doesn't, or if you download a VST manually, you need to tell FL Studio where to find it. The process is the same whether you're adding one plugin or fifty.

On Windows, VSTs typically land in C:\Program Files\Common Files\VST3 or C:\Program Files\Common Files\VST (the older format). On Mac, they go into /Library/Audio/Plug-Ins/VST3 or /Library/Audio/Plug-Ins/VST. If your VST installer asked you to choose a folder, check what you selected — it might be somewhere else entirely.

FL Studio can scan these folders automatically, but only if you tell it to. If a plugin doesn't show up after installation, the folder path is either wrong, or FL Studio hasn't scanned that location yet.

Key Takeaways

  • Most VST installers put plugins in the correct folder automatically, but you can manually point FL Studio to any folder where VSTs are stored.
  • FL Studio has separate settings for VST2 and VST3 plugins, and you may need to add paths for both if you use older and newer plugins.
  • After adding a new folder path, you must rescan or restart FL Studio before the plugins appear in your browser.
  • If a VST doesn't load, check that the file is actually in the folder you pointed FL Studio to, and that it matches your system architecture (32-bit or 64-bit).

Finding the VST settings in FL Studio

Open FL Studio and go to the top menu. Click Options, then scroll down and click File Settings. A window will open with several tabs on the left side. Look for the tab labeled Plugins — this is where you manage VST locations.

You'll see two sections: one for VST Plugins (the older VST2 format) and one for VST3 Plugins (the newer format). Most modern plugins are VST3, but some older ones are still VST2. You may need to add paths to both sections if you use a mix of old and new plugins.

The window shows a list of folders FL Studio is already scanning. If your VST is in one of these folders and still doesn't appear, the folder path might be wrong, or FL Studio needs to rescan.

Adding a new folder path for your VSTs

In the Plugins tab, look for a button that says Add or a plus icon. Click it. A file browser window will open. Navigate to the folder where your VST files are stored, then click Select Folder or OK. FL Studio will add that path to the list.

If you're not sure where your VST is, check the installation folder. Most VST installers create a folder with the plugin name — look for a file with a .dll extension (Windows) or .vst3 or .vst extension (Mac). The folder containing that file is what you want to add.

After you add the path, you'll see it appear in the list. Do not close the window yet — you need to rescan so FL Studio finds the plugins in that folder.

Rescanning and restarting to load new plugins

In the same Plugins tab, look for a button labeled Rescan. Click it. FL Studio will search all the folders in its list and look for VST files. This can take a few seconds if you have many plugins. When it finishes, any new plugins should appear in your browser.

If the rescan doesn't work, close FL Studio completely and open it again. A full restart sometimes forces FL Studio to reload the plugin list. After you restart, go back to Options > File Settings > Plugins and check whether the plugin now appears.

Once the plugin shows up in the Plugins tab, it should also appear in your browser when you're working on a project. Look in the browser panel on the left side of FL Studio — expand the Plugins folder and you should see your new VST listed there, ready to drag onto a track.

Fixing plugins that don't show up after adding them

If you added the folder path but the plugin still doesn't appear, check three things. First, make sure the VST file is actually in the folder you added — open the folder in Windows Explorer or Finder and look for the plugin file. Second, verify that the plugin matches your FL Studio installation. If you're running 64-bit FL Studio, you need 64-bit VST files. If you have 32-bit VST files, they won't load.

Third, check whether the plugin needs additional files to run. Some VSTs require a license file, a configuration file, or supporting libraries in the same folder. If the installer created multiple folders, you may need to add the parent folder instead of the plugin folder itself.

If you're still stuck, try removing the path and re-adding it. Sometimes FL Studio caches an old path and doesn't update it. Go to the Plugins tab, select the path you added, click Remove, then add it again and rescan.

Understanding VST2 versus VST3 in FL Studio

FL Studio supports both VST2 and VST3 formats. VST3 is newer and more efficient, but VST2 is still common, especially for older plugins. The difference matters because FL Studio has separate settings for each format — adding a VST2 plugin to the VST3 path won't work.

When you install a plugin, the installer usually puts it in the correct folder for its format. But if you're manually moving VST files around, make sure VST2 files go into the VST folder and VST3 files go into the VST3 folder. If you're not sure which format your plugin is, check the developer's website or look at the file extension — VST3 files often have .vst3 in the name.

If you have plugins in both formats, add paths to both the VST and VST3 sections in the Plugins tab. FL Studio will scan both locations and load everything that matches.

What to do if a VST loads but sounds wrong or crashes

Sometimes a VST appears in your browser and loads into a track, but it sounds distorted, plays at the wrong speed, or causes FL Studio to crash. This usually means the plugin is incompatible with your version of FL Studio, or it needs an update.

First, check the plugin developer's website to see if there's a newer version. Download and install the update, then rescan in FL Studio. If that doesn't help, try removing the plugin from the Plugins tab and restarting FL Studio. Some plugins conflict with each other or with FL Studio's settings, and a clean restart can fix it.

If the plugin crashes FL Studio every time you load it, you may need to uninstall it and contact the developer for support. Not all VSTs work with all versions of FL Studio, especially very old plugins or plugins designed for other DAWs.

Frequently Asked Questions

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

No, but you do need to rescan. Click the Rescan button in the Plugins tab and FL Studio will find any new plugins in your existing folders. A full restart is only necessary if rescan doesn't work or if the plugin crashes when you try to load it.

Can I use VSTs from other DAWs in FL Studio?

Yes, as long as they're in VST format. VSTs are designed to work across different music software. However, some plugins are built specifically for one DAW and may not work properly in FL Studio. Check the developer's website to confirm compatibility before installing.

What if my VST is in a .zip file?

Extract the .zip file first. Most VST installers are .zip files that unpack into an installer or a folder of plugin files. Once extracted, run the installer if there is one, or point FL Studio to the folder containing the plugin files. Do not try to add the .zip file itself to FL Studio.

Can I move VST files to a different folder after installing them?

You can, but you'll need to update the folder path in FL Studio afterward. If you move a VST to a new location, remove the old path from the Plugins tab, add the new path, and rescan. Some plugins store settings or license information in their original folder, so moving them may cause them to lose configuration data.

Why does FL Studio show a VST in the list but it won't load into a track?

This usually means the plugin file is corrupted, or it's the wrong architecture for your FL Studio version. Try removing it from the Plugins tab, restarting FL Studio, and reinstalling the plugin. If it still won't load, contact the plugin developer or try a different version of the plugin.