Encoding, bitrate and networks

Every live stream is a race against the network. A computer or phone must compress video and audio in real time and upload it continuously to a platform's ingest servers, which then transcode it into versions for viewers on different devices and connections. If the upload cannot keep up, frames drop and viewers see stutters, freezes or disconnections. Understanding encoding settings, bitrates, keyframes, latency and network reliability lets streamers deliver the best possible picture within their connection. This lesson covers how streaming delivery works, codecs, resolution and frame rate choices, bitrate and upload bandwidth, keyframe intervals and rate control, platform recommendations, latency, network reliability, multistreaming and simulcasting, and monitoring stream health.

How live delivery works

A live stream travels through several stages. The streaming software captures sources, composes scenes and encodes the result. It sends the stream to the platform's ingest server using a protocol, most commonly RTMP (Real-Time Messaging Protocol) or its encrypted form RTMPS; newer protocols such as SRT and WebRTC-based ingest (WHIP) offer lower latency or better resilience, and some platforms accept them. The platform then transcodes the stream into several renditions at different resolutions and bitrates, a ladder, and delivers them to viewers through content delivery networks using adaptive streaming formats such as HLS, so each viewer receives the best rendition their connection can handle. Some platforms let streamers send multiple renditions themselves, as with Twitch's Enhanced Broadcasting, offloading transcoding to the streamer's computer.

Codecs

A codec compresses video. H.264 (AVC) is universally supported by platforms and devices and remains the default for most streaming. HEVC (H.265) and AV1 compress more efficiently, delivering similar quality at lower bitrates or better quality at the same bitrate, and are increasingly supported for ingest on some platforms and with recent hardware encoders. Audio is usually encoded with AAC, typically at 128 to 192 kbps stereo, or Opus on some WebRTC-based systems. Check each platform's current ingest support before choosing a newer codec; at the time of writing, YouTube accepts H.264, HEVC and AV1, and Twitch supports HEVC and AV1 for some configurations through Enhanced Broadcasting, while standard Twitch ingest uses H.264.

Resolution and frame rate

Higher resolution and frame rate need more bitrate to look good. Fast-moving content, such as action games and sports, needs a high frame rate (60 fps) for smooth motion, and suffers most from compression artefacts. Slower content, such as talk shows, art and board games, looks fine at 30 fps, and the bitrate saved can improve detail. If bandwidth is limited, a sharp 720p60 stream usually looks better than a blocky 1080p60 stream at the same bitrate. Downscaling inside the streaming software, for example from a 1440p game output to a 1080p or 936p stream, reduces the encoding load. For vertical streams on mobile platforms, 1080 × 1920 or 720 × 1280 at 30 fps is common.

Bitrate and upload bandwidth

Bitrate is the amount of data per second in the stream, usually measured in kilobits per second (kbps) or megabits per second (Mbps). The total stream bitrate is the video bitrate plus the audio bitrate plus a small protocol overhead. The upload connection must sustain this continuously, with headroom for fluctuations and for anything else using the network, such as game traffic, voice chat and other household devices. A common rule is to use no more than about 70 to 80 % of the reliably measured upload speed for the stream.

Here \(U_{\text{reliable}}\) is the sustained upload speed measured over time, not a single best speed test. Multistreaming directly from the computer to several platforms multiplies the required upload, while restreaming services take one upload and distribute it.

Platform recommendations

Platforms publish recommended settings, which change over time. At the time of writing, commonly cited figures include:

Using the platform's own setup wizard or the streaming software's auto-configuration gives a starting point. For low-motion content, lower bitrates look fine; for high-motion content, more bitrate or lower resolution is needed.

Keyframes and rate control

Video compression stores occasional complete frames, called keyframes or I-frames, and in between stores only the changes. The keyframe interval is the time between keyframes. Platforms generally require a keyframe interval of 2 seconds, because their transcoders and adaptive streaming segments rely on it; incorrect intervals can cause buffering, poor quality or warnings in stream health dashboards. Rate control determines how bitrate varies: constant bitrate (CBR) keeps the bitrate steady, which suits live streaming because it avoids sudden spikes that the network cannot handle, and is what most platforms recommend. Variable bitrate (VBR) and constant quality modes suit local recordings, where bandwidth is not a constraint.

