obsproject/obs-websocket

Remote-control of OBS Studio through WebSocket

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 16th, 2026
Created on October 9th, 2016
Open Issues & Pull Requests: 156 (+0)
GitHub issues: Enabled
Number of forks: 750
Total Stargazers: 4,356 (+0)
Total Subscribers: 104 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.8 days
Mean response time: 89.8 days
90th percentile: 298.4 days
Tracked items: 53

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 68% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 652 days
Stale 30+ days: 61
Stale 90+ days: 55

Recent activity

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

Top labels

  • Issue: Feature Request (39)
  • Issue: Unconfirmed (31)
  • priority/medium (2)
  • Requires OBS Changes (1)
  • hacktoberfest (1)
  • priority/high (1)
  • priority/low (1)

Most active issues this week

Detailed Description

OBS WebSocket is a remote-control plugin that enables programmatic control of OBS Studio through WebSocket connections.

The plugin solves the problem of automating OBS Studio from external applications by exposing a WebSocket interface that accepts commands and returns responses. Rather than requiring direct integration with OBS Studio's codebase, external tools can connect over the network and send commands to control streaming, recording, scene switching, and other broadcast operations. This approach decouples the control logic from the broadcast software itself, allowing any application capable of WebSocket communication to interact with OBS Studio.

The tool suits developers building companion applications, stream overlays, mobile control interfaces, or automation scripts that need to interact with OBS Studio. It is particularly valuable for multi-application broadcast setups where OBS Studio runs on one machine and control logic runs elsewhere. Anyone adopting this plugin should expect to work with WebSocket protocol fundamentals and understand how to structure requests and parse responses from the plugin's command interface.

Development activity shows consistent engagement with the codebase through regular commits addressing bug fixes and feature additions. The project maintains responsiveness to reported issues, with maintainers actively triaging and responding to user-submitted problems. Pull requests receive review and integration when they align with the project's direction. The maintainers demonstrate a commitment to compatibility by ensuring the plugin continues to work across OBS Studio updates and different operating system environments.