Discovery & signaling
Receivers advertise over mDNS on the LAN (signaling port 50125). Senders can also connect by IP when multicast is blocked. A pairing code gates who may connect.
Castzo is its own sender, its own receiver, and your LAN. Every session uses the same fully self-developed, high-performance protocol.
Receivers advertise over mDNS on the LAN (signaling port 50125). Senders can also connect by IP when multicast is blocked. A pairing code gates who may connect.
Windows uses DXGI / Graphics Capture, macOS uses ScreenCaptureKit, Android uses MediaProjection, and iOS uses the built-in screen-sharing flow. H.264 is preferred, with H.265 and VP8 fallbacks. Hardware encoders and adaptive bitrate keep latency low.
The receiver renders the remote stream full-screen and normalizes pointer coordinates to the visible video area, rejecting black bars. Window and display geometry are re-read for DPI and multi-monitor changes.
Media (images, video, audio) travels over a local HTTP server plus DLNA playback. Arbitrary files use a dedicated /prismcast/push endpoint. Each sender's content is tracked by source IP, so one sender cannot clear another's.
Streaming stays on your LAN. Pairing codes gate connections, only paired or connected receivers can request control, and the sender can revoke control at any time. Your media never needs to leave the local network.
The sender discovers a receiver, opens a direct session, and reconnects if the link drops. There is no protocol handoff; the same Castzo transport is used throughout.
Discovery: mDNS · signaling port 50125
Encoding preference: H.264 → H.265 → VP8
Media channel: local HTTP server + DLNA playback
File channel: /prismcast/push
Quality range: up to 1440p / 120 fps; options are shown only when supported
Every layer is tuned for Castzo, from capture to render.
Download the sender and receiver, put them on the same LAN, and start casting.