Control OBSControl OBS

Remote Access

By default, Control OBS connects directly to OBS on your local network. If you want to control OBS from a different location, such as from your phone on mobile data or from another building, you need to make the WebSocket server reachable from the internet. There are three ways to do this.

Your options

Option A - Port forwarding

Port forwarding tells your router to send incoming traffic on a specific port to a specific device on your local network.

1

Give your computer a static local IP

By default, your computer's local IP can change each time it reconnects. Set a static IP (or a DHCP reservation on your router) so the forwarding rule stays valid. Your router's admin panel is usually reachable at 192.168.1.1 or 192.168.0.1.

2

Create a port forwarding rule

In your router's admin panel, find the port forwarding section (sometimes called Virtual Servers or NAT). Create a rule to forward external TCP port 4455 to internal port 4455on your computer's local IP address.

3

Find your public IP address

Search for “what is my IP” in a browser on any device at home. This is the address you will enter in Control OBS when connecting remotely.

4

Add the device in Control OBS

In the app, tap Add Device and enter your public IP address (not your local 192.168.x.xaddress), port 4455, and your WebSocket password.

Most residential broadband connections have a dynamic public IP, meaning it can change periodically. If the connection stops working after a few days, check whether your public IP has changed. A dynamic DNS (DDNS) service can give you a stable hostname that tracks your IP automatically.

Security notice. Port forwarding exposes your OBS WebSocket server to the internet. Always enable authentication and use a strong password. Anyone who knows your IP and port can attempt to connect.

Option B - AntiScuff hosted OBS

AntiScuff provides cloud-hosted OBS instances that are always online and always reachable from Control OBS, with no port forwarding required. Your OBS runs on our servers near major streaming ingest points, which can improve stream reliability and reduce latency to platforms like Twitch and YouTube.

When you set up an AntiScuff server, you will receive a WebSocket connection URL that you can paste directly into Control OBS as a remote device.

Visit antiscuff.com to learn more about hosted OBS and pricing. Existing AntiScuff customers can find their WebSocket URL in the dashboard.

Option C - Bridge relay

The bridge relay lets you control OBS from anywhere without opening any ports on your router or running any additional software. It works by adding a browser source to OBS that makes an outbound connection to a relay server. The app then connects to the same relay using a short Bridge ID.

1

Open the bridge setup page

On your OBS PC, visit proxy.controlobs.com/bridge in a regular browser tab. Enter your OBS WebSocket host, port, and password, then click Generate Bridge ID.

2

Add the browser source to OBS

Copy the ready-made browser source URL shown on the setup page and add it as a Browser Source in OBS Studio. The source connects to the relay automatically whenever OBS is running. You can place it on any scene, or add it to all scenes using a scene collection.

3

Enter the Bridge ID in the app

In Control OBS, tap Add Device and choose Bridge. Enter your Bridge ID and tap Connect. The app will connect through the relay as long as OBS is running with the browser source active.

Your Bridge ID is a private UUID. Keep it to yourself - anyone with the ID can connect to your OBS instance. You can generate a new ID at any time from the setup page, which invalidates the old one.

← TroubleshootingAll guides →