How to Install VST Plugins (Windows & Mac): Complete 2026 Guide

Plugin Formats: VST3, VST2, AU, and CLAP

Before you install anything, you need to know what you are installing. Plugin files look like ordinary installers or zip archives, but the format they deliver — VST3, VST2, AU, or CLAP — determines which DAWs can load them and where they need to live on your drive.

The short version: VST3 is the default for Windows and is now standard on Mac. AU (Audio Unit) is the Apple-native format and the only format Logic Pro supports. VST2 is a legacy format — Steinberg stopped issuing new VST2 development licenses in October 2018,^[1] so any plugin released after that date that still ships a VST2 version is doing so under a pre-existing license. CLAP is a newer open-source format gaining traction in REAPER, Bitwig, and FL Studio — useful to know about but not yet universal.

Most free plugins you download from Plugg Supply or anywhere else will ship a VST3 installer (and an AU for macOS users). If a plugin offers both VST3 and VST2, install VST3. It is more CPU-efficient, supports resizable interfaces, and installs to a standardized path every DAW already knows about.^[2]

Default Plugin Folder Paths

These are the paths every compliant DAW scans automatically. Install to these locations and you will never have to configure anything manually. All paths below are from the Steinberg VST3 Developer Portal^[3] and the official CLAP specification.^[4]

Windows Plugin Paths

The Steinberg specification defines two VST3 scan locations on Windows,^[3] scanned in priority order:

System-wide (most common): C:\Program Files\Common Files\VST3\ — this is where every VST3 installer drops files by default. All 64-bit, modern DAWs scan here first.

Per-user install (priority 1, if present): %LOCALAPPDATA%\Programs\Common\VST3\ — expands to something like C:\Users\YourName\AppData\Local\Programs\Common\VST3\. Used when installing without administrator rights. Most DAWs scan both locations.

VST2 legacy path: C:\Program Files\VSTPlugins\ or wherever the installer puts it — VST2 has no mandated single location, so paths vary. Your DAW will need to be told about it explicitly.

CLAP: C:\Program Files\Common Files\CLAP\ (system) or %LOCALAPPDATA%\Programs\Common\CLAP\ (per-user).^[4]

macOS Plugin Paths

On macOS, the Steinberg spec^[3] defines the following locations:

System-wide VST3: /Library/Audio/Plug-Ins/VST3/ — installed for all users, requires admin password. Confirmed as the primary scan path by Ableton.^[2]

Per-user VST3: ~/Library/Audio/Plug-Ins/VST3/ — the tilde expands to your home folder. Installed without admin rights. Most DAWs scan this path too.

AU (Audio Unit): /Library/Audio/Plug-Ins/Components/ (system-wide) or ~/Library/Audio/Plug-Ins/Components/ (per-user). These are the only formats Logic Pro loads.^[5]

VST2 (legacy): /Library/Audio/Plug-Ins/VST/ — less common, increasingly irrelevant.

CLAP: /Library/Audio/Plug-Ins/CLAP/ (system) or ~/Library/Audio/Plug-Ins/CLAP/ (per-user).^[4]

Installing Plugins on Windows

1. Download the plugin installer
   Most reputable plugins ship an .exe or .msi installer. Avoid randomly named .dll files floating around forums — if there is no official installer, get the plugin from the developer's site or a trusted source like Plugg Supply.
2. Run the installer as Administrator
   Right-click the installer and choose Run as administrator. This ensures the plugin writes to C:\Program Files\Common Files\VST3\ — the system path every DAW scans. If you run without admin rights, the installer may use the per-user path instead (%LOCALAPPDATA%\Programs\Common\VST3\), which is fine as long as your DAW also scans that location.^[3]
3. Follow the installer's format selection screen
   Most installers let you choose which formats to install (VST3, VST2, AAX). On Windows, selecting VST3 is always the right call. Skip VST2 unless you have a specific reason to need it.
