Where Do VST3 Plugins Go? Install Paths, VST2 vs VST3 and CLAP

On Windows, VST3 plugins go in C:\Program Files\Common Files\VST3. On macOS they go in /Library/Audio/Plug-Ins/VST3 for all users, or ~/Library/Audio/Plug-Ins/VST3 for one user. Those paths are fixed by the VST3 specification, so unlike VST2 you do not choose them. Audio Units live in /Library/Audio/Plug-Ins/Components.

Disclosure: we make audio plugins, and one free one of ours is mentioned at the end. This guide is format documentation and applies to any developer's plugins equally. No affiliate links.

The Install Paths, In Full

On macOS the paths starting with /Library install for every user on the machine. The same paths prefixed with ~ install for the current user only. The user folder is hidden by default: in Finder press Command, Shift and G, then type the path.

Why VST3 Has a Fixed Location and VST2 Did Not

VST2 let each installer put files anywhere, then required you to tell the DAW which folders to scan. That flexibility produced the single most common support problem in music software: plugins scattered across four directories, a DAW scanning three of them, and a user certain the installer had failed.

VST3 fixed the path in the specification. Every installer writes to the same place, every host looks in the same place, and the mismatch disappears. It is worth knowing this because it explains why a VST3 has no "choose install folder" step, which occasionally reads as the installer being broken when it is not.

The trade-off is that a VST3 is a bundle rather than a single file. On Windows a VST3 may appear as a folder rather than a .vst3 file, and that is normal.

VST2 vs VST3: What Actually Changed

VST3 is not simply a newer version number. The relevant differences for a producer:

• Silence processing. A VST3 can tell the host it is receiving silence, and the host can stop processing it. On a session with fifty instances this measurably reduces CPU load. VST2 processes silence at full cost.
• Sample-accurate automation. Automation resolution is no longer tied to the audio buffer size, so fast parameter moves land where you drew them.
• Flexible channel configuration. A plugin can present mono, stereo and surround versions of itself rather than shipping separate builds.
• Better sidechain support. Sidechain inputs are part of the specification instead of a workaround.
• Resizable interfaces. Supported natively, which matters on high-resolution displays.

Steinberg ended VST2 licensing for new developers, so the format is in long-term decline. Existing VST2 plugins keep working in hosts that still support them, but new releases are increasingly VST3 only.

Practical answer to "should I use VST2 or VST3": use VST3 when both are offered. Keep the VST2 version installed only if you have older sessions that reference it, because a project saved with the VST2 instance will not always relink to the VST3 one. The two are separate plugins as far as your DAW is concerned.

CLAP, and Whether You Should Care Yet

CLAP is a newer open-source plugin format developed by Bitwig and u-he, free of licensing restrictions. Technically it improves on VST3 in a few areas: per-note modulation, better multi-threading support, and non-destructive parameter modulation.

Host support is the limiting factor. Bitwig, Reaper, FL Studio and several others support it. Others do not. For most producers today CLAP is a nice option when a favourite developer offers it and not a reason to change anything. If your host supports it and a plugin offers both, CLAP is a reasonable choice.

When a Plugin Does Not Show Up

Work through these in order. The overwhelming majority of cases are one of the first three.

1. Rescan the plugin folder. Most hosts cache their plugin list. In FL Studio: Options, then Manage plugins, then Find more plugins. Image-Line documents the scanner in the FL Studio manual. Other hosts have an equivalent under preferences.
2. Check the architecture. A 32-bit plugin will not load in a 64-bit host without a bridge. Nearly everything is 64-bit now, but old downloads are not.
3. Check you installed the format your host supports. Logic Pro loads Audio Units and not VST. Pro Tools loads AAX and not VST. Installing a VST3 for Logic produces exactly the symptom of a plugin that does not appear.
4. On Apple Silicon, check native versus Rosetta. A host running under Rosetta will not see arm64-only plugins, and a native host will not load Intel-only plugins without a bridge. Universal binaries avoid the problem entirely.
5. Look for a failed scan list. Most hosts keep a record of plugins that crashed during scanning and then skip them permanently until you clear it.
6. Confirm the file is actually in the fixed path. Some installers offer a custom location for VST2 and silently place VST3 correctly, so people look in the wrong folder.

Unsigned Installers on macOS and Windows

Small developers frequently ship without a code-signing certificate, because signing requires paid developer program membership on both platforms. The result is a one-time warning, not a sign of a problem with the file.

