streamlabs/desktop

Free and open source streaming software built on OBS and Electron.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 14th, 2026
Created on October 26th, 2017
Open Issues & Pull Requests: 45 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 688
Total Stargazers: 4,851 (+0)
Total Subscribers: 122 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Streamlabs Desktop is a free and open source streaming application built on OBS and Electron.

The tool addresses the need for accessible live streaming software by combining OBS's proven streaming engine with a modern desktop application interface. It runs on Electron and uses a multi-window architecture where a persistent worker window handles services, a main window provides the user interface, and child windows manage modal interactions like source properties. This design allows the application to communicate across windows via interprocess communication rather than blocking operations, keeping the interface responsive during streaming tasks.

Streamlabs Desktop targets content creators who want streaming software without licensing costs and developers who want to contribute to or fork streaming infrastructure. The project supports macOS and 64-bit Windows. It integrates with major streaming platforms including Twitch, YouTube, and Facebook. The codebase is written primarily in TypeScript and uses Vue for UI components, making it accessible to developers familiar with modern JavaScript tooling. Development requires Node.js, Yarn, Bash, and native C++ modules that are installed as prebuilt binaries.

The project maintains active development with regular commits across its core systems. Work spans the full application stack including the Electron framework integration, the Vue-based user interface, native module bindings, and the services layer that coordinates streaming operations. The team addresses both feature development and infrastructure concerns, with ongoing attention to the multi-window IPC architecture that underpins the application's responsiveness.