Yes, Studio One loads third-party audio plugins, and it loads more formats than most hosts. The confusion is which format to pick, the fact that Studio One finds some plugins on its own but has to be pointed at others, and that when a plugin does not appear there is usually no error saying why.
Menu names are Options on Windows and Preferences on Mac. Folder paths are shown for both. Where a step depends on your version of Studio One it is called out.
Yes, and it is one of the broadest hosts here. On Windows Studio One loads VST2 and VST3. On macOS it loads VST2, VST3, and Audio Units (AU), because Audio Units is Apple's own format and does not exist off the Mac. Studio One 7 also added the open CLAP format, so a plugin shipped as a CLAP loads there too.
PreSonus recommends VST3. When a plugin ships both a VST3 and an AU, the VST3 is generally the one to load in Studio One. VST2 still loads, but it is the legacy format, so use it only when a developer offers nothing newer.
For Studio One, reach for the VST3 first. On a Mac the AU works too, so an AU-only plugin is fine there. On Windows there is no AU at all, so a plugin sold as Audio Unit only cannot run in Studio One on a PC.
Most of this assumes Studio One Pro, which hosts third-party VST and AU out of the box. Studio One Artist gained third-party plugin support in later versions, but some older Artist releases needed a paid add-on to host outside plugins at all. If nothing third-party loads in an older Artist install, that is the first thing to check.
An installer normally drops each format in the right place for you. If you are copying one by hand, these are the standard folders, on Mac and on Windows.
| Format | File | Mac folder | Windows folder |
|---|---|---|---|
| Audio Unit (Mac only) | .component |
/Library/Audio/Plug-Ins/Components |
Not available on Windows |
| VST3 | .vst3 |
/Library/Audio/Plug-Ins/VST3 |
C:\Program Files\Common Files\VST3 |
| VST2 (legacy) | .vst / .dll |
/Library/Audio/Plug-Ins/VST |
A folder you choose |
Here is the useful part. Audio Units and VST3 have fixed locations in the operating
system, and Studio One scans those automatically at startup, so you almost never locate
them by hand. VST2 is the one that varies. On Windows especially, a
.dll can land in whatever folder its installer chose, and if that folder is not one
Studio One watches, the plugin simply never appears.
That is what the Locations list is for. Go to Studio One > Options (Windows) or Studio One > Preferences (Mac), open Locations, then the VST Plug-Ins tab. Click Add, choose the folder that holds your VST2 files, and click Apply so Studio One scans it. Keep Scan at startup ticked so new plugins in that folder are picked up on the next launch.
Add the specific folder that contains the plugins, not a giant parent folder above
it. In particular, never add the whole C:\Program Files folder to
the Locations list. Studio One will try to scan everything inside it, and that can crash the
program on launch. Point it at the plugin folder itself.
Studio One scans and validates plugins at startup. A plugin that fails validation, or that lives in a folder Studio One is not watching, is quietly left out with no popup. Work through these in order.
Studio One looks for new and changed plugins when it starts, with Scan at startup enabled. Installing one while Studio One is open often does nothing until you fully quit and relaunch. This alone fixes most cases.
Audio Units and VST3 sit in standard locations Studio One already scans. A VST2 in a custom folder does not, so add that folder under Options or Preferences > Locations > VST Plug-Ins, as above, then relaunch.
If a plugin errors or crashes during the scan, Studio One parks it on a blocklist and hides it, and it stays hidden even after you fix the cause. In the same Locations > VST Plug-Ins panel, click Reset Blocklist, confirm, and restart Studio One so it scans those plugins again. Older versions label this button Reset Blacklist.
If a plugin is installed and off the blocklist but still absent, force a fresh scan. Open the
Plug-in Manager and use its gear icon to Rescan All. If that
does not do it, clear the scan cache: on Windows, quit Studio One and delete the
x64 folder inside
C:\Users\YOURNAME\AppData\Roaming\PreSonus\Studio One 7 (the folder is named for your version, so it may read Studio One 6 or similar), then relaunch and it rebuilds
from scratch. On a Mac the equivalent cache lives in your user Library under Application Support;
the exact folder name varies by version, so confirm it before deleting anything.
Studio One is 64-bit. A 32-bit plugin will not load. On an Apple Silicon Mac, a Universal or Apple Silicon plugin loads natively; to use an Intel-only plugin you run Studio One itself under Rosetta (select Studio One in Finder, press Cmd+I, tick Open using Rosetta). Prefer a native build wherever the developer offers one.
On Windows there is no Audio Units, so an AU will never appear no matter how often you rescan.
Make sure you installed the .vst3 on Windows, and either the .vst3 or
the .component on a Mac.
The blocklist is the reason a plugin that clearly installed still refuses to appear. One bad scan puts it there and it never comes back on its own. If a plugin is in the right folder, is the right format, and is still missing, reset the blocklist and relaunch before you assume the plugin is broken.
Studio One keeps your plugins in the Browser on the right, under the Instruments and Effects tabs, listed by the company that made them rather than by product name. That trips people up: you bought a plugin called Halo and you are scrolling for H, but it is filed under its maker.
To use an effect, drag it from the Effects tab onto a channel in the console or onto an insert slot. To use an instrument, drag it from the Instruments tab onto the arrange area and Studio One makes a new track for it. From there you play or record into it like any track, with full inserts, sends and automation.
Studio One's own instruments and effects are deep, and for most jobs you do not need anything else. The gap people tend to feel is not another EQ or another reverb, it is a starting point: a part that plays itself while you find the idea, instead of an empty track waiting for you to program it.
REHEAT writes acid basslines that move on their own. You set a key and a feel and it generates the line, so there is a part playing before you have programmed a single step. It ships as a VST3 and an Audio Unit, so it drops straight into Studio One, and as an AAX for Pro Tools too. Drag the MIDI it writes straight onto a track in Studio One to keep editing it, or run the REHEAT MIDI DRIVER to play the line live through your own synth. It is signed and notarized, so none of the trouble on this page applies to it.
Play the whole thing free in your browser first, no install and no account.
We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.
Tunary