How to Install VST3 Guitar Plugins on Windows and Mac

How to Install VST3 Guitar Plugins on Windows and Mac

Installing a VST3 guitar plugin comes down to three things: run the installer, make sure the file lands in your system’s VST3 folder, and let your DAW rescan so it shows up. On Windows that folder is C:\Program Files\Common Files\VST3. On macOS it is /Library/Audio/Plug-Ins/VST3. Most problems come from a skipped rescan, a 32-bit host, or a file saved in the wrong place.
This guide walks through each step, then covers the failures that cost people an evening. It also explains what to look for in a guitar plugin before you install one.
TL;DR
- Run the plugin’s installer. If there isn’t one, copy the
.vst3file into the standard VST3 folder for your operating system. - Windows system folder:
C:\Program Files\Common Files\VST3. macOS system folder:/Library/Audio/Plug-Ins/VST3. - Rescan plugins in your DAW. Many hosts only look for new plugins when you tell them to.
- If a plugin doesn’t appear, check the architecture (64-bit plugin, 64-bit host), the folder, and whether the maker has a newer installer.
- Amp-simulation plugins need a real guitar signal through an audio interface. They are a different thing from MIDI guitar instruments.
Table of Contents
- What a VST3 guitar plugin is, and what it does
- Before you install: check three things
- Where VST3 plugins go
- Installing on Windows, step by step
- Installing on macOS
- Making your DAW find the plugin
- When the plugin doesn’t show up or won’t load
- Choosing a guitar plugin worth installing
- Our perspective
- Installing GothDSP plugins
- FAQ
- Sources
What a VST3 guitar plugin is, and what it does
VST3 is a plugin format. Your DAW (the host) loads the plugin and runs your audio through it. Guitar plugins come in two broad kinds, and mixing them up is the most common buying mistake.
MusicRadar draws the line between amp-simulation plugins, which recreate an amplifier and effects pedals and need a real guitar, and guitar VST instruments, which generate guitar performances from MIDI. The first kind gives you amp and pedal tones from your own playing. The second can supply string noise, harmonics, muted notes and other articulations without a guitar in your hands.
The plugins this guide has in mind are the first kind: you plug a guitar into an interface, open a track in your DAW, and the plugin shapes the tone. A good one gives you a full chain, with amp, pedals and effects, rather than a bare amp that needs five other plugins around it.

Before you install: check three things
Two minutes here saves a lot of troubleshooting.
1. Your DAW supports VST3
Most current hosts do. Ableton’s Windows guide says Live supports VST3 and VST2, and that since Live 10 it supports only 64-bit plugins. If your host is older or 32-bit only, a 64-bit plugin will not load in it, however correctly you install it.
2. The plugin matches your system
Read the plugin’s requirements: operating system, supported hosts, and 64-bit support. Ableton’s guidance points the same way: match the plugin’s system and host requirements, then install fresh on the machine you use rather than copying files over from another computer. Copying folders between computers tends to skip registration and license steps that an installer handles.
3. You have a way to get your guitar in
An amp plugin processes the signal it receives. You need an audio interface with an instrument input, and a buffer size low enough that monitoring doesn’t feel laggy. Many amp plugins also ship a standalone app, which lets you play without opening a DAW at all. That is useful for testing the install before you involve the host.
Where VST3 plugins go
The VST3 format has standard locations, so most hosts look in the same places. That is the main reason VST3 is easier than the old VST2 format, where each DAW could point to its own folder.
| System | Standard VST3 folder | Notes |
|---|---|---|
| Windows | C:\Program Files\Common Files\VST3 |
Ableton recommends installing on the system (C:) drive |
| macOS, system-wide | /Library/Audio/Plug-Ins/VST3 |
Steinberg’s standard location |
| macOS, current user only | ~/Library/Audio/Plug-Ins/VST3 |
Less common, per Steinberg; the Library folder is hidden |
On the Mac, Ableton’s macOS guide lists the system folders for each format: Components for AU, VST for VST2, and VST3 for VST3. It adds that plugins can instead sit in the matching folders inside your hidden user Library.
Steinberg also notes that installation paths vary by format, operating system, manufacturer, architecture and customization. So if a plugin’s installer offers a custom path, think twice before changing it. The default exists so every host finds the plugin without extra setup.
Installing on Windows, step by step
- Download the installer from the maker’s site while logged in to the account you bought or trialed with.
- Close your DAW. Some installers can’t write to the plugin folder while a host has it open.
- Run the installer and keep the VST3 option ticked. If it offers a standalone app, install that too.
- Accept the default path,
C:\Program Files\Common Files\VST3, unless you have a reason to change it. - Open the standalone app first, if there is one. Confirm your interface is selected and you hear your guitar.
- Open your DAW and rescan (see below).
- Add the plugin to an audio track, not an instrument track, since you’re feeding it a guitar signal.
If the plugin arrives as a bare .vst3 file or folder with no installer, copy it into the VST3 folder yourself. Windows will ask for administrator permission to write there.
Installing on macOS
The flow is the same: run the installer, accept the default location, rescan in your host. If you copy manually, put the .vst3 bundle in /Library/Audio/Plug-Ins/VST3. To reach the per-user folder, hold Option in Finder’s Go menu to reveal Library. If you’re a guitarist on a Mac, our Mac page tells you where we stand there.
One rule from Ableton is worth remembering: VST2 and VST3 must live in separate folders, and any custom folders you set for them must differ. Don’t point both at the same place.

