Where Are VST Plugins Stored? Default Paths on Windows and Mac

Default Plugin Folders at a Glance

Every plugin format has fixed default folders that DAWs scan on startup. If you just need to find an installed plugin — not install a new one — this table is the answer. For step-by-step installation and DAW rescan instructions, see how to install VST plugins.

Paths differ by format (VST2, VST3, AU, CLAP), operating system, and whether the plugin is installed for all users (system) or one account (user). Most installers drop files into system-wide folders automatically.

• VST2 Legacy Steinberg format. Still common on free plugins. Being phased out but many DAWs still scan VST2 folders.
• VST3 Current cross-platform standard. Steinberg defines the exact scan locations hosts must check^[1].
• AU Apple Audio Units — macOS only. Required for Logic Pro and GarageBand. Scanned by the Component Manager^[2].
• CLAP Open-source format (Bitwig, Reaper, FL Studio 2024.1+). Uses its own dedicated CLAP folder on both platforms^[4].

Windows Plugin Paths (VST2, VST3, CLAP)

On 64-bit Windows, most modern installers target the Common Files folders. Steinberg's VST3 specification defines two global scan locations: C:\Program Files\Common Files\VST3 for native 64-bit plugins and C:\Program Files (x86)\Common Files\VST3 for 32-bit plugins on 64-bit Windows^[1]. FL Studio also scans C:\Program Files\VST3 and the x86 equivalents^[4].

VST3 on Windows

System (all users): C:\Program Files\Common Files\VST3 — primary location for 64-bit VST3 bundles.

32-bit on 64-bit Windows: C:\Program Files (x86)\Common Files\VST3.

Per-user (development): %LOCALAPPDATA%\Programs\Common\VST3 — scanned first by VST3 hosts per Steinberg priority rules^[1].

VST2 on Windows

VST2 has no single enforced standard path, but these folders are scanned by most DAWs:

Common Files: C:\Program Files\Common Files\VST2 (64-bit)^[4].

Steinberg legacy: C:\Program Files\Steinberg\VSTPlugins (64-bit) and C:\Program Files (x86)\Steinberg\VSTPlugins (32-bit)^[6].

Alternate: C:\Program Files\VstPlugins — common on older free plugins. DAWs let you add custom VST2 search paths in their plugin manager.

CLAP on Windows

CLAP plugins install as .clap files to C:\Program Files\Common Files\CLAP^[4][5]. Bitwig Studio, Reaper, and FL Studio 2024.1+ scan this folder automatically.

macOS Plugin Paths (VST2, VST3, AU, CLAP)

macOS keeps audio plugins under Library/Audio/Plug-Ins/. FabFilter documents these as the only correct system-wide locations for manual installs^[3]. Steinberg's VST3 spec adds a per-user path scanned with higher priority than the global folder^[1].

Apple's Component Manager scans ~/Library/Audio/Plug-Ins/Components/ and /Library/Audio/Plug-Ins/Components/ for AU plugins, refreshing its registry on login and when folder timestamps change^[2]. Logic Pro does not load VST or CLAP — only AU.

The user Library folder (~/Library) is hidden by default in Finder. Use Go → Go to Folder (Cmd+Shift+G) and paste the full path to jump there directly.

User Folders vs System Folders

Plugins can live in two scopes. System folders (/Library/... on Mac, Program Files\... on Windows) are visible to every user account and require admin rights to write. User folders (~/Library/... on Mac, %LOCALAPPDATA%\... on Windows) install plugins for one account only — useful when you lack admin access or want to test a beta plugin without affecting other users.

For VST3, Steinberg defines scan priority: user paths are checked before global paths, and the first match wins^[1]. If the same plugin exists in both locations, the user-folder copy loads.

• Use system folders when Running the official installer with default settings — this is what 95% of producers should do.
• Use user folders when Manually copying a plugin without admin rights, or testing a single-user beta build.
• Avoid Installing VST plugins inside your DAW application folder (e.g. FL Studio's internal Plugins directory) — FL Studio explicitly warns against this^[4].

What Plugin Files Look Like on Disk

Knowing the file extension helps you confirm a plugin landed in the right folder before rescanning your DAW.

VST2 (Windows): a single .dll file per plugin (e.g. FabFilter Pro-Q 3.dll). VST2 (macOS): a .vst bundle (folder that looks like a file).

VST3: a .vst3 bundle on both platforms — a folder containing the plugin binary and metadata. On Windows it appears at C:\Program Files\Common Files\VST3\PluginName.vst3\.

AU (macOS only): a .component bundle in the Components folder. Each bundle contains an Info.plist and executable in Contents/MacOS/^[2].

CLAP: a single .clap file (not a bundle) in the CLAP folder^[5].

How to Open Plugin Folders Quickly

You do not need to dig through Finder or File Explorer manually every time. These shortcuts jump straight to the default scan paths.

1. Windows — paste a path
   Open File Explorer, click the address bar, paste e.g. C:\Program Files\Common Files\VST3, press Enter^[6].
2. macOS — Go to Folder
   In Finder, press Cmd+Shift+G, paste e.g. /Library/Audio/Plug-Ins/VST3/, press Enter^[3].
3. macOS — reveal user Library
   For ~/Library/Audio/Plug-Ins/, use Go to Folder with the tilde path. The user Library is hidden by default in Finder.
4. Confirm the plugin file
   Look for a .vst3, .component, .clap, or .dll matching the plugin name. If it is missing, the installer may have used a custom path — check the vendor's docs.
5. Rescan in your DAW
   If the file is present but invisible in your DAW, trigger a plugin rescan. See how to install VST plugins for per-DAW rescan steps — this article covers locations only.

Why Your DAW Cannot Find a Plugin

A plugin on disk does not guarantee your DAW will list it. These are the most common mismatches between file location and DAW visibility.

Wrong format for your DAW: Logic Pro scans AU only — a VST3 in the correct VST3 folder still will not appear. Ableton on Windows does not load AU. Match format to DAW; see plugin formats VST, AU, and AAX for a full comparison.

Wrong bit depth: 32-bit VST2 plugins on 64-bit Windows often need a custom search path or bridging. VST3 on 64-bit Windows belongs in Common Files\VST3, not the x86 folder, unless it is a 32-bit build^[1].

Custom install path: Some installers let you pick a non-default folder. If you chose a custom location, add that path in your DAW's plugin manager — the default scan will miss it.

Needs rescan: After copying or installing a plugin manually, most DAWs require an explicit rescan before the plugin appears in menus.

Install, Rescan, and Browse Free Plugins

This page is a location reference — not an installation guide. Once you know where plugins live, follow how to install VST plugins for installer walkthroughs, DAW-specific rescan steps, and troubleshooting when plugins fail validation.

New to plugin formats? Read what is a VST plugin for a plain-language explainer, then browse best free VST plugins 2026 for production-ready tools that ship with correct installers targeting these default paths.

Paid vs free plugins often install to the same folders — the difference is licensing, not location. See free vs paid VST plugins if you are deciding what to install first.