macOS Sequoia and later: the first attempt is blocked. Open System Settings, go to Privacy and Security, scroll to the security section, and choose Open Anyway next to the blocked item. You will be asked once more to confirm.

Older macOS: right-click, or Control-click, the installer and choose Open from the context menu rather than double-clicking. That presents an Open button the normal launch path does not.

Windows: SmartScreen shows a blue panel. Click More info, then Run anyway.

Only do this for files from a source you trust. The prompt exists for a reason; it simply cannot distinguish between a small developer and a bad actor.

Housekeeping That Prevents Most Problems

• Do not keep VST2 and VST3 of the same plugin active unless you need the VST2 for old sessions. Two entries for one plugin causes confusion later.
• Never rename a plugin file. Hosts identify plugins by an internal unique identifier, but sessions can reference paths. Renaming breaks the link.
• Uninstall properly. Deleting the file leaves preference and preset folders behind. Use the uninstaller when one is provided.
• Back up your presets folder separately. It usually lives in Documents or Application Support and is not covered by a plugin reinstall.
• Keep one plugin folder, not four. The single most useful habit for anyone still using VST2.

Format Support by DAW

This table explains a lot of confusion. Logic and Pro Tools users cannot use VST at all, which is why developers ship Audio Unit and AAX builds separately. Sound On Sound has tracked the format landscape across two decades of changes.

Keeping a Plugin Library Manageable

Install paths solve half the problem. The other half is what happens after two years of collecting.

Audit once a year. Open your plugin folder and remove anything you have not loaded in twelve months. A shorter list is faster to scan and faster to choose from, and scan time on session load adds up.

Use your host's favourites system. Most DAWs let you flag plugins and hide the rest. Working from a shortlist of fifteen you know well produces better records than browsing two hundred you do not.

Keep installers, not just plugins. When a machine dies, redownloading forty installers from forty developer sites is a lost weekend. A folder of installers on an external drive is worth the space.

Note which sessions use which plugins. If you uninstall something a two-year-old session depends on, that session will open with a missing-plugin placeholder and no settings. This is the strongest argument for leaving free plugins installed even when you stop using them.

Be careful with beta versions. A beta that crashes during scanning can land on your host's failed-plugin list, which then silently skips it even after you install a stable build.

From Our Own Line

Our plugins ship as VST3 for macOS and Windows, and as Audio Unit for macOS, so they install to the fixed paths above. VEIL is free and is a reasonable thing to test your install path with: download it, run the installer, rescan, and if it appears then your scanning setup is correct. It is keyless, with no account required, and it installs on every machine you own.

Our 1.0.0 installers are not code-signed yet, so the one-time warning described above applies. The steps are included in a notes file inside every download.

If you are setting up a vocal chain after getting plugins installed, our chain guide covers the order to put them in.

Frequently Asked Questions

Where do VST3 plugins go?

On Windows, C:\Program Files\Common Files\VST3. On macOS, /Library/Audio/Plug-Ins/VST3 for all users or ~/Library/Audio/Plug-Ins/VST3 for the current user. These paths are fixed by the VST3 specification and cannot be changed.

Should I use VST2 or VST3?

VST3 when both are offered. It uses less CPU on silent tracks, has sample-accurate automation and better sidechain support. Keep VST2 installed only for older sessions that reference it, because a project saved with a VST2 instance will not always relink to the VST3 version.

What is the difference between VST and VST3?

VST3 adds silence processing to cut CPU use, sample-accurate automation independent of buffer size, flexible channel configurations, native sidechain inputs and resizable interfaces. It also uses a fixed install path, where VST2 allowed any folder.

Why is my VST3 not showing up in FL Studio?

Usually the plugin list needs rescanning: Options, Manage plugins, Find more plugins. If that fails, check the plugin is 64-bit, confirm it is in the fixed VST3 path, and look for a failed-scan list that may be skipping it.

Is CLAP better than VST3?

CLAP has technical advantages including per-note modulation and better multi-threading, and it is free of licensing restrictions. Host support is narrower. If your DAW supports CLAP and a developer offers it, it is a reasonable choice, but it is not yet a reason to change your setup.

Why does macOS say the plugin installer cannot be opened?

The installer is not code-signed, which is common for small developers. Open System Settings, go to Privacy and Security, and choose Open Anyway. On older macOS, right-click the installer and choose Open instead of double-clicking.