H.264 vs H.265 vs VP9
How the three compare on efficiency and compatibility, why licensing shaped which won where, and which two Dexta can actually produce.
In short
H.264 plays on everything and is the safe default. H.265 and VP9 are roughly 30–50% more efficient at the same quality but are less universally supported. Dexta encodes H.264 and VP9 — it does not produce H.265.
A codec is the method used to store the picture. All three of these do the same broad job; they differ in how cleverly, and in who is allowed to use them without paying.
| H.264 (AVC) | H.265 (HEVC) | VP9 | |
|---|---|---|---|
| Released | 2003 | 2013 | 2013 |
| Efficiency vs H.264 | Baseline | ~40–50% better | ~30–40% better |
| Playback support | Universal | Good on Apple, patchy elsewhere | All modern browsers; weaker outside |
| Licensing | Patent pool, widely licensed | Complex, multiple pools | Royalty-free (Google) |
| Encoding speed | Fast | Slow | Slow |
| In Dexta | Yes — MP4, MOV | No | Yes — WebM |
Why H.264 still wins by default
It is twenty years old and less efficient than either successor, and it plays on literally everything: every browser, every phone, every television, every editing program, every upload form. When a file has to work rather than be small, that is worth more than 40% efficiency.
Where H.265 and VP9 fit
H.265 delivers the biggest saving and carries the messiest licensing, which is why it took hold in hardware — Apple devices, broadcast, 4K delivery — and never became a web default.
VP9 is royalty-free, which is exactly why Google could deploy it across YouTube and the browsers could support it without negotiation. On the web it is well supported; hand a .webm to a colleague to open in desktop software and you may get a shrug.
Choosing in practice
- Sending a file to a person, or uploading to a platform — MP4 with H.264. It cannot be refused.
- Serving video on your own web page — WebM with VP9 is smaller at the same quality, and every current browser plays it.
- Archiving 4K footage where storage is the constraint — H.265, using software that can encode it.
Mistakes worth avoiding
- Sending a WebM to someone who did not ask for one. It may not open outside a browser.
- Re-encoding H.264 to VP9 to "save space" on a file you already have. You lose a generation of quality for a saving that only applies if you were encoding from a master.
- Comparing CRF numbers between codecs.
Tools used in this guide
Related guides
CRF explained
What the Constant Rate Factor actually controls, what the numbers mean, and why the same CRF gives a different result in H.264 and VP9.
2 min readvideoHow video compression works
Why a minute of video is not 60 still photographs, what an encoder actually throws away, and why the same setting behaves differently on two clips.
3 min readvideoVideo bitrate explained
What bitrate actually measures, how it relates to file size and quality, and why Dexta gives you a quality target instead of a bitrate field.
2 min read