You installed a plugin and now you need to find it. Maybe your DAW cannot see it, or you want to delete one properly.
There is no single VST folder on Windows. VST3 has one strict location, VST2 has about 6, and installers do not always use either.
Key takeaways
- VST3 goes to
C:\Program Files\Common Files\VST3. This is enforced by the format. - VST2 has no single home.
C:\Program Files\VSTPluginsandC:\Program Files\Steinberg\VSTPluginsare the most common. - Never move a VST3 file. Relocating it breaks links to its presets and interface assets.
- Searching your drive for
*.vst3finds anything an installer hid. - Sample libraries live somewhere different from the plugin itself, often on another drive.
Quick answer
VST3 plugins install to C:\Program Files\Common Files\VST3. VST2 plugins usually land in C:\Program Files\VSTPlugins or C:\Program Files\Steinberg\VSTPlugins, though installers vary. To find a specific plugin, open File Explorer, go to C:\ and search for *.vst3 or the plugin name.
Where are VST plugins stored on Windows?
It depends on the format. VST3 is strict, VST2 is not, and that difference explains most of the confusion.
| Format | Path | File type |
|---|---|---|
| VST3 (64-bit) | C:\Program Files\Common Files\VST3 | .vst3 |
| VST3 (32-bit) | C:\Program Files (x86)\Common Files\VST3 | .vst3 |
| VST2 (64-bit) | C:\Program Files\VSTPlugins | .dll |
| VST2 (Steinberg) | C:\Program Files\Steinberg\VSTPlugins | .dll |
| VST2 (32-bit) | C:\Program Files (x86)\VSTPlugins | .dll |
| CLAP | C:\Program Files\Common Files\CLAP | .clap |
Steinberg defines the VST3 path in the format specification, so hosts scan it automatically. VST2 predates that rule, which is why plugins from 1996 onwards ended up scattered.
Which folder should you actually use?
The table lists where things end up. This is what to do about it.
- VST3: accept the default and never touch it. The format depends on that path.
- VST2: pick 1 folder you own, such as
D:\VST2, and send every installer there. - Sample libraries: a second drive if you have one. They are the only part that gets large.
- Everything else: leave alone. Tidying plugin folders by hand causes more problems than it solves.
Decide once and apply it to every install after that. Mixed conventions built up over years are what make plugin folders unmanageable.
Where is the VST3 folder on Windows 11?
Same as Windows 10. C:\Program Files\Common Files\VST3 has not changed across versions.
Paste that path straight into the File Explorer address bar and press Enter. Faster than clicking through folders.
There is also a per user path at %LOCALAPPDATA%\Programs\Common\VST3. Hosts scan it first, and a few installers use it when they lack admin rights.
Pro tip
Pin your VST3 folder to Quick Access in File Explorer. You will open it more often than you expect, usually while checking whether an install actually worked. Right click the folder, choose Pin to Quick Access, and it sits in the sidebar permanently.
Where do I put VST plugins if I download a .dll file?
Some free plugins arrive as a zip containing a bare .dll rather than an installer. You place those yourself.
Extract the zip first. Running a plugin from inside a compressed folder does not work.
Copy the .dll into C:\Program Files\VSTPlugins, or your own VST2 folder. If the download included a folder with the same name as the .dll, move that too. It holds the presets.
How do I find where a plugin installed?
When an installer put a plugin somewhere unexpected, searching beats guessing.
- Open File Explorer and click This PC.
- Type
*.vst3in the search box for VST3, or the plugin name for anything else. - Wait for the search to finish. Indexing makes the first run slow.
- Right click a result and choose Open file location.
Your DAW also knows. Most plugin managers show the full path of every scanned plugin, which is quicker than searching the drive.
Can I move VST plugins or use a custom folder?
VST2, yes. VST3, no. That single rule covers most of it.
A .dll is self contained, so you can move it and point your DAW at the new folder. Take any matching data folder with it. A custom VST2 folder such as D:\VST2 is a good idea, because it needs no admin rights and survives a Windows reinstall.
VST3 bundles expect the standard path. Moving one can break its interface assets and preset links, and most hosts will not look elsewhere. I lost an afternoon to this before learning the rule properly.
Point your DAW at both your custom VST2 folder and the standard VST3 path. Our guide to a VST not showing up in FL Studio covers adding them.
Do not do this
Never install plugins inside your DAW’s own program folder. FL Studio warns against it directly. An update or reinstall can wipe the folder, and you lose every plugin you put there. Keep plugins somewhere your DAW does not manage.
Where are plugin sample libraries stored?
The plugin file and its content are separate. A synth might be 20 MB while its library runs to 40 GB.
Libraries usually sit in C:\ProgramData\ under the developer name, or C:\Users\[you]\AppData\Roaming\. Many installers let you send them to another drive.
Put large libraries on a separate SSD if you have one. Keep the plugin itself in the standard folder, since only the content needs the space.
Pro tip
Write down where you send sample libraries. When we set up a new machine, the plugins reinstalled in minutes and the libraries took a full day, purely because nobody could remember which drive held what. A text file in your VST folder costs nothing and saves that day.
Where do VST plugins install on a Mac?
macOS is tidier than Windows. Every format has 1 defined folder, and installers stick to it.
| Format | Path |
|---|---|
| VST3 | /Library/Audio/Plug-Ins/VST3 |
| VST2 | /Library/Audio/Plug-Ins/VST |
| AU | /Library/Audio/Plug-Ins/Components |
Press Cmd, Shift, G in Finder and paste a path to jump straight there. Each folder also has a per user version under your home directory, which hosts scan first.
Why can my DAW not find a plugin that is installed?
A plugin on disk does not mean your DAW knows about it. Most DAWs only scan folders you have listed.
Add the folder to your plugin search paths, then rescan. In FL Studio that is Options, then Manage plugins, with Verify plugins ticked.
Bit depth matters too. A 32-bit host cannot load a 64-bit plugin. The full list is in a VST not showing up in FL Studio, plus the Serum specific case.
How do I uninstall a VST plugin properly?
Use the official uninstaller when one exists. Check Settings, then Apps, before deleting anything by hand.
Deleting only the .vst3 or .dll leaves presets, licence files and sample content behind. That can be tens of gigabytes.
Rescan your DAW afterwards so the plugin database drops the removed entry. Skip that and it keeps offering a plugin that no longer exists.
Frequently asked questions
Do VST plugins work in every DAW?
Almost. Most DAWs on Windows and macOS load VST2 and VST3. Logic Pro and GarageBand are the exception, because they only accept AU plugins, so a VST only release will never appear in them.
What is the difference between the VST2 and VST3 folders?
VST3 has one mandatory path defined by Steinberg, so every host knows where to look. VST2 never had that rule, so plugins ended up spread across several folders.
Can I install VST plugins on a different drive?
Yes for VST2 and for sample libraries. Keep VST3 bundles in the standard Common Files path, because moving them breaks preset and interface links.
Why are my plugins in Program Files (x86)?
That folder holds 32-bit software. A plugin there is the 32-bit version, which a 64-bit DAW cannot load without bridging. Reinstall the 64-bit version instead.
Do I need admin rights to install VST plugins?
Yes for anything writing to Program Files. Without them an installer can report success while files are missing. Right click and choose Run as administrator.
Where does FL Studio look for plugins?
Only in the folders listed under Plugin search paths in Manage plugins. It scans the standard VST3 location by default, but any custom folder must be added manually.
Where to go next
If a plugin is in the right folder and your DAW still cannot see it, read a VST not showing up in FL Studio. For crashes rather than missing plugins, see FL Studio crashing when loading plugins, and for performance problems high CPU usage in FL Studio.
Filling that folder is the fun part. Start with the best free VST plugins, then plugin bundles worth buying. For specific jobs see the EQ plugins pros use, the best reverb plugins and compressors for transparent mixing.
Setting up a new machine? Compare DAWs on Windows versus Mac and FL Studio against Ableton Live. Decide once where VST plugins install on Windows, keep to it, and plugin management stops being a recurring chore.