Making your DAW find the plugin
Installed does not mean visible. Hosts keep a plugin list, and a new file often isn’t in it until a scan runs.
Ableton Live
In Live’s plugin preferences, enable the plugin source (on Windows, the VST3 system folder option), then let Live scan. Ableton says to enable the right plugin source and allow the scan to complete. Use the default folder so the scan doesn’t need a custom path.
Cubase and Nuendo
iZotope’s guide recommends opening Studio > Plug-in Manager, adding the VST3 path if necessary, and clicking Re-scan All.
FL Studio
FL Studio has a plugin manager in its settings with a scan command. Run it after installing. Keep VST3 plugins in their default system folders; don’t count on custom search paths to find them.
Other hosts
Reaper, Studio One, Bitwig and the rest all have a plugin page in preferences with a rescan or refresh option. Look for it, run it, and restart the DAW if the plugin still doesn’t appear.
When the plugin doesn’t show up or won’t load
Work through these in order. The first three fix most cases.
- Rescan again. Clear the plugin cache if your host offers it, then scan.
- Check the path. Steinberg’s advice is to confirm the host monitors the folder where the plugin was installed. A file in a custom folder the host doesn’t watch is invisible.
- Check architecture. Per Steinberg, a 32-bit host can’t load a 64-bit plugin. Make sure both are 64-bit.
- Reinstall the latest version. If the install is corrupted, look for a manufacturer update and reinstall rather than patching files by hand.
- Check the format. If your DAW only takes AU or VST2, a VST3-only plugin won’t appear. On a Mac, Ableton treats AU, VST2 and VST3 as a matter of preference, so you can use whichever format your plugin ships.
- Test the standalone app. If it works standalone but not in the host, the audio engine is fine and the problem is the host’s plugin list.
Pro Tools is a special case. Some readers ask whether it runs VST3. Avid’s host has its own plugin format, so check the plugin maker’s compatibility list before buying, rather than assuming a VST3 will load.
Choosing a guitar plugin worth installing
With the install sorted, the question is what to put in the folder. Based on MusicRadar’s comparison points, weigh these:
- Plugin type. Amp and effects plugin or MIDI guitar instrument? Decide which problem you’re solving.
- Your style. A plugin built for scooped high-gain tone and one built for hazy cassette-warped indie are different tools.
- DAW compatibility. Confirm your host and OS are supported.
- Whether the chain is complete. Check whether amps and effects suit your needs without a pile of add-ons.
- Trial access. Install it, play your own guitar through it, and decide with your own ears.
For metal, look for tight low-end, gain staging and a way to drop tuning. For lo-fi indie, look for tape character, wobble and noise that sounds like a machine and not a filter.
Our perspective
We build guitar plugins, and most support questions we hear are not about tone. They are about the first ten minutes: the plugin installed, but the DAW can’t see it. So we make installation boring on purpose. Each plugin ships as a VST3 and a standalone app, with the full chain in one plugin and no add-on modules to chase.
Our advice to any guitarist: open the standalone first. If you hear your guitar there, your audio setup works, and anything wrong afterward is a host scan or a path. That one habit splits troubleshooting in half.
The other thing we care about is real-time polyphonic detune. It lets you drop tuning on chords and multi-string playing without retuning the guitar. Because it runs live, it has to be stable inside a DAW session. We’d rather you test that with a trial, on your own machine and your own interface, than trust a demo video.
— Louis
Installing GothDSP plugins
Our plugins for Windows come as VST3 and standalone apps, and the install follows the steps above. Each one is a complete chain, and you can try it before you buy.
| Plugin | What it’s for | One-off price | Monthly |
|---|---|---|---|
| Requiem | Metal amp with detune | €59 | from €5.99 per month |
| Septem | Dual-guitar plugin with harmonizer | €69 | from €6.99 per month |
| Somnia | Lo-fi indie with tape effect | €49 | from €5.99 per month |
| Vulgaris | Groove metal with whammy and detune | €69 | from €6.99 per month |
| Fuscus | Hard rock “brown sound” with Variac and flanger | €69 | from €6.99 per month |
The full list and checkout are on our pricing page. If you build chains in your DAW, our pedalboard workflow guide shows how to order amp, pedals and effects once it’s installed. You can also see the creators who play GothDSP in real musical settings.
FAQ
Where do I install VST plugins?
For VST3 on Windows, use C:\Program Files\Common Files\VST3. On macOS, use /Library/Audio/Plug-Ins/VST3, or the same path inside your user Library. The default folders are the safest choice because hosts check them automatically.
Why doesn’t my VST3 guitar plugin appear in my DAW?
Usually the host hasn’t rescanned, the file is in a folder the host doesn’t watch, or the host and plugin differ in architecture. Rescan first, then confirm both are 64-bit. If that fails, reinstall the latest version from the maker.
Can Pro Tools run VST3?
Not by assuming it. Pro Tools uses its own plugin format, so check the plugin maker’s supported hosts before you buy. DAWs such as Ableton Live, Cubase and FL Studio do load VST3.
What is the difference between an amp plugin and a guitar VST instrument?
An amp plugin recreates amps and pedals and processes a real guitar signal. A guitar VST instrument generates guitar sounds from MIDI, with articulations like harmonics and muted notes. Pick by whether you play guitar or program it.
Sources
- Best guitar VSTs 2026, MusicRadar
- Using VST plug-ins on Windows, Ableton
- Using AU and VST plug-ins on macOS, Ableton
- VST plug-in locations on Mac OS X and macOS, Steinberg
- Locating plug-ins within Cubase or Nuendo, iZotope