Skip to main content
Page is under construction.

Check the github issues for ways to contribute! Or provide your feedback in this quick form
If you’re new to live video, this page covers the core concepts you need before writing any code. If you already know RTMP, HLS, and how transcoding pipelines work, skip to the Video Streaming Quickstart.

​
Start here in 5 minutes

  • Prereqs: Basic familiarity with web APIs and one broadcaster tool (OBS or browser encoder)
  • Time: 5 minutes
  • Outcome: You understand stream key/playback ID, ingest, and playback flow well enough to start the quickstart
  • First action: Read Stream Key vs. Playback ID, then continue to Video Streaming Quickstart

​
How Live Video Works

A live stream travels through four stages:
  1. Ingest — Your broadcaster sends a raw video signal to a server
  2. Transcoding — The server converts it into multiple quality levels for different devices and connection speeds
  3. Delivery — Processed video is made available via a CDN or playback server
  4. Playback — Viewers watch the stream in their browser or app
Livepeer’s decentralized network handles steps 2 and 3 — transcoding and delivery — using a distributed network of GPU operators called orchestrators.

​
Core Concepts

​
Stream Key vs. Playback ID

These are the two most important identifiers in a live streaming workflow:
Stream KeyPlayback ID
What it isSecret credential for publishing videoPublic identifier for watching video
Who uses itBroadcaster (OBS, encoder, streaming app)Viewers (embedded player, your app)
SecurityKeep secret — anyone with it can publish to your streamPublic — safe to expose to end users
How to get itFrom your gateway/Studio when you create a streamFrom your gateway/Studio alongside the stream key
Think of the stream key as a password and the playback ID as a public URL slug.

​
RTMP (Real-Time Messaging Protocol)

RTMP is the standard protocol for sending video from a broadcaster to an ingest server. OBS, hardware encoders, and most professional streaming tools support RTMP. 
rtmp://rtmp.livepeer.com/live/{streamKey}
When you push video to this endpoint with your stream key, Livepeer ingests it, transcodes it, and makes it available for playback.

​
HLS (HTTP Live Streaming)

HLS is the standard delivery format for live and on-demand video. It splits video into small segments and serves them over HTTP. Most players (browsers, mobile, smart TVs) support HLS natively. 
https://livepeercdn.studio/hls/{playbackId}/index.m3u8
As of 02-March-2026, livepeercdn.studio is the documented Studio HLS playback host. HLS introduces latency (typically 5-30 seconds) because viewers are buffering ahead. This is acceptable for most streaming use cases.

​
WebRTC / WHIP

WebRTC is a browser standard for real-time audio and video communication. Livepeer supports WebRTC ingest via WHIP (WebRTC-HTTP Ingest Protocol), enabling sub-second latency streaming directly from a browser without OBS. 
https://playback.livepeer.studio/webrtc/{streamKey}
WebRTC is also used for low-latency playback — where viewers receive the stream with under 2 seconds of delay instead of the typical HLS buffer.

​
Latency Modes

ModeLatencyProtocolBest For
Standard HLS10-30 secondsHLS/MPEG-TSBroadcast streaming, VOD-like quality
Low-Latency HLS (LL-HLS)2-5 secondsLL-HLSSports, events, interactive streams
WebRTC PlaybackUnder 500msWebRTC/WHEPInteractive, conversational, real-time AI video
For most applications, standard or low-latency HLS is the right choice. WebRTC playback is used when viewer interaction or real-time AI processing requires near-zero delay.

​
Transcoding and Quality Ladders

Transcoding converts an incoming high-quality stream into multiple renditions at different resolutions and bitrates — a quality ladder. The viewer’s player automatically selects the best rendition for their connection speed (called adaptive bitrate streaming). Example quality ladder:
RenditionResolutionBitrate
1080p1920×10804000 kbps
720p1280×7202000 kbps
480p854×4801000 kbps
360p640×360500 kbps
Livepeer’s orchestrators perform this transcoding work in real time for every active stream.

​
How Livepeer Differs from Traditional Streaming

Traditional (AWS MediaLive, Mux)Livepeer
TranscodingCentralized cloud serversDistributed GPU network
PricingPer-minute, billed by providerCompetitive market pricing
ControlProvider manages everythingGateway operators control routing
Censorship resistanceProvider can terminate streamsDecentralized — no single point of control
AI videoSeparate AI infrastructure requiredAI inference native to the same network

​
Key Terms Reference

TermMeaning
StreamA live video broadcast session
Stream KeySecret credential for publishing to a stream
Playback IDPublic identifier for watching a stream or asset
IngestReceiving raw video from a broadcaster
TranscodeConverting video into multiple formats/quality levels
SegmentA short chunk of video (typically 2-6 seconds) transcoded independently
GatewayLivepeer network entry point that routes jobs to orchestrators
OrchestratorGPU operator that performs transcoding and AI inference
RTMPProtocol used by OBS and encoders to send video to an ingest server
HLSHTTP-based playback format for live and on-demand video
LL-HLSLow-latency variant of HLS (2-5 second delay)
WebRTCBrowser real-time communication protocol (sub-500ms latency)
WHIPWebRTC ingest protocol — push video from browser to Livepeer
ABRAdaptive Bitrate — automatic quality selection based on viewer connection

​
Ready to Build?

Video Streaming Quickstart

Create your first stream and play it back in minutes.

Livepeer Studio

Hosted gateway for live streaming and VOD — start with the dashboard.

OBS Setup Guide

Configure OBS to stream to Livepeer.

Livepeer Player

Embed the Livepeer React Player in your app.
Last modified on March 2, 2026