robbert-vdh/yabridge

A modern and transparent way to use Windows VST2, VST3 and CLAP plugins on Linux

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on February 3rd, 2020
Open Issues & Pull Requests: 137 (+0)
GitHub issues: Enabled
Number of forks: 126
Total Stargazers: 4,105 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 days
Mean response time: 32.3 days
90th percentile: 48.5 days
Tracked items: 144

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 41% of tracked open issues have had no activity in three months. Only 24% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 98
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 483 days
Stale 30+ days: 81
Stale 90+ days: 62

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • configuration-issue (3)
  • fixed-in-master (3)
  • enhancement (2)
  • wine-issue (2)
  • bug (1)
  • documentation (1)
  • help wanted (1)
  • invalid (1)

Detailed Description

yabridge is a plugin bridge that enables Windows VST2, VST3, and CLAP plugins to run on Linux.

The tool solves the problem of plugin availability on Linux by bridging the gap between Windows plugin binaries and Linux audio applications. Rather than requiring plugins to be natively compiled for Linux or asking users to run entire DAWs under compatibility layers, yabridge uses a transparent approach where a Linux-side plugin wrapper communicates with a Windows plugin instance running under Wine. This architecture allows existing Windows plugins to function within Linux audio hosts without modification, presenting them as native Linux plugins to the host application.

Developers and musicians working on Linux who rely on Windows-only plugins should consider yabridge if they need access to a specific plugin ecosystem without waiting for native ports. The tool suits projects where plugin availability is a blocker for Linux adoption. It works best in environments where Wine is already functional and where the overhead of inter-process communication is acceptable for the audio workload.

The project shows sustained development with regular updates addressing compatibility issues and adding support for new plugin standards. Maintenance activity indicates ongoing attention to bug reports and feature requests from users encountering real-world plugin scenarios. The codebase receives refinements to improve stability and performance of the bridging mechanism. Development demonstrates responsiveness to the needs of the Linux audio community, with updates reflecting both emerging plugin technologies and practical issues encountered by active users.