Guide · Remote access
Control OBS from outside your network
- The easiest way: remote access (Pro)
- Why not just port-forward
- The safe path: a mesh VPN
- Tailscale step by step
- The risky option, honestly
- Good to know
OBS Blade normally talks to OBS over your local network - that's what the phone setup guide walks through. But sometimes you want more: start the recording from the garden, check the stream from the office, help a friend fix their scenes from your couch. This guide is about doing that without opening a security hole.
The easiest way: remote access in OBS Blade Pro
With OBS Blade Pro, install OBS Blade Remote on the PC running OBS and set it up once in the app - tap the globe on the dashboard while you're on your Wi-Fi. From then on OBS Blade reaches that OBS from anywhere through our relay: end-to-end encrypted, so the relay can't read your sessions, nothing to open on your router, and no VPN app on your phone. Your OBS password stays on the PC.
The rest of this guide is the free way that needs nothing from us: a mesh VPN you run yourself.
Why not just port-forward the WebSocket?
The obvious idea is to forward port 4455 on your router to the streaming PC and connect to your home IP from anywhere. Please don't - and it's worth understanding why:
- obs-websocket has no TLS. Traffic between the app and OBS - including the authentication handshake - is not encrypted. On the open internet, anyone in a position to watch the traffic can watch yours.
- A password is the only barrier. Once the port is public, every scanner on the internet will find it within days. The only thing between them and full control of your OBS is one password, and they can try as many as they like - there's no lockout.
- It's remote control of your PC's production tool. Whoever gets in can switch scenes, stop streams and fire any hotkey OBS exposes.
The short version: obs-websocket was designed for a trusted LAN. Treat a public port-forward of it like posting your OBS remote on the open internet - because that's what it is.
The safe path: a mesh VPN
A mesh VPN puts your phone and your PC on the same encrypted, private network no matter where they physically are. Once both are in, connecting OBS Blade works exactly like it does at home - same app, same port, same password - except the traffic is encrypted end to end and invisible to the public internet. Nothing on your router changes, and no port is ever exposed.
The two well-known options are Tailscale and a self-hosted WireGuard setup. WireGuard is excellent but means running your own server; Tailscale is built on WireGuard, is free for personal use, and takes minutes because it handles the key exchange and NAT traversal for you. If you already run WireGuard, use that - the OBS Blade side is identical either way. The steps below use Tailscale because it's the easiest path for most people.
Tailscale step by step
- Install Tailscale on the streaming PC.
Download it from
tailscale.comfor Windows or macOS, install and sign in (it uses your existing Google, Microsoft, Apple or GitHub account - no new password to invent). Your PC now has a stable Tailscale IP in the100.x.y.zrange, visible in the Tailscale menu or admin console. - Install Tailscale on your phone or tablet.
Get the Tailscale app from the App Store or Google Play and sign in to the same account. Both devices are now on your "tailnet" - your private mesh.
- Connect OBS Blade to the Tailscale IP.
In OBS Blade, add a manual connection: the PC's Tailscale IP, port
4455, and the same WebSocket password you use at home. With the Tailscale app running on the phone, it connects from anywhere - mobile data included.
Keep the password anyway. Defence in depth: the VPN keeps strangers out, the password keeps anyone already on your tailnet honest. Leave OBS's WebSocket password set even though the port is no longer public.
The risky option, honestly
If you absolutely cannot run a VPN - some managed or older devices make it hard - port-forwarding is the fallback people reach for. If you go that way, at minimum: use a long, random, unique password in OBS's WebSocket settings; forward a non-standard external port to 4455; and restrict the forward to source IPs you actually use if your router supports it. Understand that this reduces, not removes, the risk - the traffic is still unencrypted and the port is still public. It's the option we'd talk a friend out of.
Good to know
- Relay or VPN - both keep your sessions private. OBS Blade's own remote access (Pro) is end-to-end encrypted, so the relay only passes data it can't read. A mesh VPN is free and doesn't involve our servers at all. Either way there's no OBS Blade account.
- Live preview uses bandwidth. The scene preview is a stream of images; over mobile data it adds up. The dashboard works fine without watching it constantly.
- Everything else is unchanged. Scenes, mixer, stats, chat - the app behaves exactly as it does on your LAN, just a few milliseconds later.
