Video Streaming Bandwidth Requirements: How Much Do You Need?

“How much bandwidth do I need?” sounds like one question, but it hides three: how fast must a viewer’s connection be to watch smoothly, how fast must your upload be to stream live, and how much capacity must a server or CDN deliver when hundreds or thousands of people watch at once. This guide answers all three with real numbers, simple formulas and worked examples.

If you want to skip to the answer for your own situation, our streaming bandwidth calculator does the maths for any bitrate, audience and duration.

The key number: bitrate

Everything starts with the stream’s bitrate, the amount of data per second, measured in megabits per second (Mbps). A 1080p stream might be 5 Mbps. A 4K stream might be 20 Mbps. Bitrate depends on resolution, frame rate, codec and how complex the picture is. For the full background, see what is video bitrate.

Once you know the bitrate, bandwidth and data use follow from simple multiplication.

Part 1: bandwidth to watch video

Typical bitrates by quality

The recommended connection is higher than the bitrate on purpose. Real connections fluctuate, other devices share the line, and players need headroom to fill their buffers. A rule of thumb: your connection should be at least 1.5 to 2 times the stream bitrate.

Streaming services publish their own minimums. For example, many recommend around 5 Mbps for HD and 15 to 25 Mbps for 4K. Because they use efficient codecs and adaptive bitrate streaming, your player automatically picks a lower quality when bandwidth is short.

Households with several viewers

Add the streams together. Two people watching 4K and one watching 1080p need roughly 20 + 20 + 5 = 45 Mbps of real throughput, plus room for everything else. A 100 Mbps connection handles that comfortably. A 30 Mbps connection will force at least one stream to drop quality.

Wi-Fi vs actual internet speed

Your internet plan is only part of the story. Weak Wi-Fi, a busy 2.4 GHz band or an old router can deliver far less than your plan’s speed to a TV in another room. If streaming struggles despite a fast plan, test speed on the device itself, move closer to the router, use 5 GHz or 6 GHz Wi-Fi, or connect by Ethernet.

Data use per hour

To convert bitrate to data per hour: GB per hour = Mbps × 0.45.

That explains why a mobile data plan disappears quickly with HD video, and why many apps default to lower quality on cellular connections.

Part 2: upload speed to stream live

If you broadcast live, your upload speed matters, not your download speed. Home connections are often asymmetric: 500 Mbps down but only 20 Mbps up.

When you stream to a platform that transcodes for you, such as YouTube, Twitch, Facebook, Vimeo or most online video platforms, you upload one stream. The platform makes the other qualities and delivers them to viewers. So your upload needs are:

Upload needed ≈ stream bitrate × 1.5

If you send several streams yourself, for example multistreaming to three platforms at once from OBS, multiply accordingly, or use a restreaming service that takes one upload and forwards it. If your encoder produces its own adaptive ladder, add up all the renditions.

For details on testing and stabilising your upload, see how much upload speed you need for live streaming.

Part 3: server and CDN bandwidth for your audience

This is where numbers get big. Every viewer receives their own copy of the stream, so delivery bandwidth scales with the audience.

Peak delivery bandwidth = bitrate × concurrent viewers × (1 + overhead)

Overhead covers container and protocol overhead, manifests and retransmissions, typically 5 to 10 percent.

Total data delivered = bitrate × viewers × duration (seconds) ÷ 8, plus overhead.

Worked example: a webinar

• 1080p30 at 5 Mbps
• 800 concurrent viewers
• 90 minutes
• 8 percent overhead

Peak bandwidth: 5 × 800 × 1.08 = 4,320 Mbps, or about 4.3 Gbps. Data per viewer: 5 × 1.08 × 5,400 ÷ 8 = 3,645 MB, or about 3.6 GB. Total data: about 2.9 TB.

No home or office connection can deliver 4.3 Gbps, which is why live streams to more than a handful of people go through a platform or a CDN. CDNs have servers close to viewers and capacity measured in terabits.

Worked example: an on-demand course library

• 2,000 students watching an average of 3 hours per month
• Average delivered bitrate 3 Mbps, because many watch at 720p on laptops and phones

Data per month: 3 × 3 × 3,600 × 2,000 ÷ 8 = 8,100,000 MB, or about 8.1 TB.

At a CDN price of $0.01 to $0.05 per GB, that is roughly $80 to $400 per month in delivery. Knowing this helps you choose a hosting plan. Our video hosting guide for online courses compares options.

Why real-world numbers are usually lower

The formulas give a ceiling. In practice, delivered bandwidth is often 10 to 30 percent lower because:

• Adaptive bitrate means many viewers watch lower renditions, especially on phones.
• Not everyone watches the whole time. People join late and leave early.
• Efficient codecs such as HEVC and AV1 reduce bitrates on supported devices. See H.264 vs H.265 vs AV1.
• Small players often do not need top quality; some players cap resolution to the player size.

Use the ceiling for capacity planning and contracts, and your analytics for budgeting after the first few events.

How to reduce bandwidth without hurting viewers

• Use a good bitrate ladder. Do not make 1080p the only option. A 720p rendition at 3 Mbps saves 40 percent for viewers who cannot tell the difference. See best encoding settings for streaming.
• Encode more efficiently. Use slower presets, capped CRF or per-title encoding.
• Add HEVC or AV1 renditions for devices that support them.
• Cap resolution to player size. A 400-pixel-wide embedded player does not need 1080p.
• Lower the frame rate for talking-head content.
• Cache well. Make sure your CDN caches segments with long lifetimes for VOD.

Quick reference

• Watching: connection ≥ 1.5–2 × stream bitrate.
• Live upload: ≥ 1.5 × total bitrate you send.
• Delivery peak: bitrate × concurrent viewers × ~1.08.
• Data: Mbps × 0.45 = GB per hour, per viewer.

Bandwidth for video calls vs streaming

People often compare streaming requirements with video calls, but the numbers differ. Video calls on Zoom, Teams and Google Meet adapt aggressively and use relatively low bitrates, because the picture is usually a face on a plain background:

Unlike streaming, calls need symmetric bandwidth and low latency. A connection that streams 4K perfectly can still struggle with calls if its upload is weak or its latency jumps around.

How to check what you are actually getting

Speed tests measure a moment. To see what streaming really uses:

• Open the “stats for nerds” overlay in YouTube (right-click the player) to see connection speed, buffer health and current resolution.
• In our HLS player, lock each quality level and watch whether playback keeps up.
• On your router, many models show per-device bandwidth in real time.
• For live events you run, the platform’s analytics show average bitrate delivered and rebuffering ratios by region, which tell you whether viewers’ connections are coping with your ladder.

Summary

Streaming bandwidth comes down to the stream’s bitrate multiplied by viewers and time. Viewers need about twice the bitrate in download speed, broadcasters need about 1.5 times in upload, and delivery networks need the bitrate multiplied by the audience. For anything beyond a small audience, use a platform or CDN, design a sensible bitrate ladder, and plan capacity with the bandwidth calculator.