How it works
A DNS trick, a local RTMP server, and OBS
The PS5 can broadcast, but only to a few services, and only the way it wants. Console Cast changes where that broadcast goes, without touching the PS5 or the stream itself.
1. The DNS part
When you press Broadcast, the PS5 looks up Twitch's ingest servers by name and sends plain RTMP to whatever address comes back. Console Cast runs a small DNS server on your Mac, and you point the PS5's Primary DNS at it.
That DNS server does exactly one unusual thing: it answers Twitch's ingest hostnames with your Mac's LAN IP. Every other lookup, from game servers to the PlayStation Store, is forwarded to your router unchanged, so the PS5 stays fully online.
| Hostname | Console Cast answers |
|---|---|
*.contribute.live-video.net | Your Mac's IP |
*.global-contribute.live-video.net | Your Mac's IP |
live.twitch.tv, live-*.twitch.tv | Your Mac's IP |
ingest.twitch.tv | Forwarded to your router. It's HTTPS discovery and must reach the real Twitch. |
| Everything else | Forwarded to your router |
On a real PS5, the sequence looks like this: it looks up ingest.twitch.tv (passed through), then ingest.global-contribute.live-video.net (redirected to the Mac), and starts publishing about three seconds after you press Broadcast.
The PS5's Secondary DNS must be 0.0.0.0. If it's set to anything real, the PS5 can quietly ask that server instead and stream to the real Twitch.
2. The video path
The PS5 now connects to port 1935 on your Mac. Console Cast runs MediaMTX, an open-source media server, to receive it. The PS5 publishes to app/live_<your stream key>, which changes per account, so Console Cast relays it to a fixed path:
rtmp://127.0.0.1:1935/ps5That relay is a straight copy. The PS5 sends 1080p60 H.264 (Main profile) with AAC-LC 48 kHz stereo audio at about 6 Mbps, and those exact packets are what OBS receives. Nothing is decoded or re-encoded until OBS does its own encode for your stream.
OBS reads the relay as a Media Source. Console Cast can add that source for you over obs-websocket: it reads the port and password from OBS's own config, creates PS5 (Console Cast) in your current scene, and scales it to fit the canvas.
Browser preview
For checking the feed without OBS, MediaMTX also serves two players, reachable only from the Mac itself:
- WebRTC at
http://127.0.0.1:8889/ps5: the lowest latency. Video only, because browsers can't play the PS5's AAC audio over WebRTC. - Low-latency HLS at
http://127.0.0.1:8888/ps5: video and audio, with about half a second of delay. It starts muted.
3. Modes
Console Cast has three states, and the difference matters because your PS5 depends on it for DNS.
| Mode | What happens |
|---|---|
| Armed | Twitch ingest lookups go to your Mac, and the PS5 broadcast arrives in OBS. This is how Console Cast starts. |
| Pass-through | DNS keeps working normally. The PS5 stays online and broadcasts straight to the real Twitch. |
| Not running | The PS5 has no DNS, so it has no internet, because its Secondary DNS is 0.0.0.0. Start Console Cast again, or set the PS5's DNS back to Automatic. |
4. Privacy
- No account, no sign-in, no telemetry, and no cloud service.
- The video travels from the PS5 to your Mac over your own network.
- The control API (
http://127.0.0.1:7777) and the preview players listen only on the Mac itself. - Your Twitch stream key is part of the path the PS5 publishes to. Console Cast masks it in its status output.
5. Latency
Because Console Cast copies packets instead of decoding them, it adds almost no delay of its own. Most of the delay you'll see comes from the PS5's encoder, which buffers 1–3 seconds before anything leaves the console.
WebRTC preview
1080p60 test feed, same Mac
LL-HLS preview
1080p60 test feed, same Mac
PS5 encoder
Before it reaches the Mac
Preview numbers were measured with a 1080p60 test pattern published on the same Mac.
Ready to try it? The setup guide takes about ten minutes, most of it in the PS5's network menu.