Bitrate and upload speed are not the same number
Your encoder or streaming software sends video at a set bitrate: the number of megabits per second it pushes out. Upload speed is how much your internet connection can carry outward. A stream stays smooth only if the connection carries the bitrate continuously, with room left over for the moments when the network wobbles.
That spare room is headroom, and a common rule is to have at least 1.5–2 times the stream's bitrate available as steady upload. The word steady matters. A speed test captures a short burst; a stream needs the same rate minute after minute for hours. If upload dips below the bitrate even briefly, the encoder buffers, drops quality or disconnects, and viewers notice before you do.
How much upload for a live stream: the arithmetic
Multiply the bitrate by 1.5 for a minimum and by 2 for comfort. The bitrates below are examples only; use the figure your platform or encoder settings call for.
| Encoder bitrate | × 1.5 (minimum) | × 2 (comfortable) | Against the 10–20 Mbps planning range |
|---|---|---|---|
| 5 Mbps | 7.5 Mbps | 10 Mbps | Inside it, at the low end |
| 6 Mbps | 9 Mbps | 12 Mbps | Inside it |
| 8 Mbps | 12 Mbps | 16 Mbps | Inside it |
| 10 Mbps | 15 Mbps | 20 Mbps | Inside it, at the top end |
| 12 Mbps | 18 Mbps | 24 Mbps | Above it; plan from the bitrate, not the range |
Figures are per stream, before anything else shares the connection.
How to calculate live stream internet requirements
Five steps take you from an encoder setting to an upload figure you can hold a venue or provider to.
Find the bitrate
Get the combined video and audio bitrate from your platform's recommendations or your production team's encoder settings, and write it down in Mbps.
Apply headroom
Multiply by 1.5–2. Use the higher figure for long streams, important audiences, or venues where you can't test beforehand.
Count every outgoing stream
Sending to two platforms from one encoder, or running a second encoder as backup, can mean two full streams leaving the venue. Each needs its own share.
Add everything else that uploads
Remote presenters on video calls at about 1.5 Mbps each, photographers sending images and staff cloud sync all draw on the same upload.
Compare with measured steady upload
Test from the encoder's actual position at the time of day you'll stream, and look for the lowest sustained figure, not the peak.
Worked example: a launch stream with remote speakers
A product launch streams to one platform at 8 Mbps. With headroom, 8 × 2 = 16 Mbps. Two remote speakers join by video call, adding 2 × 1.5 = 3 Mbps. Upload needed at the reveal: 16 + 3 = 19 Mbps. If the photo team also has to send large image sets during the event, that's worked out separately from the volume and the time allowed, and it can easily outweigh the stream.
Now compare with the venue. If its line offers 20 Mbps of upload shared with the building, the plan fails even though 19 is less than 20: nothing is left for the building's other users, and photo uploads haven't been counted. Either the stream gets its own connection, or photo uploads wait until the stream ends. Our event bandwidth calculator runs these sums for you.
Multiple streams: how upload adds up
Every stream that leaves the venue needs its own share of upload. These examples apply 2× headroom.
| Setup | Upload calculation | Planning upload |
|---|---|---|
| One stream at 6 Mbps | 6 × 2 | 12 Mbps |
| The same stream sent separately to two platforms | 2 × (6 × 2) | 24 Mbps |
| Two rooms, each streaming at 8 Mbps | 2 × (8 × 2) | 32 Mbps |
| One stream at 8 Mbps plus four remote presenters | (8 × 2) + (4 × 1.5) | 22 Mbps |
| Main and backup encoders both sending at 6 Mbps | 2 × (6 × 2) | 24 Mbps |
If a cloud service receives one stream and forwards it to several platforms, only one stream leaves the venue. Check how your setup works before doubling.
Network setup for a stable stream
Upload is only half of it. How the encoder connects decides whether the upload you've paid for actually reaches it.
Cable the encoder
A network cable from the encoder to the switch takes WiFi airtime out of the equation, so a filling room can't push the stream off its connection.
Give the stream its own network
Put the encoder on a production network guests can't join, as described in separate networks for events, so guest load can't take its share.
Reserve the stream's upload
Where the router allows it, set aside the stream's upload so other traffic can't eat into it at the critical moment.
Keep the stream desk near the connection
Long cable runs and extra switches add places to fail. Plan the desk position together with the network layout.
Avoid a phone hotspot as the main link
A phone hotspot shares mobile capacity with everyone nearby, and mobile upload is limited and varies from site to site.
Live stream internet test plan
Run this before the day, then again before doors.
- Test from the encoder's real position, over the same cable and network it will use
- Test at the time of day you'll go live, ideally on a matching weekday
- Run a private or unlisted test stream for at least as long as the longest segment
- Watch the encoder's own upload and dropped-frame readings, not just a speed test
- Check the stream on a phone using mobile data, off the venue network
- Test again once guests and staff are connected, if you can
- Switch to the backup connection on purpose and time how long the stream takes to recover
- Write down the bitrate, the measured upload and who decides to lower quality if needed
Backup connections for live streams
A stream that matters needs a second path out. The usual pattern is a main fixed connection with enough steady upload and a backup internet link that takes over if the main one fails. A 4G/5G router makes a useful backup, but plan it honestly: mobile networks can congest when a crowd gathers, and mobile upload is limited and site-dependent. Test the backup at the venue, at a busy time, before relying on it.
Decide in advance what happens on failover. Lowering the bitrate so the stream fits the backup's upload is usually better than a stream that keeps dropping. Recording locally on the encoder means the content survives even if the live stream doesn't. For a full event-day setup, see live streaming internet for events.
Questions people ask
How much upload speed do I need to live stream?
Plan 10–20 Mbps of steady upload per live stream. Work it out from your encoder's bitrate: multiply by 1.5 for a minimum and by 2 for comfortable headroom, so a stream at 8 Mbps needs 12–16 Mbps. Then add upload for anything else sharing the connection, such as video calls at about 1.5 Mbps each.
Is 10 Mbps upload enough for live streaming?
10 Mbps of steady upload can carry one stream at around 5–6 Mbps with headroom (5 × 2 = 10; 6 × 1.5 = 9). It isn't enough for higher bitrates, a second stream, or a stream sharing the line with video calls and guest traffic. If the 10 Mbps is shared with a building, assume you'll get less.
Can I live stream over WiFi?
You can, but cable the encoder wherever possible. WiFi airtime is shared with every device in range, so a room filling with guests can squeeze the stream. A network cable to the switch and a production network that guests can't join remove both risks. If WiFi is unavoidable, test it with the room full.
Can I live stream an event over 4G or 5G?
Sometimes, for a modest stream, but treat 4G/5G as the backup rather than the main connection for anything important. Mobile networks can congest when a crowd gathers, and mobile upload is limited and varies by site. If 4G/5G is the only option, test at the venue at a busy time and choose a lower bitrate.
What happens if upload drops during a live stream?
If upload falls below the stream's bitrate, the encoder starts buffering, viewers see stuttering or lower quality, and the stream may disconnect. Headroom of 1.5–2 times the bitrate absorbs short dips. A backup connection, a plan for lowering the bitrate and a local recording protect against longer ones.
Do I need double the upload to stream to two platforms?
If your encoder sends separately to each platform, yes: each destination is a full stream leaving the venue, so two platforms at 6 Mbps with 2× headroom need 2 × 12 = 24 Mbps. If a cloud service receives one stream and forwards it to several platforms, only one stream's worth of upload leaves the venue.
