Key takeaways
- HEVC typically needs roughly 30–50% less bitrate than H.264 for similar visual quality, with the biggest gains at 1080p and 4K.
- H.264 remains the safest choice for universal playback, including older set-top boxes, browsers and budget devices.
- Keyframe interval and GOP structure matter as much as the codec for channel-change speed and segmenting.
- Many operators run both: HEVC for 4K and capable devices, H.264 as the compatibility baseline.
How the two codecs differ
H.264 (also known as AVC, MPEG-4 Part 10) was standardised in 2003 and became the default codec for broadcast contribution, streaming and video conferencing. H.265 (HEVC, High Efficiency Video Coding) followed in 2013 with one main goal: deliver the same perceived quality at a substantially lower bitrate.
HEVC achieves this through several structural improvements. Instead of the fixed 16×16 macroblocks of H.264, it uses coding tree units of up to 64×64 pixels that can be split recursively, so large flat areas such as sky or studio backgrounds are encoded very cheaply while detailed areas get finer partitions. It also offers more intra-prediction directions, improved motion vector prediction, better in-loop filtering (including sample adaptive offset) and more flexible transform sizes.
The cost of this efficiency is complexity. Encoding HEVC in real time typically requires considerably more CPU than H.264 at the same resolution, and decoding is also heavier — which is why hardware support on the receiving device is so important.
Profiles and levels
Both codecs define profiles (which coding tools may be used) and levels (limits on resolution, frame rate and bitrate). A decoder that supports a given profile and level is guaranteed to play any compliant stream within those limits.
H.264
- Baseline / Constrained Baseline — no B-frames, minimal tools; used for very old or low-power devices.
- Main — adds B-frames and CABAC entropy coding; a common choice for SD and HD broadcast.
- High — adds 8×8 transforms and other tools; the standard choice for HD streaming today.
HEVC
- Main — 8-bit 4:2:0, the most widely supported HEVC profile.
- Main 10 — 10-bit 4:2:0, required for HDR formats and preferred for 4K because it reduces banding.
For live channels the level is usually dictated by resolution and frame rate: for example, 1080p at 50/60 frames per second typically needs level 4.2 in H.264 and level 4.1 in HEVC, while 2160p at 50/60 fps needs HEVC level 5.1. Signalling a level that is higher than necessary can make some devices refuse a stream they could actually decode.
GOP structure and keyframe interval
Compressed video is organised into groups of pictures (GOPs). Each GOP starts with an intra-coded keyframe (an IDR frame) that can be decoded on its own, followed by predicted P- and B-frames that only store differences. Keyframes are large, so a long GOP saves bandwidth — but a player can only start decoding at a keyframe.
This has direct operational consequences for live delivery:
- Channel change time. With a 10-second GOP, a viewer may wait up to 10 seconds for the first picture. A 1–2 second keyframe interval is a common compromise for live TV.
- Segmenting. Segmented formats such as HLS require segments to begin on a keyframe. A keyframe interval that divides evenly into the segment duration (for example 2 seconds for 4- or 6-second segments) keeps segments aligned.
- Closed vs open GOP. Closed GOPs, where no frame references the previous GOP, are safer for segmenting and switching between bitrate renditions.
Typical bitrates by resolution
The bitrate a channel needs depends heavily on content: a news studio compresses far better than live sport with fast motion and crowds. The figures below are rough starting points for good-quality live delivery, not fixed rules.
| Resolution & frame rate | H.264 (typical) | HEVC (typical) |
|---|---|---|
| 576i / 576p (SD) | 1.5–2.5 Mbps | 1–1.8 Mbps |
| 720p50 | 3–4.5 Mbps | 2–3 Mbps |
| 1080i25 / 1080p25 | 4.5–6 Mbps | 3–4 Mbps |
| 1080p50 | 6–9 Mbps | 4–6 Mbps |
| 2160p50 (4K) | Rarely used | 15–25 Mbps |
Always validate with your own content and viewers' screens. Objective metrics such as VMAF or PSNR help, but a short side-by-side review of fast-motion scenes is still one of the best tests.
Device and decoder support
H.264 High Profile is decoded in hardware by practically every device in use today: smart TVs, streaming sticks, set-top boxes, phones, tablets and all major browsers. HEVC hardware decoding is standard on most smart TVs and streaming devices from the last several years and on modern phones, but support is less uniform on older set-top boxes, low-cost Android devices and in some desktop browsers.
Before switching channels to HEVC, check the decoder capabilities of the devices actually in your subscriber base. Software decoding of HEVC on weak hardware leads to dropped frames, heat and battery drain.
Licensing and the next generation
Both codecs are covered by patent pools, and HEVC licensing has historically been more fragmented than H.264. Device manufacturers usually handle decoder licensing, but operators deploying encoders should review their own obligations. AV1, a royalty-free codec from the Alliance for Open Media, offers further efficiency gains and is gaining hardware support in newer TVs and devices, but real-time AV1 encoding for many live channels is still demanding today.
Which codec to choose
- Choose H.264 when you need guaranteed playback on every device, when channels are SD or 720p, or when encoder capacity is limited.
- Choose HEVC for 4K, for bandwidth-constrained networks, and for subscriber bases dominated by recent smart TVs and streaming devices.
- Pass through rather than re-encode whenever the source already arrives in a suitable codec and bitrate — every re-encode costs processing and some quality.
How SaurusRex handles it: codec choice is made per channel. Channels can be transcoded or passed through untouched, HEVC sources are supported, and the console reports codec, resolution, frame rate, bitrate and real processing speed for every channel in real time. Learn more on the platform page.