Home | Save 40–50% Bandwidth: H.265 vs H.264 for UK Event Production | Go Back

Save 40–50% Bandwidth: H.265 vs H.264 for UK Event Production

Date added: 5/09/2026

Use H.264 for live streaming, webinars and anything that must play back on the widest range of devices without a second thought. Use H.265 for 4K or HDR recording, archival masters and bandwidth-constrained delivery where you control the playback environment. Firefly AV, an AV hire and event production company based in Leeds and Preston working UK-wide, encodes both formats daily across live and hybrid events, and the choice almost always comes down to compatibility versus efficiency, not raw picture quality.

TL;DR:

  • H.265 offers roughly 40 to 50% smaller file sizes and bandwidth usage than H.264 at the same quality, especially at 4K resolution.
  • Software encoding for H.265 is significantly slower than H.264, requiring dedicated hardware encoders for real-time live streaming.
  • Compatibility issues still limit H.265 adoption on many platforms, browsers, and live ingestion systems, making H.264 the safer choice for broad device support.
  • Capturing and archiving 4K or HDR footage in H.265 reduces storage costs over time, but live production should verify platform support first.
  • Licensing complexities for H.265 involve multiple patent pools, often increasing legal overhead compared to the predictable licensing of H.264.

Table of Contents

H264 vs H265: how do they compare across the metrics that matter?

H.265 (HEVC) beats H.264 (AVC) on file size and bandwidth in almost every test, but H.264 still wins on compatibility and encoding speed. That trade-off is the entire story of this comparison, and it plays out differently depending on whether you’re streaming live, packaging a VOD library, or archiving 4K masters.

Bitrate tells the clearest part of the story. A 1080p stream at good quality typically needs 4,500 to 6,000 kbps in H.264, but the same perceptual quality in H.265 usually lands between 2,250 and 3,000 kbps. At 4K, the gap widens: H.264 wants 25 to 35 Mbps, while H.265 can hold similar quality at 12 to 18 Mbps, a saving of roughly 40 to 50% that grows with resolution.

Dimension H.264 (AVC) H.265 (HEVC)
Typical 1080p bitrate 4,500–6,000 kbps 2,250–3,000 kbps
Typical 4K bitrate 25–35 Mbps 12–18 Mbps
Compression efficiency Baseline ~40–50% smaller at matched quality
Encoding cost Lower, mature hardware support 2–10x heavier in software; hardware encoders often needed
Device/browser decode Near-universal Strong on Safari/iOS; patchier on Chrome/Firefox
Platform live ingest Widely accepted Restricted or unsupported on many platforms
Licensing Largely settled for streaming Fragmented across multiple patent pools

A few things fall out of that table worth acting on:

  • If your event streams to YouTube, Facebook or a corporate webinar platform, check ingest support before you commit to H.265 — many still expect H.264.
  • If you’re archiving 4K or HDR event footage for a client library, H.265 cuts storage costs meaningfully over a multi-year archive.
  • If you’re running adaptive bitrate (ABR) ladders for VOD, a mixed approach (H.264 for lower rungs, H.265 for the top rung) often delivers the best reach-to-cost ratio.

Why does H.265 compress video more efficiently than H.264?

The efficiency gap comes down to how each codec carves up and predicts a frame. H.264 works in fixed 16x16 macroblocks. H.265 replaces that with coding tree units (CTUs) that scale up to 64x64 pixels and split recursively, so a static sky gets one large block while a busy crowd shot gets many small ones. That flexibility alone accounts for a large share of the bitrate saving.

H.265 also supports far more prediction modes: 35 intra-prediction directions against H.264’s 9, plus more refined inter-prediction and motion compensation. It adds sample adaptive offset (SAO) filtering to reduce banding and ringing artefacts after decoding, and its entropy coding (CABAC, present in both, but tuned differently) squeezes out more redundancy per frame. These gains scale with resolution, which is why the improvement at 4K is more dramatic than at 720p.

The objective evidence backs this up. A Tektronix PQA500 laboratory study comparing H.264 and H.265 encoders found H.265 outperformed H.264 in PQR and PSNR testing across multiple scenes and bitrates, though the margin depended heavily on scene content and encoder implementation.

That last caveat matters more than it sounds. Two things worth knowing before you trust any codec benchmark:

  • Results vary by encoder build: x265 versus a hardware HEVC encoder can produce noticeably different output at the same nominal bitrate.
  • CRF values don’t map directly between x264 and x265 — a CRF 23 in one isn’t equivalent to CRF 23 in the other, so compare using VMAF or PSNR scores, not raw CRF numbers.

Statistic to remember: independent lab testing shows H.265 delivering measurably better picture quality per bit than H.264, but the size of that advantage shifts with scene complexity, motion, and which specific encoder produced the file.

Is H.265 practical to encode in real time?

Encoding H.265 in software is genuinely heavier work. Typical figures put x265 at two to ten times slower than x264 for equivalent settings, which rules out software-only HEVC encoding for most live, real-time production unless you throw serious CPU at it.

That’s where hardware encoders earn their keep. NVIDIA NVENC, Apple VideoToolbox and Intel Quick Sync all offer dedicated HEVC encoding silicon that handles 4K in real time without saturating a CPU, and most professional capture and streaming rigs built after 2022 include one of these.

Device and browser support has its own gaps:

  • Safari and iOS have supported HEVC playback natively for years, including hardware decode on recent iPhones and iPads.
  • Chrome and Firefox have historically offered fragmented HEVC support, often relying on hardware decode being present rather than guaranteeing software fallback.
  • Smart TVs and set-top boxes released since roughly 2018 generally decode HEVC fine, but older hardware in the field can’t.
  • Live platform ingest is the sharpest constraint: many streaming platforms still require H.264 for live ingest regardless of what the viewer’s device can decode.

