Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use -vsync vfr to preserve VFR); (2) different audio sample rates not resampled (add -ar 48000 ); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run ffprobe on both source and output to compare timing.

Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use -vsync vfr to preserve VFR); (2) different audio sample rates not resampled (add -ar 48000 ); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run ffprobe on both source and output to compare timing.

Guide

WebM Format: Open Web Video Container — VP8, VP9, AV1 & Opus

PC By Pablo Cirre • Updated May 7, 2026

WebM — Open Web Video Container Format Complete Guide

What Is WebM?

WebM is an open, royalty-free multimedia container format developed by Google and released in 2010 as part of the WebM Project. Designed specifically for HTML5 video delivery on the web, WebM pairs exclusively open, royalty-free video and audio codecs:

Video: VP8 (2010), VP9 (2013), or AV1 (2018)
Audio: Vorbis (legacy) or Opus (modern, preferred)

WebM is a subset of the Matroska (MKV) container format, using the same EBML-based structure but restricting codec choices to the royalty-free codec stack. A WebM file is technically a valid MKV file, though the reverse is not true.

Google created WebM in response to the fragmented H.264 licensing situation in 2010, providing a patent-clear video solution for web publishers who could not pay MPEG LA royalties. WebM is supported natively in Chrome, Firefox, Edge, and Opera; Safari added VP9 and AV1 support in later versions.

WebM Container Structure

WebM inherits MKV's EBML structure with these restrictions:

Mandatory Video Codecs

V_VP8 — VP8 (legacy, initial codec)
V_VP9 — VP9 (current standard)
V_AV1 — AV1 (emerging, superior compression)

Mandatory Audio Codecs

A_VORBIS — Vorbis (legacy)
A_OPUS — Opus (modern, recommended for all new content)

Prohibited Features

WebM intentionally excludes many Matroska features:

No chapters
No embedded fonts
No attachments
No subtitle tracks (though text tracks can be added via WebVTT in the HTML layer)
No DRM metadata (WebM itself is DRM-free; DRM applied via EME — Encrypted Media Extensions — at the browser level)

VP8: The Original WebM Codec

VP8 was Google's first contribution to the open codec ecosystem, released simultaneously with WebM in May 2010:

Developed by On2 Technologies (acquired by Google for $124.6M in 2010)
MPEG-4 ASP compatible efficiency; roughly comparable to H.264 Baseline
Uses DCT-based compression with 8×8 blocks, loop filter, intraframe prediction
Maximum resolution: 16383×16383 (practical: up to 1080p)
Hardware decoders: widespread in modern SoCs (Qualcomm Snapdragon, MediaTek, ARM Mali)
Status: Frozen — no further development; superseded by VP9

VP8 is now rarely used for new content. Legacy WebM files from 2010–2016 frequently use VP8.

VP9: The Web Video Standard

VP9 is Google's second-generation open codec, released in 2013:

