Where Does yabridge Put Bridged Plugins on Linux?
yabridge mirrors Windows VST2, VST3, and CLAP plugins into ~/.vst, ~/.vst3, and ~/.clap bridge folders.
Last updated
yabridge does not move your Windows installers. It creates small bridge files your Linux DAW loads. After yabridgectl sync, VST2 bridges appear in ~/.vst/yabridge, VST3 in ~/.vst3/yabridge, and CLAP in ~/.clap/yabridge. Point the DAW at those parent folders.
Real .dll and .vst3 files stay in the Wine prefix, often ~/.wine/drive_c/Program Files. Config files named yabridge.toml sit beside bridges or in parent folders. Binaries live in ~/.local/share/yabridge.
Where yabridge stores this, by platform
~/.vst/yabridge
Bridged VST2 .so files. Managed by yabridgectl, do not add plugins by hand here. Run sync after installing new Windows VST2 plugins.
~/.vst3/yabridge
Bridged VST3 bundles. Add the parent ~/.vst3 to DAW search paths. Config in yabridge.toml beside bridges controls groups and GUI quirks.
~/.clap/yabridge
Bridged CLAP files. Same sync workflow. Runtime files sit in ~/.local/share/yabridge, with Wine prefixes holding the original Windows binaries.
Frequently asked questions
Where do I add plugin folders for yabridge?
Tell yabridgectl where the Windows plugins live with the add command, then run sync. The DAW only scans the bridge folders. Never copy .dll files directly into ~/.vst/yabridge.
Where is the yabridge config file?
Create yabridge.toml next to the bridged plugin or in a parent like ~/.vst/yabridge for global rules. It sets groups, scaling, and host quirks. One file can cover a whole vendor folder.
Notice an outdated path? Let us know.