Pro Tip: Never assume HEVC decode support from a device spec sheet alone. Test playback on the actual make and model your audience will use, especially for corporate webinars where attendees join from locked-down work laptops with older GPU drivers.

What does licensing complexity actually cost you?

H.264’s patent position settled years ago; common internet streaming use is largely predictable from a licensing standpoint, which is a big part of why it became the default codec for a generation of platforms.

H.265 never reached that same clarity. Its patents sit across at least three competing pools, MPEG LA, HEVC Advance and Velos Media, and a distributor implementing HEVC at scale may need to negotiate with more than one to stay covered.

That fragmentation has real consequences:

  • Larger streaming platforms often budget legal and licensing overhead specifically for HEVC deployment that H.264 never required.
  • Some services have opted for AV1 instead, partly to sidestep HEVC’s patent complexity, even though AV1 hardware decode support is still catching up.
  • Smaller production teams generally never touch HEVC licensing directly, since it’s baked into the encoder or platform they use, but it explains why adoption has been slower than the technical case alone would predict.

Which codec should you use for live, VOD, recording and archiving?

Match the codec to the job rather than picking one for everything. Here’s a working checklist:

  1. Confirm destination ingest first. Check whether your streaming platform or venue’s receiving system accepts H.265 before you plan around it; if in doubt, default to H.264.
  2. Test on real playback devices, not assumptions, particularly for mixed corporate audiences joining from unmanaged laptops.
  3. Measure encoding cost against your hardware. If you’re not running NVENC, Quick Sync or VideoToolbox, software HEVC in real time is a risk for live events.
  4. Build an ABR ladder with H.264 at the base for guaranteed reach, and H.265 or AV1 at the top rung for viewers whose devices support it.
  5. Keep an H.264 fallback rendition for every H.265 master and test the full chain end-to-end before the event, not on the day.

For settings: 1080p30 live typically sits around 4,500 to 6,000 kbps in H.264 or 2,250 to 3,000 kbps in H.265; 4K HDR recording for later editing is usually captured in a higher-bitrate intermediate rather than a heavily compressed delivery codec.

Pro Tip: If you’re recording multi-camera footage for post-production, don’t deliver in a highly compressed H.265 file straight off the camera. Capture in a higher-bitrate format and compress to H.264 or H.265 only at final export, once editing and colour grading are finished.

How does Firefly AV choose between H.264 and H.265 on-site?

How does Firefly AV choose between H.264 and H.265 on-site? — overview diagram

Based in Leeds and Preston and working UK-wide, Firefly AV makes this call on nearly every hybrid and broadcast event we run. Our Birddog cameras and Blackmagic Video Assist units feed a Vmix 4K Media Server, which lets us encode to H.264 for the live platform feed while retaining a higher-bitrate H.265 or ProRes master for the client archive.

Our advice to organisers: request H.265 only when you know the playback environment (an internal 4K screen, a controlled corporate portal), and default to H.264 for anything hitting a public streaming platform or a mixed-device audience. Paired with Absen LED walls, Panasonic projectors, and Sennheiser mics run through Allen & Heath consoles, the encoding decision is usually the easiest part once the rest of the signal chain is right.

— Michael

Get help choosing and running the right codec for your event

Getting the codec right matters less if nobody’s watching the ingest logs during the show, and that’s the gap Firefly AV closes for event organisers who’d rather not manage encoder settings mid-event. We run hardware encoding, managed ABR streams, and on-site technical management as standard on hybrid and broadcast jobs, packaging output in whatever mix of H.264 and H.265 your destination platform actually accepts.

Firefly AV

Book Firefly AV when your event involves 4K or HDR delivery, multi-camera hybrid production, or high-concurrency live streams where a rejected ingest stream isn’t an option. Our equipment hire catalogue covers the Vmix 4K Media Server, Birddog cameras and streaming kit behind these setups, and our AV equipment overview for event planners is a good starting point if you’re briefing an event for the first time. Get in touch to talk through your streaming requirements before you lock in a venue or platform.

Sources

Consult the ITU-T H.265 Recommendation for the formal specification, and the live streaming platform guidance and export settings guide for operational detail.

FAQ

Is H.264 better quality than H.265?

No. At the same bitrate, H.265 generally delivers better perceptual quality, as shown in Tektronix PQA500 lab testing, but H.264 remains excellent quality at higher bitrates where storage or bandwidth isn’t a constraint.

What are the disadvantages of H.265?

H.265 costs more to encode (2 to 10 times slower in software), has fragmented licensing across multiple patent pools, and faces inconsistent browser decode support, particularly on Chrome and Firefox compared with Safari.

Why use H.264 instead of H.265?

Choose H.264 when you need guaranteed compatibility across devices and browsers, lower encoding overhead, and predictable licensing, which is why most live streaming platforms still require H.264 for ingest.

Is H.264 high quality?

Yes. H.264 produces very high quality video at adequate bitrates, and the vast majority of broadcast, web and mobile video still runs on it; it simply needs a higher bitrate than H.265 to reach the same perceptual result.

Can I use both H.264 and H.265 for the same event?

Yes, and it’s often the best approach: many production teams encode an H.265 or higher-bitrate master for archival and top-tier delivery while keeping an H.264 rendition as a compatibility fallback for live ingest and older devices.

Does 2026 hardware make H.265 easier to use for live production?

Hardware encoders like NVIDIA NVENC, Apple VideoToolbox and Intel Quick Sync have made real-time HEVC encoding far more practical than pure software encoding, but platform ingest restrictions, not hardware capability, remain the main reason many live events still default to H.264.