4. Confirm the install path
   The installer should show the destination: C:\Program Files\Common Files\VST3\. Do not change this path unless you have a deliberate folder strategy. Changing it means you will have to manually add that custom folder to every DAW's search list.
5. Open your DAW and run a plugin scan
   After installation, open your DAW and trigger a plugin rescan. Each DAW has a different menu path — see the DAW-specific steps in the next section.

If a plugin ships as a raw zip with a .vst3 bundle inside (some free tools do this), manually copy the .vst3 folder into C:\Program Files\Common Files\VST3\. On Windows, a .vst3 is technically a folder with a specific internal structure — it looks like a file in Explorer but it is a directory. Copy the entire thing, not just what is inside it.

Installing Plugins on macOS

1. Download the installer — .pkg or .dmg
   Mac plugin installers usually come as a .pkg file (inside a .dmg disk image). Download, open the DMG, and run the PKG.
2. Choose the correct format
   The installer will ask which formats to install. If you use Logic Pro, select AU. For Ableton Live or FL Studio on Mac, select VST3. If you use both Logic and another DAW, install both AU and VST3.
3. Approve the macOS security prompt
   macOS Gatekeeper will block unsigned plugins by default. If you see a security warning, go to System Settings → Privacy & Security and click Allow Anyway for the blocked installer. This is standard behavior for third-party plugin developers who have not paid for Apple's notarization — it does not mean the plugin is malicious.
4. Verify the file landed in the right folder
   Open Finder, press Cmd+Shift+G, and type /Library/Audio/Plug-Ins/VST3/ (for VST3) or /Library/Audio/Plug-Ins/Components/ (for AU). Confirm your plugin file is there. If the installer ran without admin rights, check the user-level paths: ~/Library/Audio/Plug-Ins/VST3/ and ~/Library/Audio/Plug-Ins/Components/.^[3]
5. Scan in your DAW
   Open your DAW and trigger a rescan. On Mac, the VST3 and AU system paths are scanned automatically — you rarely need to add custom folders.

Apple Silicon note: if you are on an M-series Mac, check whether the plugin has a native ARM build. Plugins without an ARM build run through Rosetta 2, which works but uses more CPU. Most actively maintained free plugins ship universal (ARM + Intel) binaries by 2026.

Pointing Your DAW to the Plugin Folder

If you install to the standard system paths (C:\Program Files\Common Files\VST3 on Windows, /Library/Audio/Plug-Ins/VST3/ on Mac), most DAWs will find your plugins automatically on the next scan. You only need to add a custom folder manually if you installed to a non-standard location. Here is how each major DAW handles it.

FL Studio

FL Studio scans the standard VST3 path automatically, but you can add custom paths in the Plugin Manager.^[6]

1. Go to Options → Manage Plugins (or press Ctrl+Shift+P).

2. In the Plugin search paths section, click the folder + icon to add a custom directory.

3. Enable Verify Plugins at the top of the Plugin Manager — this is required to correctly categorize VST3 and AU files (the fast scan mode only looks for .dll files by default).^[6]

4. Click Find more plugins / Find installed plugins. Wait for the scan to complete.

5. Your new plugin appears in the Browser under Plugin database → Installed → Effects → New or Generators → New.

Ableton Live

Ableton Live separates VST3 system folder, VST3 custom folder, and VST2 custom folder into distinct toggle switches.^[2]

1. Go to Options → Settings (Ctrl+, on Windows / Cmd+, on Mac) and click the Plug-ins tab.

2. Set Use VST3 Plug-in System Folder to On. This tells Ableton to scan C:\Program Files\Common Files\VST3\ (Windows) or /Library/Audio/Plug-Ins/VST3/ (Mac).

3. If your plugin is in a custom location, enable Use VST3 Plug-in Custom Folder and point it to that directory. Keep VST2 and VST3 folders separate — pointing the VST3 custom folder to the same location as VST2 will cause issues.^[2]

