How to Control OBS Remotely with WebSocket
OBS's built-in WebSocket feature lets a compatible tool control actions such as switching scenes or muting a source. This can be useful when you want a phone or control panel within reach of your camera position.
OBS 28 and later include WebSocket support. You normally do not need a separate obs-websocket plugin for these versions.
Enable the OBS connection
- 1.Open Tools → WebSocket Server Settings or obs-websocket Settings, depending on the version's label.
- 2.Enable the WebSocket server.
- 3.Keep authentication enabled.
- 4.Review or set the connection password.
- 5.Apply the changes.
Treat the password as a control credential. Someone with the required access could change scenes or operate outputs, not merely watch a preview.
Connect a compatible client
Use a client whose developer documents support for your OBS WebSocket version. Follow that client's connection instructions for the computer address, server port, and password.
A client on the same computer and a phone on your local network use different network addressing. Copy the connection information deliberately rather than guessing an internet address.
For a local controller, keep the connection on your trusted network. Do not open a router port to the public internet simply because the client cannot connect.
Start with a small control panel
Add only the actions you need, such as a main-scene button and microphone mute control. Label them clearly.
Test while off air and confirm the result in OBS. Avoid placing a start-stream button where it is easy to tap accidentally. A remote control should make the session easier, not leave you unsure whether an output is running.
If the client will not connect
Confirm the server is enabled, the credentials match, and the devices can reach each other. Check relevant local firewall permissions without disabling protection broadly.
If OBS is running in safe mode, WebSocket functionality is disabled. Return to a normal launch when that troubleshooting session is finished.
Test connection loss
Disconnect and reconnect the client during an offline test. Check what its buttons show afterward and whether they reflect the real OBS state.
Keep access to OBS's own controls as a fallback. Remote-control compatibility does not establish that any particular streaming platform supports the OBS output method you chose.