How does a streaming platform deliver 4K HDR video to 230M+ subscribers globally without buffering, adapting quality in real-time to each viewer's bandwidth while minimizing rebuffer events to <0.1% of sessions?
Core challenge: A user's bandwidth fluctuates constantly (WiFi ? cellular ? tunnel). The player must predict bandwidth, pre-buffer segments, and switch quality seamlessly · all without visible artifacts or interruption.
230M+
subscribers
190+ countries
<0.1%
rebuffer rate
target per session
15%+
of global internet traffic
peak hours
8+
quality levels
240p ? 4K HDR
High-Level Architecture
Content preparation ? CDN distribution ? adaptive client playback
Adaptive Bitrate (ABR) Algorithm
The client-side brain that decides quality for each segment
Signal
What It Measures
How It's Used
Throughput
Download speed of last N segments (EWMA)
Upper bound on selectable bitrate
Buffer Level
Seconds of video buffered ahead
Low buffer ? drop quality aggressively
VMAF Score
Perceptual quality metric per encode
Choose encode with best quality/bitrate ratio
Device
Screen resolution, HDR capability
Don't send 4K to a phone on cellular
Network type
WiFi vs cellular vs ethernet
More conservative on cellular (data caps)
Netflix's approach:Buffer-based + throughput-based hybrid. Start conservative (low quality, fast start). Ramp up as buffer fills. Drop immediately if buffer drains below threshold. Per-shot encoding means a dark scene at 2Mbps looks as good as a bright scene at 8Mbps · ABR picks the optimal encode per scene.
Key metrics:Time to first frame <2s. Rebuffer rate <0.1%. Quality switches minimized (hysteresis). Start bitrate based on historical bandwidth for that user/device/ISP.
Anti-patterns:Throughput-only ABR · oscillates wildly. Fixed quality · buffers on slow networks. No hysteresis · constant quality switching is jarring. Same encode ladder for all content · wastes bits on simple scenes.
Scaling & Key Decisions
Challenge
Netflix Solution
Why
Global delivery
Open Connect (own CDN in ISPs)
Lower latency than third-party CDN, no transit costs
Real-world:Netflix serves 15%+ of global internet traffic at peak. Open Connect has 17,000+ servers. Per-shot encoding saved 20% bandwidth. AV1 codec rolling out for 30% more compression. Each title encoded into ~1200 versions (resolution · bitrate · codec · HDR).
Interview Cheat Sheet
The 8 things to say for video streaming design
1.Adaptive Bitrate (ABR) · client measures bandwidth, requests appropriate quality segment 2.HLS/DASH manifest · playlist of segment URLs at multiple quality levels, client picks 3.CDN (Open Connect) · 17K+ edge servers, content pre-positioned during off-peak 4.Per-title encoding · each title gets custom bitrate ladder (animation needs less than action) 5.Buffer-based algorithm · switch quality based on buffer level, not just bandwidth estimate 6.Rebuffer rate <0.1% · the key quality metric (users leave after 2s of buffering) 7.Pre-positioning popular content · push to edge during off-peak, serve locally at peak 8.Multi-codec strategy · H.264 (compatibility) ? H.265 (4K) ? AV1 (next-gen, 30% savings)