Roughly 40–50 % more efficient than VP8 at equivalent visual quality
Comparable to H.265/HEVC in compression efficiency (both superior to H.264)
10-bit and 12-bit colour support (vs. VP8's 8-bit only)
Profiles: Profile 0 (8-bit 4:2:0), Profile 1 (8-bit 4:2:2/4:4:4), Profile 2 (10/12-bit 4:2:0), Profile 3 (10/12-bit 4:2:2/4:4:4)
Maximum resolution: 65536×65536
Hardware decoders: available in all Qualcomm, MediaTek, Samsung Exynos, Intel, and Apple chips since ~2016

VP9 on YouTube

YouTube serves VP9 WebM as the default video stream for most content:

All YouTube 1080p, 1440p, 2160p (4K), and 8K streams: VP9 WebM + Opus audio
VP9 reduces bandwidth usage vs. H.264; Google estimates 35–40% savings
Chrome, Firefox, and Edge automatically receive VP9 streams; Safari receives H.264 unless VP9 is selected

AV1: The Next-Generation Open Codec

AV1 is developed by the Alliance for Open Media (AOMedia), a consortium including Google, Apple, Microsoft, Netflix, Amazon, Mozilla, and Intel, released in 2018:

30–40 % more efficient than VP9 at equivalent visual quality
50 % more efficient than H.264 (approximately)
Royalty-free, perpetually open-source specification
Supports 8, 10, and 12-bit colour depth
Supports HDR (HDR10, HLG) and wide colour gamut (Rec. 2020, DCI-P3)
Maximum resolution: 65536×65536

AV1 Hardware Support

NVIDIA RTX 3000+ — AV1 hardware decode and encode
Intel 11th Gen Tiger Lake+ — AV1 hardware decode; 12th Gen+ adds encode
AMD RX 6000 series+ — AV1 hardware decode and encode
Qualcomm Snapdragon 888+ — AV1 hardware decode
Apple Silicon (M1/M2/M3) — AV1 hardware decode
All major SoCs from 2021+ include AV1 decode acceleration

AV1 Encoding Complexity

AV1 encoding is significantly slower than H.264 or VP9:

At equivalent quality settings, AV1 encoding takes 5–30× longer than H.264
Real-time AV1 encoding requires hardware encoders (GPU/ASIC)
Software encoding (libaom) at high quality settings can take hours for a 1-hour video
SVT-AV1 encoder is faster with modest quality trade-off; widely deployed at Netflix

WebM vs. MP4: Web Video Comparison

Feature	WebM	MP4
Container	Matroska subset	ISOBMFF/QuickTime
Video codecs	VP8, VP9, AV1	H.264, H.265, AV1
Audio codecs	Vorbis, Opus	AAC, MP3, Opus
Royalty-free	Fully	H.264/H.265 require licences
Browser support	Chrome, Firefox, Edge (full); Safari (partial)	Universal
Streaming (HLS/DASH)	DASH; no HLS	Both DASH and HLS
Transparency/Alpha	VP8/VP9 support alpha channel in 4-channel mode	No alpha in H.264
File size at same quality	VP9: ~35% smaller than H.264; AV1: ~50% smaller	Baseline
Encoding speed	Slower (VP9); much slower (AV1)	Faster (H.264)

Alpha Channel in WebM

A significant WebM/VP9 advantage over MP4/H.264: transparent video. VP9 WebM supports a 4-channel encoding mode (YUV + Alpha) where an independent 8-bit alpha channel is compressed alongside the colour channels. This enables:

Video with transparency — logo animations, motion graphics overlaying any background
UI animations — complex animated UI elements that blend over content
Green screen replacement — keyed alpha channel instead of chroma key

MP4/H.264 has no alpha support; transparent video in web contexts almost exclusively uses WebM VP9 with alpha.

Browser Support Matrix (2025)

Browser	VP8	VP9	AV1	Notes
Chrome 4+	Yes	Yes	Yes	Full stack support
Firefox 4+	Yes	Yes	Yes	Full stack support
Edge 14+	Yes	Yes	Yes	Chromium-based
Opera 10.6+	Yes	Yes	Yes	Chromium-based
Safari 12.1+	No	Yes (macOS)	Yes (macOS M-series)	Partial
iOS Safari	No	Limited	Limited	WebM playback limited on iOS

Converting WebM Files

WebM → MP4: Re-encoding required (different codec families); H.264 from VP9 source is straightforward; quality-neutral at matching bitrates WebM → MKV: Nearly lossless container switch (same codec family); stream copy preserves VP8/VP9/AV1 + Vorbis/Opus without re-encoding MP4 → WebM: Re-encoding to VP9 or AV1; produces smaller files for web delivery; slower than H.264 encoding WebM → GIF: Animate WebM to GIF for maximum compatibility; significant size increase and quality reduction YouTube download: YouTube's WebM streams (VP9 + Opus) can be converted to MP4 H.264 + AAC for playback on devices without WebM support

Use Cases

Web Video Publishing: WebM (VP9 + Opus) reduces bandwidth by 35–40 % vs. H.264 MP4 while delivering equivalent quality. For high-traffic video websites, this translates to significant CDN cost savings.

Transparent Video Overlays: VP9 WebM with alpha channel is the standard for web video overlays — popup animations, product demonstrations, UI walkthroughs where the video element must be composited over page content.

YouTube Source Format: Creators uploading to YouTube benefit from understanding that YouTube transcodes all uploads to VP9 WebM internally. Higher-quality source uploads (4K, HDR) produce better VP9 outputs.

Open-Source Projects: Firefox extensions, web-based games, and open-source video players prefer WebM for its royalty-free status and community support.

Related conversions

Common video conversions that pair well with this guide:

Related conversions

Put what you just learned into practice — convert your files now in seconds, free and without registration.

Convert →

Convert →

Convert →

Convert →

Convert →

Convert →

Frequently Asked Questions

Yes. Chrome, Firefox, and Edge (all available on Windows) play WebM natively. VLC also plays WebM. Windows Media Player and the Windows built-in video player do not support WebM natively — install VLC or open WebM files in a supported browser instead.

Yes. Chrome, Firefox, e Edge (all disponível no Windows) reproduzir WebM natively. VLC also plays WebM. Windows Media Player e the Windows built-in video player do not support WebM natively — install VLC ou abrir WebM arquivos em um suportado browser instead.

Yes. Chrome, Firefox, und Edge (all verfügbar auf Windows) abspielen WebM natively. VLC also plays WebM. Windows Media Player und the Windows built-in video player do not support WebM natively — install VLC oder öffnen WebM Dateien in einem unterstützt browser instead.

Yes. Chrome, Firefox, y Edge (all disponible en Windows) reproducir WebM natively. VLC also plays WebM. Windows Media Player y the Windows built-in video player do not support WebM natively — install VLC o abrir WebM archivos en un soportado browser instead.

AV1 is the most efficient (royalty-free, ~30% smaller than H.265) but encoding is slow. H.265 (HEVC) saves ~30–50% over H.264 and is supported by every modern phone and desktop. H.264 remains the safest baseline for legacy compatibility. Rule of thumb: archives → AV1, daily use → H.265, broadest reach → H.264.

For bandwidth efficiency, yes: VP9 WebM is typically 35% smaller than H.264 MP4 at equivalent quality, and AV1 WebM is 50% smaller. However, MP4 has near-universal support on all devices and apps. Best practice for web: serve both formats, letting the browser select VP9/AV1 WebM with H.264 MP4 as fallback.

For bandwidth efficiency, yes: VP9 WebM is tipicamente 35% menor que H.264 MP4 at equivalent quality, e AV1 WebM is 50% smaller. Porém, MP4 has near-universal support on todos os dispositivos e apps. Best practice para web: serve both formatoos, letting o navegador select VP9/AV1 WebM com H.264 MP4 as fallback.

For bandwidth efficiency, yes: VP9 WebM is typically 35% kleiner als H.264 MP4 at equivalent quality, und AV1 WebM is 50% smaller. Jedoch, MP4 has near-universal support on alle Geräte und apps. Best practice für web: serve both Formate, letting der Browser select VP9/AV1 WebM mit H.264 MP4 as fallback.

For bandwidth efficiency, yes: VP9 WebM is typically 35% más pequeño que H.264 MP4 at equivalent quality, y AV1 WebM is 50% smaller. Sin embargo, MP4 has near-universal support on todos los dispositivos y apps. Best practice para web: serve both formatoos, letting el navegador select VP9/AV1 WebM con H.264 MP4 as fallback.

CRF (Constant Rate Factor) is the best default for offline files: ffmpeg picks the bitrate frame-by-frame to maintain perceived quality. Two-pass is only better when you must hit an exact final size (DVD targets). Constant bitrate is for streaming with a fixed channel. For "smallest at quality X" always use CRF.

Converting MP4 (H.264) to WebM (VP9 or AV1) always involves re-encoding, introducing some quality trade-off. At matching bitrates and quality settings (e.g., CRF mode), the difference is typically imperceptible. The resulting WebM file will be smaller than the MP4 at the same perceptual quality.

Converting MP4 (H.264) to WebM (VP9 ou AV1) always involves re-encoding, introducing some quality trade-off. At matching bitrates e quality settings (e.g., CRF mode), the difference is tipicamente imperceptible. The resulting WebM arquivo will be menor que the MP4 at the same perceptual quality.

Converting MP4 (H.264) to WebM (VP9 oder AV1) always involves re-encoding, introducing some quality trade-off. At matching Bitrates und quality settings (e.g., CRF mode), the difference is typically imperceptible. The resulting WebM Datei will be kleiner als the MP4 at the same perceptual quality.

Converting MP4 (H.264) to WebM (VP9 o AV1) always involves re-encoding, introducing some quality trade-off. At matching bitrates y quality settings (e.g., CRF mode), the difference is typically imperceptible. The resulting WebM archivo will be más pequeño que the MP4 at the same perceptual quality.

Common causes: (1) variable framerate source rendered as constant (use <code>-vsync vfr</code> to preserve VFR); (2) different audio sample rates not resampled (add <code>-ar 48000</code>); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run <code>ffprobe</code> on both source and output to compare timing.

Apple historically preferred H.264 and AAC (which they contributed to) over Google's VP8/VP9 codecs. Apple joined the Alliance for Open Media and added AV1 support in Safari 14. VP9 support was added in Safari 12.1 on macOS but remains limited on iOS/iPadOS. Full WebM support across all Apple platforms remains incomplete as of 2025.

Yes if you only change the container: <code>ffmpeg -i in.mkv -c copy out.mp4</code>. This remuxes the stream without re-encoding, takes seconds even for hours of footage. Limitations: codec must be supported by the target container (e.g. you cannot put H.264 in WebM, only VP8/VP9/AV1). To shrink size you must re-encode.