Reference Formats
VP9
VP9 is a royalty-free video codec developed by Google, typically packaged inside the WebM container, and used most prominently as YouTube's primary delivery codec alongside AV1.
Extension
.webm
Full name
VP9 (successor to VP8 in Google's VPx codec line)
Introduced
2013
Vendor
Google, via The WebM Project
What is inside the container
VP9 is normally delivered inside WebM, itself a restricted profile of the Matroska container, though it also appears inside MP4. It carries no royalty for encoding or decoding — Google issues an irrevocable free patent license, and VP9's IP is now additionally cross-licensed under the Alliance for Open Media's patent framework alongside AV1, since Google was a founding AOMedia member.
How to open it
For archives
VP9 is a reasonable royalty-free alternative to H.265 for DAM libraries wanting to avoid HEVC's fragmented patent licensing, particularly for content whose primary delivery target is the web or YouTube, where VP9 support is deep and mature. For broader compatibility beyond browsers — mobile apps, legacy players, professional NLEs — keep an H.264 proxy alongside any VP9 delivery asset, since VP9 support outside the browser/Google ecosystem is less universal than H.264's.
Google released VP9 in 2013 as the successor to VP8, developed in-house and distributed under The WebM Project alongside the Matroska-derived WebM container. It was positioned explicitly as a royalty-free alternative to HEVC, arriving the same year HEVC was finalized — a direct competitive response to the licensing complexity that would soon push the industry toward AOMedia and AV1. Google backed that free-license claim with an irrevocable patent grant, and has since folded VP9 into the broader royalty-free umbrella alongside AV1 as a founding member of the Alliance for Open Media.
VP9’s largest real-world footprint is YouTube, where it has served as a default adaptive-streaming codec for years, giving it deep, mature support across Chrome, Firefox, Edge, and Android — platforms where Google has direct influence over decode support. That gives VP9 a somewhat different adoption shape than AV1 or H.265: it’s extremely well-supported in the web/Google ecosystem specifically, but less universally adopted in professional NLEs, legacy hardware players, and non-Google mobile contexts.
For a DAM, VP9’s main practical value is as a genuinely royalty-free, storage-efficient delivery codec for web-first content, without the multi-pool licensing questions that come with HEVC. It’s a sensible pairing with WebM for browser-based asset previews and embedded players, though libraries needing guaranteed compatibility across professional editing tools and older devices should still keep an H.264 proxy in the mix rather than relying on VP9 as the sole delivery format.
| VP9 | H.265 (HEVC) | |
|---|---|---|
| Royalty status | Royalty-free, irrevocable Google patent grant | Licensed across up to three patent pools |
| Primary container | WebM (restricted Matroska) | MP4 or MOV |
| Strongest ecosystem | YouTube, Chrome, Android | Apple devices since iOS 11 |
Frequently asked
Is VP9 a container or a codec?
It's a codec — the video compression method itself, not a file wrapper. VP9 is almost always delivered inside the WebM container, a restricted profile of Matroska, though it can also appear in MP4.
Does using VP9 in a DAM's delivery pipeline carry any licensing cost?
No — Google grants an irrevocable, royalty-free patent license for VP9, and it's additionally covered under the Alliance for Open Media's patent cross-license framework alongside AV1, since Google is a founding AOMedia member.
Why does so much of our video traffic show up as VP9 in analytics?
Because VP9 has been YouTube's default adaptive-streaming codec for years, and browsers that connect to Google's ecosystem — Chrome, Android's media framework — have particularly deep, well-optimized VP9 support.
Is VP9 as widely supported as H.264 outside of browsers?
No — VP9 support is strong in browsers and Google's own platforms, but it's less universal in professional NLEs, older hardware players, and some mobile ecosystems compared to H.264's near-total compatibility.
How does VP9 compare to H.265 for storage efficiency?
The two are broadly comparable in compression efficiency for equivalent quality, but VP9 has the advantage of being unambiguously royalty-free, avoiding the fragmented multi-pool licensing questions that come with HEVC.
What tool should we use to batch-transcode assets into VP9?
ffmpeg with the libvpx-vp9 encoder is the standard open-source path (`ffmpeg -i input.mp4 -c:v libvpx-vp9 output.webm`), and it's widely used in production transcoding pipelines for WebM delivery.
Can VP9 files be played on older Windows systems without extra codecs?
VLC plays VP9-in-WebM natively regardless of Windows version, so it's a reliable fallback even on systems where the native Windows media stack doesn't handle WebM directly.
Is VP9 still relevant now that AV1 exists?
Yes, particularly for web-first and YouTube-targeted delivery, where it remains a mature, deeply supported default. AV1 offers better compression efficiency and is where Google's own long-term investment is heading, but VP9's browser and Android support base means it isn't obsolete.
Sources
- VP9 was publicly released by Google on June 17, 2013. checked 2026-08-07 — Wikipedia — VP9
- Official VP9 technical overview from The WebM Project. checked 2026-08-07 — WebM Project — VP9
- Google is a founding member of the Alliance for Open Media, which now covers VP9's patent cross-license alongside AV1. checked 2026-08-07 — Wikipedia — Alliance for Open Media