A specialist checks a wired connection and live-streaming equipment.

ASAWEB GUIDE

Internet for live streaming is not calculated from the plan's maximum speed.

A broadcast depends on stable upload with headroom, low packet loss and a test performed under real event conditions.

Direct answer

Add the video and audio bitrates of every signal leaving through the connection, then apply planning headroom. As an operational reference, reserve 1.5 to 2 times the total—and validate stability, loss, jitter and redundancy in a real test.

First concept

Download does not replace upload

Viewers consume download. Broadcasters continuously send data and depend on upload. A fast advertised plan can offer lower upload, vary throughout the day or share capacity with other venue users.

Test the connection used by the encoder, preferably over Ethernet, in the same environment and at a similar time to the event.

Calculation

Use total bitrate × safety margin

  1. 01

    Define the output

    Resolution, frame rate, codec and bitrate accepted by the destination.

  2. 02

    Add audio and video

    Include every signal that will actually leave through the local connection.

  3. 03

    Count destinations

    Separate direct outputs add together; one signal to cloud restreaming does not multiply at the source.

  4. 04

    Apply headroom

    Plan for 1.5 to 2 times the total as a starting point, then test the network.

AsaWeb practice

In conventional streaming, reach also depends on the bitrate delivered to viewers

For AsaWeb's conventional operations aimed at a broad Brazilian audience, the most common outgoing range is 1,500 to 2,500 kbps—1.5 to 2.5 Mbps. A frequent starting recommendation is about 1,500 kbps when the priority is access from mobile phones, 3G or 4G networks and connections with variable capacity.

A higher bitrate does not automatically improve the experience. It can increase buffering, start time and abandonment for viewers with limited connectivity. Configuration must balance image legibility, motion, audio, audience profile and player capability.

This range is an AsaWeb operational reference, not a universal rule. Fast motion, small on-screen text, adaptive multi-quality delivery or controlled networks may require a different setup.

1,500 kbps · 1.5 Mbps

A frequent starting point for conventional streaming that prioritizes compatibility and mobile audiences.

2,000 to 2,500 kbps

May provide more definition when the content, player and audience connectivity allow it.

Platform reference

One 1080p30 signal sent directly to YouTube

YouTube's current H.264 reference for 1080p at 30 fps lists 10 Mbps video and 128 kbps stereo audio. That is about 10.1 Mbps. With planning headroom, the source connection would need roughly 15 to 20 Mbps of genuinely stable upload for this output.

This example explains a YouTube-specific recommendation; it is not AsaWeb's default conventional-streaming configuration. Resolution, codec, platform, protocol, transcoding, audience profile and network conditions change the calculation.

Official YouTube reference

Check supported bitrates and codecs before configuring the encoder.

Open specifications

Facebook Live specifications

Review the destination's current format and resolution requirements before the event.

Open specifications

Multichannel

Architecture changes source consumption

If the encoder sends four independent outputs, the connection must support their combined bitrate. If it sends one signal to a cloud distribution platform, the source carries that signal once and the platform replicates it to compatible destinations.

Network quality

Speed without stability is still a risk

  • 01Prefer Ethernet to Wi-Fi
  • 02Check packet loss, jitter and sustained variation
  • 03Avoid competing traffic on the same network
  • 04Keep a backup connection when impact justifies it
  • 05Test encoder, cables, power and platform together
  • 06Confirm social-platform credentials before the event

Final checklist

Before going live

  • 01Test at the venue and near the event's time window
  • 02Keep bitrate below observed stable capacity
  • 03Monitor both encoder output and destination return
  • 04Define who can reduce quality or move to backup
  • 05Record approved settings to avoid last-minute changes

NEXT STEP

Would you like to size connectivity and distribution for your event?

Send the desired resolution, destinations, venue and an upload-test result.

Plan my broadcast
Talk to AsaWeb