Yes, Bitwig Studio loads third-party plugins, in VST2, VST3 and CLAP. The thing that surprises people on a Mac is what is missing: Bitwig does not host Audio Units at all. The other snag is that Bitwig only sees a folder you have told it to scan, and when a plugin does not appear there is no error telling you why.
This covers Bitwig Studio on macOS and Windows. Paths shown are the defaults; the table has both platforms, and Windows notes are called out where they differ.
Bitwig hosts VST2, VST3 and CLAP, and it does so on macOS, Windows and Linux alike. It does not host Audio Units. AU is Apple's own format, and Bitwig has never added it, so on a Mac the format to reach for is VST3, or CLAP if the developer ships one. If a plugin you own comes only as an Audio Unit, it will not appear in Bitwig at all, and there is no setting that changes that.
CLAP is worth a word, because Bitwig helped create it. If a developer ships both a VST3 and a CLAP of the same plugin, either will load, and Bitwig lets you say which one it should prefer. For most people VST3 is the safe default; CLAP is the one to pick when you want the deeper per-note and modulation behaviour Bitwig is known for.
Bitwig runs plugins in a separate process from its own audio engine, which is why a plugin that misbehaves does not usually take the whole project down with it. You can choose how far to push that in the plugin hosting options, from running everything together to giving each plugin its own sandbox. If a plugin does crash, its panel is replaced by a small notice with a reload button, and playback often keeps going. None of this affects which formats load; it just changes how safely they run.
A plugin file is a VST2 (.dll on Windows, .vst on Mac), a VST3
(.vst3), or a CLAP (.clap). An installer usually drops it in the right
place for you. These are the default folders plugins land in, and the ones Bitwig looks in once
you have pointed it there.
| Format | File | Default folder |
|---|---|---|
| VST3 (Mac) | .vst3 |
/Library/Audio/Plug-Ins/VST3 |
| VST2 (Mac) | .vst |
/Library/Audio/Plug-Ins/VST |
| CLAP (Mac) | .clap |
/Library/Audio/Plug-Ins/CLAP |
| VST3 (Windows) | .vst3 |
C:\Program Files\Common Files\VST3 |
| CLAP (Windows) | .clap |
C:\Program Files\Common Files\CLAP |
| VST2 (Windows) | .dll |
No fixed standard; add a custom folder (see below) |
Bitwig does not watch those folders and pick things up on its own. It scans folders you list, which you set in Settings, on the Locations page, under Plug-in Locations. The default system folders above are usually there already; if a plugin installed somewhere else, add that folder to the list. After you change the list, run a rescan so Bitwig re-reads it.
Installing a plugin while Bitwig is open does nothing until Bitwig scans again. Open Settings > Locations and use the Rescan control for the format, or in the browser open the File Browser tab, expand the library locations, right-click the format and choose to re-index it. Restarting Bitwig triggers a scan too. The exact wording of these controls shifts a little between versions, so if a label does not match, look for the rescan or reindex action near the plugin folders rather than trusting a screenshot from an older release.
Bitwig scans plugins and quietly leaves out anything it cannot load, with no message. Work through these in order.
Bitwig picks up new plugins on a scan, not the moment they land on disk. Open the Locations settings and run the Rescan for that format, or re-index the folder from the File Browser. Fully quitting and reopening Bitwig does the same thing. This alone fixes most cases.
Bitwig only scans folders that are listed under Settings > Locations > Plug-in Locations. If your installer put the plugin somewhere off the beaten path, or you copied it in by hand, add that exact folder to the list and rescan.
Bitwig hosts VST2, VST3 and CLAP, and does not host Audio Units. If the only build you
installed is the AU (a .component file), it will never show up. Install the
VST3 or CLAP version instead. On Windows there is no Audio Units in the first
place, so this only bites on a Mac.
Bitwig runs natively on Apple Silicon. A plugin has to be built for the way Bitwig is running, so an Intel-only plugin may not load in a native Apple Silicon session. Select the plugin file in Finder, press Cmd+I, and under General it should read Universal or Apple Silicon, not Intel only.
On macOS, an unsigned or unnotarized plugin can be blocked by Gatekeeper before Bitwig ever sees it. If you got a security warning during install, that is the cause. Anything from a real developer will be signed and notarized and will install with no warning.
Open the Browser, either the pop-up browser you get when you add a device or the browser panel at the side. Your installed plugins sit alongside Bitwig's own devices, and you can filter the browser to VST or CLAP to narrow it down. Drop one onto a track's device chain, or drag it in from the browser.
An instrument goes on a track and turns notes into sound; an audio effect processes whatever runs through the chain it sits in. Because Bitwig is a full DAW, you can chain devices freely, send several tracks to one effect, and map Bitwig's own modulators onto a plugin's own knobs, which is a large part of why people reach for it.
Bitwig's stock devices are deep, and its modulation system does things most hosts cannot, so most people do not need a whole bundle on top. The honest answer is that you want one or two things Bitwig does not do out of the box, rather than a shelf of plugins. One that comes up: a bed that keeps moving on its own, made out of your own playing, so you have something alive to write against instead of a static pad.
SILT is a tape loop that will not sit still. Play a chord or drop a sample in, and it wears the loop out for you, with wow, flutter, dust and dropout, until a plain held note turns into an evolving bed you can write over. It ships as an Audio Unit, a VST3, an AAX and a standalone. Since Bitwig does not host Audio Units, here you load the VST3, which is the whole point of this page.
Universal, signed and notarized, so none of the trouble above applies to it. Hear 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