WHIP & SRT Ingest
Publish over WHIP or SRT from the bundled ppobs client or your own encoder. Both protocols expose the same simulcast and multitrack capabilities, so you are not locked into a single transport.
WHIP: the WebRTC-native ingest
WHIP is the standard WebRTC ingest. It pairs naturally with WHEP playback for a fully standard, low-latency pipeline with per-stream token authentication.
SRT: keep your existing pipeline
SRT is ideal if you already push over SRT. It runs as an independent connection with its own RTP state, auth token and simulcast layers, and supports the same H264/HEVC multitrack output.
Zero-code with ppobs
Fill in your appId/appSecret and a stream name in ppobs and click Start — capture, mixing, scene switching and multi-track publishing are handled for you.
FAQ
Can I publish HEVC over SRT?
Yes — SRT supports H264/HEVC multitrack, same as WHIP.
Do I have to migrate off RTMP?
PPCDN uses WHIP/SRT for ingest and WHEP for playback by design; RTMP/HLS are intentionally not offered because sharded protocols cannot meet interactive latency.
Is there a reference client?
Yes — ppobs, a patched OBS build with PPCDN presets, is available for download.
Sign up and get $10 in trial credit
Create an app to get your appId, then start publishing with ppobs.