← All posts ·

5 Step VST3 Install: Put .vst3 in C:\Program Files\Common Files\VST3

5 Step VST3 Install: Put .vst3 in C:\Program Files\Common Files\VST3

Windows workstation used to install VST3 plugin

Put .vst3 bundles in the VST3 system folder: on Windows that's C:\Program Files\Common Files\VST3, and on Linux it's typically ~/.vst3 for a per-user install. Only use a custom folder if the installer chose one or your DAW specifically requires it. A 32-bit VST3 on 64-bit Windows goes in C:\Program Files (x86)\Common Files\VST3, but check your host's support for 32-bit plugins first.

TL;DR:

  • Installing VST3 plugins in the default system folder ensures compatibility across most major DAWs without additional configuration.
  • Support for 32-bit VST3 plugins on 64-bit Windows varies by host, so check your DAW's documentation before using older builds.
  • On Linux, per-user plugins should go into "~/.vst3," while system-wide ones are best placed in "/usr/lib/vst3," with proper ownership and permissions.
  • Moving only parts of a .vst3 bundle causes incompatibility; always copy or move the entire folder as a single unit.
  • Troubleshooting missing plugins involves confirming correct paths, forcing rescans, and ensuring file permissions are set correctly for your DAW and OS.

Table of Contents

Standard VST3 locations on Windows

The Steinberg Help Center specifies C:\Program Files\Common Files\VST3 as the dedicated path for 64-bit VST3 plugins, and this is the folder nearly every modern DAW scans by default. Plugins here show up as .vst3 bundles, not single .dll files; Steinberg's documentation treats the bundle structure as a requirement of the format, not an option.

VST3 bundle entering shared plugin folder

If you're dealing with an older 32-bit VST3 build running on 64-bit Windows, it belongs in C:\Program Files (x86)\Common Files\VST3. Support for 32-bit plugins varies by host: some DAWs dropped it entirely, others need a bridging tool. Check your DAW's documentation before assuming a 32-bit plugin will load.

Ableton's own documentation confirms that VST3 devices install by default to this same system folder and recommends leaving it as the primary location rather than adding scattered custom paths. Keeping everything in one place avoids duplicate scans and stale copies left behind by old installers.

One reliable fact: both Steinberg and Ableton point to the same default VST3 system folder on Windows, which means a plugin installed correctly by any vendor's installer should appear in any VST3-compatible host without extra configuration.

VST3 locations on Linux: user and system paths

Linux doesn't have a single enforced path the way Windows does, but conventions are consistent across most distributions. A Fedora Discussion thread on plugin directories confirms that per-user installs typically land in ~/.vst3, while system-wide installs go into a shared location such as /usr/lib/vst3, though this can shift depending on your distro's packaging rules.

When installing manually, make sure the user account running your DAW actually owns the files or at least has read access. A plugin copied in as root with restrictive permissions often fails silently rather than throwing an obvious error, so this step gets skipped more than it should.

How to install or move a .vst3 plugin

Whenever a vendor provides an installer, use it. Installers handle bitness, permissions, and path selection automatically, and deviating from that path is usually where problems start. Manual installation is for cases where you've downloaded a bare .vst3 bundle or you're migrating plugins to a new drive.

  1. Close your DAW completely before copying or moving any plugin files.
  2. Copy the entire .vst3 bundle, not just part of it, into the correct system folder for your OS.
  3. Reopen your DAW and trigger a plugin rescan from its plugin manager or preferences.
  4. If the installer placed files in a custom folder, add that folder to your DAW's plugin search paths instead of relocating it.
  5. Confirm the plugin appears in your plugin list before loading it into a project.

Pro Tip: Never split a .vst3 bundle between folders. It's built as a single unit, and moving only part of it will make the plugin invisible to every host that scans for it.

DAW scanning and common fixes when a VST3 doesn't appear

Most detection issues come down to three things: the DAW hasn't rescanned, the path isn't registered, or a permissions problem is blocking access. PreSonus documentation for Studio One notes that recent versions may also scan an AppData path in addition to the standard VST3 system folder, so checking your host's specific scan locations matters more than assuming one universal rule.

A checklist for missing plugins in Logic Pro walks through a similar diagnostic sequence for AU, and the same logic (confirm path, confirm extension, force a rescan) applies directly to VST3 troubleshooting on any host.

Best practices and gotchas with VST2, VST3, and duplicates

A handful of habits prevent most plugin detection headaches before they start.

Pro Tip: If a plugin worked yesterday and vanished today, check for a second copy installed by an old update before assuming the file is corrupted.

Vector DSP perspective: packaging and support guidance for VST3 installs

We package our plugin as a standard .vst3 bundle and recommend installing it straight into the system VST3 folder rather than a custom path, since that's what every major host scans by default. When a producer reports a missing plugin, our support checklist starts with the same handful of questions: the exact install path, confirmation the .vst3 file is actually present, whether a rescan was triggered, and which OS and DAW version are involved. For UI or latency issues once a plugin loads correctly, our plugin UI scaling guide and Cubase latency checklist cover the next layer of troubleshooting.

— Kai

ToneLab: download and install

We built ToneLab as a standard VST3 bundle, so the installation steps above apply directly: accept the installer's default system folder, or place the bundle there yourself if you're installing manually. This plugin brings multi-lane parallel effects with per-lane EQ targeting to VST3, AU, and AAX hosts, aimed at producers who want more surgical control over a mix than a single-lane processor allows.

Vector-dsp

If file formats for your finished mixes are also on your mind, this WAV versus MP3 breakdown from Twisby Records covers what actually changes between the two for working musicians.

FAQ

Where is the VST folder located on Windows?

Classic VST2 plugins typically install to C:\Program Files\Steinberg\VSTPlugins or a vendor-chosen folder, which is separate from the VST3 system folder. Keep VST2 .dll files out of the VST3 directory to avoid scan conflicts, as Ableton's documentation advises.

Where are VST3 plugins located in Windows 11?

The path hasn't changed from earlier Windows versions: VST3 plugins install to C:\Program Files\Common Files\VST3 for 64-bit builds, per Steinberg's official documentation. Some hosts, including recent Studio One releases, may also check an AppData path, so confirm your specific DAW's scan locations if a plugin doesn't appear right away.

Where should I place VST3 files during manual installation?

Copy the complete .vst3 bundle into C:\Program Files\Common Files\VST3 on Windows, or into ~/.vst3 for a per-user install on Linux. Close your DAW first, place the files, then reopen and run a plugin rescan.

Where do I find the VST2 folder on my system?

VST2 installations usually live in a vendor-specified folder under Program Files on Windows, separate from the shared VST3 system folder. There's no single universal VST2 path the way there is for VST3, so check your plugin's installer or documentation for its exact target.

What do I do if ToneLab doesn't show up after installing it?

Confirm the .vst3 bundle is sitting in your DAW's recognized VST3 path, then trigger a manual rescan from the plugin manager. If it's still missing, check that the installer didn't use a custom folder that needs to be added separately in your host's plugin preferences.

Sources

Recommended