Blog

AV1, H.265, and Browser Codecs Explained

Updated Jun 9, 2026

When H.265 shrinks files, when AV1 sources may grow, and how browser codec support affects Compress Video and Video to MP4.

Codec choices confuse almost everyone, including experienced editors. AV1 promises smaller files, H.265 (HEVC) is common on phones, and H.264 is still the compatibility king. In the browser, not every device can encode or decode every codec, which directly affects ALTools tools like Compress Video and Video to MP4.

The practical questions are simpler than the jargon: when does H.265 actually help, why can a converted file get bigger, and how should you choose settings for the people who will watch the result? That is what this guide covers.

A quick codec glossary

Codec	Role	Typical container
H.264 (AVC)	Widest playback support	MP4
H.265 (HEVC)	Better compression than H.264 at the same quality	MP4
AV1	Newer and very efficient	MP4, WebM
AAC	Common audio codec for web MP4 delivery	MP4

Container (MP4, MKV, MOV) is the box. Codec is how the video or audio inside that box is compressed. Converting "to MP4" often really means H.264 + AAC inside an MP4 container.

What browsers can do today

Support changes over time, but the broad pattern stays fairly consistent:

H.264 decode - nearly universal for playback
H.264 encode - widely supported for export in modern desktop and mobile browsers
H.265 encode - available on some platforms, often through Safari or Apple hardware paths
AV1 decode - growing steadily; encode is still less common in consumer browser tools

ALTools probes capabilities at runtime. If H.265 is unavailable, Compress Video falls back to H.264 and disables the Original preset that depends on HEVC.

The AV1 -> H.265 surprise

A common myth says, "Re-encode to H.265 and the file will always shrink."

If your source is already AV1, re-encoding to H.265 at a similar quality target can produce a larger file. You are trading a newer, more efficient codec for an older one without cutting bitrate enough to make up the difference.

ALTools warns about this in the Original preset hint on Compress Video. A few practical strategies:

Source	Goal	Suggestion
AV1 master	Smallest archive	Keep AV1; do not force H.265 without testing
AV1 master	Maximum compatibility	Accept a larger MP4 or transcode to H.264 for target players
H.264 master	Smaller web file	Try H.265 if the browser supports encode, otherwise lower the preset

Judge quality with your eyes, not just by the byte count.

H.265 in ALTools compress workflow

When Use H.265 (HEVC) is enabled and supported:

Output still stays in MP4 for practical compatibility
Bitrate savings can land around 30-50% versus H.264 at similar visual quality
Playback may still fail on older TVs, embedded players, or some web hosts

Enable H.265 when you control playback, such as on your own site or inside a modern mobile app. Turn it off when sending files to clients on unknown Windows versions or older hardware.

Safari on Apple Silicon often offers a reliable HEVC encode path. Chrome on Windows can vary more, so trust the on-page availability hints instead of assuming support.

Fast-Start and remux in Video to MP4

Not every job needs a full re-encode. If your file is already H.264 + AAC inside MP4, ALTools can apply Fast-Start only:

Moves the moov atom to the front of the file
Lossless - no generation loss
Almost instant compared with a full transcode

Use a full transcode when codecs do not already match your target (ProRes in MOV, VP9 in WebM, and so on). The output targets H.264 + AAC for broadly compatible MP4 delivery.

Practical decision tree

Need the smallest file for a modern audience?
  -> Compress with H.265 if available, then verify playback

Need the widest playback compatibility?
  -> Use an H.264 Medium/High preset, or full Video to MP4 transcode

Source already AV1?
  -> Avoid blind H.265 conversion; test both size and quality

Just fixing slow web playback start?
  -> Use Video to MP4 Fast-Start remux if the file is compatible

Why browsers differ from desktop tools

Desktop transcoding tools can often force codecs and settings almost arbitrarily. Browsers only expose a limited, sandboxed set of options for security, stability, and battery life. That is why ALTools documents fallbacks instead of promising every desktop workflow—we optimize for what runs reliably on real devices.

When browser export fails on an edge case, keep a desktop master and use ALTools for the 90% of jobs that do fit.

Symptoms and fixes

H.265 toggle grayed out. Your browser or OS does not expose an encoder path - use H.264.

Compressed file is bigger than the original. The source may already be AV1 or an efficient H.264 encode - lower the preset or skip compression.

Green or black playback after export. The source may use an unusual pixel format - try a full Video to MP4 transcode.

Audio out of sync after remux. Rare on clean MP4 files, but possible - try a full transcode or re-trim the source first.