4. Click Rescan Plug-ins. To force a full rescan including previously blocklisted plugins, hold Alt (Windows) or Option (Mac) while clicking Rescan.

Logic Pro (macOS only — AU format)

Logic Pro only loads AU (Audio Unit) plugins. VST3 files installed to your system will be ignored by Logic entirely. Logic scans AU plugins from /Library/Audio/Plug-Ins/Components/ and ~/Library/Audio/Plug-Ins/Components/ automatically.^[5]

1. If Logic was open during installation, go to Logic Pro → Settings → Plug-in Manager.

2. Find your new plugin in the list and click Reset and Rescan Selection.

3. If the plugin still does not appear, click Full Audio Unit Reset at the bottom of the window. Logic will perform a complete from-scratch validation of all AU plugins on the next launch.^[5]

4. A green checkmark in the Compatibility column means the plugin passed AU validation. A red X means it failed — the plugin likely needs a different version or is incompatible with your macOS version.

Troubleshooting: Plugin Not Showing Up

You ran the installer, you rescanned, and the plugin is not there. Here are the most common causes, in order of likelihood.

• Wrong format for your DAW Logic Pro cannot load VST3 files, ever. If you installed only the VST3 version, reinstall and choose AU. Conversely, VST2/VST3 plugins will not appear in Logic regardless of where you put them.
• Plugin installed to a non-standard folder The installer placed the plugin somewhere custom (e.g. C:\VSTPlugins\). Open your DAW's plugin manager, add that folder to the search path list, and rescan. In Ableton, use VST3 Plug-in Custom Folder. In FL Studio, add the path in Manage Plugins → Plugin search paths.^[6]
• 32-bit plugin in a 64-bit DAW Modern DAWs — Ableton Live 10+, FL Studio 20+, Logic Pro — are 64-bit only. A 32-bit VST2 .dll will not load. Check the developer's downloads page for a 64-bit version.
• DAW blocklisted the plugin If the plugin crashed during a previous scan, your DAW may have added it to a blocklist and will skip it on future scans. In Ableton, hold Alt/Option while clicking Rescan to force-scan blocklisted plugins. In FL Studio, enable Re-Scan Plug-Ins with Errors in the scan options.^[6]
• Logic Pro AU validation cache is stale Logic caches AU validation results. If you installed or updated a plugin while Logic was running, the cache will not reflect it. Fix: go to Settings → Plug-in Manager → Full Audio Unit Reset. If that fails, manually delete ~/Library/Caches/AudioUnitCache/com.apple.audiounits.cache and relaunch Logic.^[5]
• macOS Gatekeeper blocked the installer If you skipped the security approval step, the plugin files may not have been written at all. Re-run the installer and allow it in System Settings → Privacy & Security → Allow Anyway before the prompt expires.
• VST3 Plug-in System Folder is disabled in Ableton In Ableton's Plug-ins preferences, Use VST3 Plug-in System Folder must be toggled On. If it is Off, Ableton ignores the entire standard system path and your plugins will never appear regardless of where they are installed.^[2]

Per-User vs. System Install: Which to Choose

The Steinberg VST3 specification defines two parallel path hierarchies: system-wide (requires admin rights) and per-user (no admin required).^[3] Both work. The differences are practical:

System install (C:\Program Files\Common Files\VST3\ on Windows, /Library/Audio/Plug-Ins/VST3/ on Mac): the plugin is available to all user accounts on the machine. Requires admin/sudo. This is the right choice for a personal production workstation.

Per-user install (%LOCALAPPDATA%\Programs\Common\VST3\ on Windows, ~/Library/Audio/Plug-Ins/VST3/ on Mac): the plugin is only available to your account. No admin required. Useful in shared studio environments where you do not want to affect other users' setups, or when installing on a machine where you do not have admin rights.

Most consumer installers default to the system path. If you are managing a large plugin library and want everything in one predictable location, stick with the system path and always run installers as administrator.