So at 60 fps with a 2-second interval, a keyframe occurs every \(60 \times 2 = 120\) frames. Encoder presets trade quality against processing: slower presets give better quality per bit but use more GPU or CPU. Profiles such as "high" and tuning options such as look-ahead and psycho-visual tuning can improve quality slightly. Streaming software's default presets for hardware encoders are good starting points.

Latency

Latency is the delay between something happening on stream and viewers seeing it. Traditional HLS delivery produced delays of 15 to 30 seconds; platforms now offer low-latency modes of a few seconds, and WebRTC-based systems can deliver under a second. Low latency makes chat interaction feel natural, since the streamer can respond to messages about what just happened, but it can reduce buffering protection for viewers on weak connections. Higher latency can be useful for competitive games, where a delay prevents stream sniping, viewers watching the stream to gain an advantage against the streamer; some streamers add an intentional delay for this reason. Choose the platform's low-latency setting for interactive shows and consider delays for competitive play.

Network reliability

Wired Ethernet connections are far more reliable than Wi-Fi for streaming, because Wi-Fi suffers interference and fluctuating speeds. Other reliability measures include quality of service (QoS) settings on the router to prioritize streaming traffic; avoiding large downloads, cloud backups and video streaming on the same network during streams; choosing a nearby ingest server, or letting the software choose automatically; and having a backup connection, such as a mobile hotspot, for important streams. For IRL and remote events, bonded cellular devices or services combine several mobile connections, and protocols such as SRT handle packet loss better than RTMP. Upload speeds on home connections vary: cable and DSL connections often have much lower upload than download speeds, while fibre connections are usually symmetrical.

Multistreaming and simulcasting

Multistreaming sends one stream to several platforms simultaneously, either directly from the streaming software, which multiplies upload bandwidth, or through a restreaming service that takes one upload and redistributes it. It can widen reach, but it complicates chat (several chats to read, though tools can merge them), splits community and income, and may conflict with platform terms: some platforms' partnership agreements restrict simultaneous streaming of the same content on other platforms, or have done so at various times. Read current terms carefully. Some streamers simulcast to a horizontal platform and a vertical platform with different layouts, using software that outputs two canvases.

Monitoring stream health

Streaming software shows dropped frames due to network (upload problems), skipped frames due to encoding lag (encoder overload), and rendering lag (the software cannot draw scenes fast enough). Platform dashboards show stream health, bitrate received, keyframe interval and warnings. Watching these indicators during streams, especially in the first minutes, catches problems before viewers complain. Common fixes include lowering bitrate for network drops, switching to a hardware encoder or faster preset for encoding lag, and simplifying scenes or capping game frame rates for rendering lag. Recording a short private test stream before important broadcasts confirms settings.

Bitrate and image quality

The bitrate a stream needs depends on how much the picture changes. A static talking head at 1080p30 can look clean at 4,500 kbps, while a fast first-person game with grass, particles and camera movement at 1080p60 can look blocky even at 6,000 kbps with H.264. Bits per pixel is a rough way to compare settings:

As a rough guide for H.264, values below about 0.05 bits per pixel tend to break up in fast motion, while talking heads stay acceptable at lower values. Newer codecs such as HEVC and AV1 achieve similar quality at lower bitrates, which is why platforms that accept them allow higher resolutions within similar bandwidth.

Encoder presets and hardware encoders

Software encoders such as x264 offer presets from very fast to very slow; slower presets give better quality at the same bitrate but use more processor power. Hardware encoders built into graphics cards, such as NVIDIA NVENC, AMD AMF and Intel Quick Sync, encode with little impact on game performance, and recent generations match or beat x264 at medium presets for streaming. Most single-PC streamers now use a hardware encoder. Watch for encoder overload warnings in the streaming software, which mean frames are being skipped because the encoder cannot keep up.

Testing a connection before going live

A speed test measures a moment, not the whole evening. Run several tests at the time of day you plan to stream, look at upload speed and jitter, and run a private test stream for at least 30 minutes while watching dropped frames. Many platforms offer a bandwidth test mode or an unlisted stream option for this purpose. Household activity such as cloud backups, game downloads and video calls can consume upload during a stream, so pause backups and use quality-of-service settings on the router where available.

Choosing settings when unsure

When unsure, start conservatively and increase quality step by step. Begin with 720p at 30 or 60 fps and a bitrate well inside the upload budget, run test streams, then raise resolution or bitrate only while dropped frames stay near zero and the picture holds up in fast scenes. Viewers forgive a slightly soft picture far more readily than buffering, frozen frames or audio that drops out, so reliability should always come first.