A dependable web video balances reach, quality, decoding cost, and file weight. There is no one-line answer here: it depends on evidence from the source, the specific properties named below, and the destination's real requirements.
Container, codec, profile, bitrate, frame rate, channels, and duration jointly determine whether media will play well. In “The practical guide to video codecs for the web,” begin with this specific observation: H.264 has broad hardware support and remains the compatibility baseline.
Three findings that guide this choice
The core distinction
H.264 has broad hardware support and remains the compatibility baseline.
The practical trade-off
VP9 and AV1 can reduce bitrate at comparable quality but encode more slowly.
The verification test
Resolution alone says little without bitrate, frame rate, motion, and codec efficiency.
A practical decision for this workflow
Use an H.264 MP4 baseline, then add WebM or AV1 derivatives where traffic justifies them.
Use resolution alone says little without bitrate, frame rate, motion, and codec efficiency. as the acceptance test on a representative source before committing an entire archive, publication, or delivery batch.
The video & audio mistake to avoid here
Keeping a mezzanine bitrate for delivery and forcing every mobile visitor to download it.
That failure conflicts directly with the recommendation for “The practical guide to video codecs for the web”: Use an H.264 MP4 baseline, then add WebM or AV1 derivatives where traffic justifies them.
Review checklist before delivery
- ✓Video and audio codecs are supported by the destination.
- ✓Duration, frame rate, and audio sync remain correct.
- ✓High-motion detail and quiet audio passages remain acceptable.
- ✓Captions, chapters, and required metadata were retained or exported separately.
Judge “The practical guide to video codecs for the web” by whether the result passes these specific checks, not by whether a new file merely opens.