Yes, FL Studio runs third-party plugins, and on a Mac it takes both of the formats a plugin usually ships in. The part that trips people up is that FL does not show a plugin you just installed until you scan for it, and when one is missing there is no error telling you why.
VST2 and VST3 work on Windows and macOS; Audio Units work on macOS only. Paths below are the standard install folders. Menu names move around between FL Studio versions, so the wording here is described rather than quoted.
Yes. FL Studio hosts VST plugins, both the older VST2 and the current VST3, on Windows and on macOS. On a Mac it also loads Audio Units (AU), Apple's own format. Windows has no Audio Units, because AU is a macOS-only format and does not exist off the Mac.
So the format you reach for depends on the machine. On macOS you can use the AU (a
.component file) or the VST3 (a .vst3 file), and either one loads. On
Windows you use the VST, and the VST3 is the one to pick when a plugin offers both. FL Studio also
loads CLAP and its own native plugins, but for something you bought from another developer it is
almost always VST or AU.
FL Studio is not fussy about format the way Logic is: on a Mac it takes VST3 and AU, and on Windows it takes VST. What it will not do is show a plugin you just installed until you scan for it. That step, not the format, is what usually goes wrong.
Plugins install into the standard system plugin folders, and FL Studio picks them up when you run a scan in its Plugin Manager. An installer normally drops the files in the right folder for you. FL does not watch those folders live, though: a plugin you just installed shows up in FL only after a scan, which you start from the Plugin Manager.
These are the folders each format installs into. If you are copying a file by hand rather than running an installer, this is where it goes.
| Format | File | Default install folder |
|---|---|---|
| VST3 (Mac) | .vst3 |
/Library/Audio/Plug-Ins/VST3 |
| Audio Unit (Mac) | .component |
/Library/Audio/Plug-Ins/Components |
| VST3 (Windows) | .vst3 |
C:\Program Files\Common Files\VST3 |
| VST2 (Windows) | .dll |
C:\Program Files\Common Files\VST2 |
VST3 and Audio Units have fixed system folders that FL Studio already knows to scan.
Old-style VST2 plugins (a loose .dll) do not always land in the
standard folder, since their installers often let you pick any location. If yours is somewhere
else, add that folder under the Plugin Manager's plugin search paths, then scan again. VST3 and
AU do not need this, and most current plugins ship VST3, so you rarely have to touch it.
Almost always because FL Studio has not scanned it yet. Unlike Logic Pro, which checks its plugins every time it launches, FL Studio adds a new plugin only when you tell it to look. So the fix, nine times out of ten, is to open the Plugin Manager and run a scan. Work through these in order.
Installing a plugin does not put it in FL Studio. You have to open the Plugin Manager and run Find installed plugins with Verify plugins switched on, which scans the plugin folders and sorts what it finds into effects and instruments. If you updated a plugin, or one threw an error last time, run the scan again and let it re-scan plugins that previously failed. Nothing is harmed by scanning again.
Open the Plugin Manager (in current FL Studio it lives under the Options menu; the exact submenu wording changes between versions) and start a scan with verify switched on. This is the whole fix in most cases, so try it first.
VST3 and Audio Units sit in the fixed system folders in the table above, which FL scans on its
own. A VST2 .dll kept in a custom folder will not be found until you add that folder
under the Plugin Manager's plugin search paths, then scan again.
On Windows there is no Audio Units, so an AU never appears; use the VST there. On a Mac use the
.component or the .vst3. If the only file a developer ships is one your
platform cannot host, that plugin cannot run there.
FL Studio on macOS is 64-bit only, so a 32-bit plugin will not load at all. On Windows, a
64-bit FL Studio wants the 64-bit build of the plugin, and an old 32-bit .dll is a
common reason one does not appear. Install the 64-bit version.
Since macOS Catalina, an unsigned or unnotarized plugin can be blocked by Gatekeeper before FL ever scans it. If you got a security warning while installing, that is the cause. Anything from a real developer will be signed and notarized and will install with no warning.
FL Studio comes loaded with instruments and effects, and for a lot of tracks you do not need to add anything. The gap people tend to feel is not one more synth, it is a starting point for a line: something that hands you a bassline to react to instead of a blank Channel Rack.
REHEAT writes acid basslines on its own. You set a key and let it run, and it plays a line back at you instead of leaving an empty piano roll. When you like one, drag the MIDI straight into FL Studio and drop it on a channel, or play it live through your own synth with REHEAT MIDI DRIVER. It ships as an Audio Unit, a VST3 and an AAX for Pro Tools, so it installs into the standard folders above; scan once in the Plugin Manager and it is there with the rest.
Hear the whole thing free in your browser first, no install and no account.
We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.
Tunary