What Is ~/Library/Audio/Plug-Ins/VST on Mac?
Your user folderUpdated
- Full path
~/Library/Audio/Plug-Ins/VST
- Scope
- Your user folderInside your home folder — one copy per user account.
- Freshist & this folder
- Freshist checks this folder when uninstalling an app. When you uninstall an app, Freshist looks here for items that belong to it. Matches on the app's bundle ID can be pre-selected; name-only guesses are labeled “not sure” and never pre-selected. Removed items go to the Trash, so you can undo.
From Freshist's own cleaning rules — the same catalog the app uses.
The format behind the folder
VST (Virtual Studio Technology) is Steinberg's plug-in standard for instruments and effects. This folder is for VST 2 plug-ins, which ship on macOS as bundles ending in .vst. The newer VST3 format uses its own folder, described in the VST3 guide.
The VST 2 standard never defined a mandatory location. Steinberg's help center notes that Mac installers settled on Apple's standard plug-in folders instead:
| Folder | Scope | Typical use |
|---|---|---|
/Library/Audio/Plug-Ins/VST | All users | Where nearly every installer writes |
~/Library/Audio/Plug-Ins/VST | Your account only | Rare: manual installs, per-user options |
Plug-ins installed somewhere else work too, but the host has to be told where to look.
Why it's often empty, and why it lingers
Steinberg announced in May 2018 that VST 2 was coming to an end and pointed developers to VST3. Existing plug-ins kept working, so many Macs still carry .vst files from older bundles and free plug-ins. Because uninstalling a music app never touches plug-in folders, VST 2 files can outlive the host they were bought for by years.
The folder doesn't take much space on its own. A typical .vst bundle is a few megabytes of code. Large instruments put samples and presets elsewhere, which is where the real gigabytes go.
Checking what's there
Read-only commands:
ls -la ~/Library/Audio/Plug-Ins/VST /Library/Audio/Plug-Ins/VST
du -sh ~/Library/Audio/Plug-Ins/VST
Most hosts also have a plug-in manager that lists each plug-in with its format and path. That's the quickest way to see whether a .vst is a duplicate of a VST3 or AU you already have.
Removing a VST 2 plug-in
Prefer the developer's uninstaller, which also removes presets, samples and license files stored outside this folder. To do it by hand:
- Quit every music app.
- In Finder, choose Go → Go to Folder… and enter
~/Library/Audio/Plug-Ins/VST. - Move the
.vstbundle to the Trash. - Reopen your host and rescan if it doesn't do so automatically.
Keep the Trash until you've opened the projects that matter. A missing plug-in leaves an empty slot, and the saved settings return if you restore the file.
What to leave alone
Don't remove the VST folder itself; installers expect it. Don't remove a .vst because it "looks old" if a project still uses it: a session pointing at a VST 2 plug-in won't always pick up the VST3 version automatically. If you also have Audio Units versions for Logic, those live separately in Components.
Sources
- VST plug-in locations on Mac OS X and macOS, Steinberg Help Center
- VST 2 SDK discontinued, Steinberg Forums
- macOS Library Directory Details, Apple File System Programming Guide
Frequently asked questions
Does Logic Pro or GarageBand use this folder?
No. Logic Pro and GarageBand only load Audio Units from the Components folders. VST plug-ins are for hosts such as Cubase, Ableton Live, Reaper, Bitwig Studio or Studio One.
Is it safe to remove a VST 2 plug-in if I also have the VST3 version?
Usually, but check your projects first. Some hosts can swap a VST 2 plug-in for its VST3 version automatically, others can't, and older sessions may still point at the VST 2 file.
Why does my host not see a plug-in I put in this folder?
The host may only scan the system folder, may need a manual rescan, or may not load VST 2 at all when running natively on Apple silicon. Check the host's plug-in settings for its scan paths.