Hubbry Logo
WebMWebMMain
Open search
WebM
Community hub
WebM
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
WebM
WebM
WebM
View on Wikipedia
from Wikipedia

WebM
logo
Filename extension
.webm
Internet media type
video/webm,
audio/webm
Developed byInitially On2, Xiph, and Matroska; later Google
Initial releaseMay 18, 2010 (15 years ago) (2010-05-18)[1]
Latest release
v1.13.0[2]
January 31, 2023 (2 years ago) (2023-01-31)
Type of formatContainer format
Container forVP8/VP9/AV1 (video)
Vorbis/Opus (audio)
Extended fromLimited subset of Matroska
Open format?Yes[3]
Free format?Yes[4]
Websitewebmproject.org

WebM is an audiovisual media file format.[5] It is primarily intended to offer a royalty-free alternative to use in the HTML video and the HTML audio elements. It has a sister project, WebP, for images. The development of the format is sponsored by Google, and the corresponding software is distributed under a BSD license.

The WebM container is based on a profile of Matroska.[3][6][7] WebM initially supported VP8 video and Vorbis audio streams. In 2013, it was updated to accommodate VP9 video and Opus audio.[8] It also supports the AV1 codec.[9]

An example of a WebM video

Vendor support

[edit]

Software

[edit]

Native WebM support by Mozilla Firefox,[10][11] Opera,[12][13] and Google Chrome[14] was announced at the 2010 Google I/O conference. Internet Explorer 9 requires third-party WebM software.[15] In 2021, Apple released Safari 14.1 for macOS, which added native WebM support to the browser.[16] As of 2019, QuickTime does not natively support WebM,[17][18] but does with a suitable third-party plug-in.[19] In 2011, the Google WebM Project Team released plugins for Internet Explorer and Safari to allow playback of WebM files through the standard HTML5 <video> tag.[20] As of 9 June 2012, Internet Explorer 9 and later supported the plugin for Windows Vista and later.[21]

VLC media player,[22] MPlayer, K-Multimedia Player and JRiver Media Center have native support for playing WebM files.[23] FFmpeg can encode and decode VP8 videos when built with support for libvpx, the VP8/VP9 codec library of the WebM project, as well as mux/demux WebM-compliant files.[24] On July 23, 2010 Fiona Glaser, Ronald Bultje, and David Conrad of the FFmpeg team announced the ffvp8 decoder. Their testing found that ffvp8 was faster than Google's own libvpx decoder.[25][26] MKVToolNix, the popular Matroska creation tools, implemented support for multiplexing/demultiplexing WebM-compliant files out of the box.[27] Haali Media Splitter also announced support for muxing/demuxing of WebM.[27] Since version 1.4.9, the LiVES video editor has support for realtime decoding and for encoding to WebM format using ffmpeg libraries.

MPC-HC since build SVN 2071 supports WebM playback with internal VP8 decoder based on FFmpeg's code.[25][28] The full decoding support for WebM is available in MPC-HC since version 1.4.2499.0.[29]

Android is WebM-enabled since version 2.3 Gingerbread,[30] which was first made available via the Nexus S smartphone and streamable since Android 4.0 Ice Cream Sandwich.[31]

The Microsoft Edge browser supports WebM since April 2016.[32]

On July 30, 2019, Blender 2.80 was released with WebM support.[33]

iOS did not natively play WebM until 2021,[34] when support for WebM was added in Safari 15 as part of iOS 15.[35]

The Sony PlayStation 5 supports capturing 1080p and 2160p footage in WebM format.[36]

ChromeOS screen recordings are saved as WebM files.[37]

Hardware

[edit]

WebM Project licenses VP8 hardware accelerators (RTL IP) to semiconductor companies for 1080p encoding and decoding at zero cost.[38] AMD, ARM and Broadcom have announced support for hardware acceleration of the WebM format.[39][40] Intel is also considering hardware-based acceleration for WebM in its Atom-based TV chips if the format gains popularity.[41] Qualcomm and Texas Instruments have announced support,[42][43] with native support coming to the TI OMAP processor.[44] Chips&Media have announced a fully hardware decoder for VP8 that can decode full HD resolution (1080p) VP8 streams at 60 frames per second.[45]

Nvidia is supporting VP8 and provides both hardware decoding and encoding in the Tegra 4 and Tegra 4i SoCs.[46] Nvidia announced 3D video support for WebM through HTML5 and their Nvidia 3D Vision technology.[47][48][49]

On January 7, 2011, Rockchip released the world's first chip to host a full hardware implementation of 1080p VP8 decoding. The video acceleration in the RK29xx chip is handled by the WebM Project's G-Series 1 hardware decoder IP.[50]

In June 2011, ZiiLABS demonstrated their 1080p VP8 decoder implementation running on the ZMS-20 processor. The chip's programmable media processing array is used to provide the VP8 acceleration.[51]

ST-Ericsson and Huawei also had hardware implementations in their computer chips.[52]

Streaming capabilities

[edit]

Since 2017, Icecast — a streaming media server traditionally used for audio streaming — has supported live video streaming using the WebM format (VP8/VP9/AV1 video codecs with Vorbis/Opus audio codecs).[53] This enables broadcasting of high-quality, royalty-free, open-standard video streams that can be played directly in browsers without requiring proprietary plugins or players.

Archived streams and server listings demonstrate WebM's viability for live streaming over Icecast, including examples of 1080p VP9 streams. Current implementations include live streams accessible at https://rdst.win:59000/dos.webm,[54] with server status visible at https://rdst.win:59000.

Streaming examples and resources

[edit]

Licensing

[edit]

The original WebM license terminated both patent grants and copyright redistribution terms if a patent infringement lawsuit was filed, causing concerns around GPL compatibility. In response to those concerns, the WebM Project decoupled the patent grant from the copyright grant, offering the code under a standard BSD license and patents under a separate grant.[55] The Free Software Foundation, which maintains The Free Software Definition, has given its endorsement for WebM and VP8[56] and considers the software's license to be compatible with the GNU General Public License.[57][58] On January 19, 2011, the Free Software Foundation announced its official support for the WebM project.[59] In February 2011, Microsoft's Vice President of Internet Explorer called upon Google to provide indemnification against patent suits.[60]

Although Google has irrevocably released all of its patents on VP8 as a royalty-free format,[61] the MPEG LA, licensors of the H.264 patent pool, have expressed interest in creating a patent pool for VP8.[62][63] Conversely, other researchers cite evidence that On2 made a particular effort to avoid any MPEG LA patents.[64] As a result of the threat, the United States Department of Justice (DOJ) started an investigation in March 2011 into the MPEG LA for its role in possibly attempting to stifle competition.[65][66] In March 2013, MPEG LA announced that it had reached an agreement with Google to license patents that "may be essential" for the implementation of the VP8 codec, and give Google the right to sub-license these patents to any third-party user of VP8 or VP9.[67][68]

In March 2013, Nokia filed an objection to the Internet Engineering Task Force concerning Google's proposal for the VP8 codec to be a core part of WebM, saying it holds essential patents to VP8's implementation.[69] Nokia listed 64 patents and 22 pending applications, adding it was not prepared to license any of them for VP8.[70] On August 5, 2013, a court in Mannheim, Germany, ruled that VP8 does not infringe a patent owned and asserted by Nokia.[71]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

WebM

View on Grokipedia
from Grokipedia
WebM is an open, designed for efficient web-based video and audio delivery, utilizing a subset of the (.MKV) structure and supporting video codecs such as , , and with audio codecs including and Opus. Developed by and announced in May 2010 at the conference following the acquisition of On2 Technologies, WebM emerged as an open-source alternative to proprietary formats like H.264, aiming to enable HTML5 video embedding across browsers without licensing fees. The format has achieved broad native support in major web browsers including Chrome, , and , facilitating its use in streaming services, though adoption has been tempered by ongoing debates over compression efficiency compared to H.264 and potential patent risks asserted by groups like . Despite these challenges, WebM's evolution to include advanced codecs like has positioned it as a key player in promoting open media standards, with increasingly available in modern devices.

History

Origins and announcement

Google acquired On2 Technologies, Inc., a developer of video compression technologies including the codec, to advance its efforts in creating an open, royalty-free video format for the web. The acquisition was initially announced on August 5, 2009, for approximately $106 million, with the agreement later amended in January 2010 to account for changes in On2's stock value. The deal closed on February 19, 2010, for a final amount of $124.6 million, providing with full rights to VP8, which served as the core for the forthcoming WebM format. On May 19, 2010, during the keynote at the Google I/O developer conference, Google publicly announced the WebM Project, introducing WebM as a new open media format designed to deliver high-quality video to the web without licensing fees. The initiative, backed by collaborators including Mozilla, Opera, and Adobe, positioned WebM as a royalty-free alternative to proprietary solutions like H.264, which required payments to patent pools, and Adobe Flash, which dominated online video playback but lacked native HTML5 integration. WebM utilized a profile of the Matroska container format, pairing the open-sourced VP8 video codec with the Vorbis audio codec, and released the reference implementation under a BSD license to encourage broad adoption. This launch aimed to standardize open video in HTML5

Early development and codec evolution

Google released the VP8 video codec specification on May 19, 2010, during its conference, providing an open-source implementation under a BSD-like license to enable royalty-free web video compression as part of the initial WebM framework. This followed Google's acquisition of in February 2010, which had developed VP8 as a successor to its earlier proprietary codecs, aiming to address limitations in compression efficiency and licensing costs for online media. To enhance compression performance over , introduced the on June 17, 2013, offering up to 50% better efficiency for high-resolution video while maintaining royalty-free status and compatibility with the WebM container. incorporated advancements such as larger block sizes, improved , and loop filtering, driven by 's analysis of web streaming demands for reduced bandwidth usage without quality loss. Audio capabilities evolved with the integration of the Opus into WebM in 2012, following its standardization as RFC 6716 by the IETF, which provided superior quality at low bitrates compared to prior options like , supporting encoding and hybrid speech/music modes for versatile web applications. The formation of the (AOMedia) on September 1, 2015, by and partners including , , and marked a collaborative shift, culminating in the codec's release in March 2018, which extended WebM support for next-generation compression achieving 30% gains over through techniques like extended partitioning and advanced . Google's leadership in these iterations emphasized scalable, open-source progression to counter proprietary standards, with ongoing refinements in the 2020s focusing on encoding speed and hardware interoperability for broader web deployment.

Technical Overview

Container structure

WebM utilizes a that is a subset of the multimedia container, employing the Extensible Binary Meta Language (EBML) to enable a hierarchical, extensible binary structure supporting multiple synchronized tracks for elements such as video, audio, and . This EBML-based design allows for forward-compatible extensions without breaking existing , facilitating the organization of metadata and media data in a tree-like format optimized for efficient and delivery in web environments. At the file's core lies the Segment element, functioning as the primary root container that encapsulates key structural components: Tracks define the characteristics and mappings of individual media streams, including codec identifiers restricted in WebM to , , or for video and or Opus for audio; Clusters group time-contiguous blocks of media data from multiple tracks to support progressive downloading and playback; and Cues provide an index of Cluster timestamps and positions for rapid seeking without full file traversal. Additional elements like Info store global file metadata such as duration and timestamps, while SeekHead (or MetaSeek) offers quick offsets to these components, collectively enabling low-latency and streaming suitability over protocols like HTTP. WebM files are identified by the .webm extension and served with the (or audio/webm for audio-only variants), with the EBML DocType explicitly set to "webm" to signal compliance and ensure interoperability in

Supported media codecs

The WebM container format supports VP8 as its baseline video codec, which was developed by and released on May 19, 2010, as part of the initial WebM specification to provide royalty-free video compression based on open specifications. VP8 enables efficient encoding for web delivery, focusing on block-based and intra-frame without reliance on proprietary patents. In December 2013, VP9 was added as a higher-efficiency successor to VP8, offering improved compression ratios—up to 50% better than VP8 for similar quality—through advancements like larger block sizes up to 64x64 pixels, enhanced motion vector , and loop filtering refinements, while maintaining status under the WebM Project's open-source framework. AV1, standardized by the in March 2018, extends WebM compatibility as a next-generation , achieving further compression gains of 30% over via techniques such as extended partitioning, advanced transforms, and synthesis, with all components designed for patent-free implementation to promote widespread adoption in open web media. WebM strictly excludes proprietary video codecs like H.264 or HEVC, adhering to the WebM Project's mandate for open, verifiable specifications to ensure interoperability without licensing encumbrances. For audio, WebM initially incorporated the codec, an open-source lossy format from the finalized in 2000, which uses and perceptual coding for high-quality stereo and multichannel audio at bitrates from 45 to 500 kbps. In 2012, Opus was integrated as a versatile addition, supporting both speech and music with low-latency encoding (as low as 2.5 ms frames), control, and hybrid SILK-CELT modes for superior performance across 6 to 510 kbps, outperforming in real-time applications while remaining fully royalty-free. Like video components, WebM audio is limited to these open codecs to preserve the format's commitment to unencumbered, empirically validated compression standards.

Encoding, decoding, and features

WebM encoding primarily utilizes the library for and video codecs, which implements parameters for temporal scalability—allowing frame sequences to be structured in layers for bandwidth-adaptive decoding—and error resilience modes that mitigate dependencies on prior frames and contexts to recover from transmission s. For video, encoding employs libaom, extending these capabilities with enhanced compression efficiency while maintaining compatibility within the WebM container. Audio encoding supports Opus or via dedicated libraries like libopus, integrated into tools such as FFmpeg for muxing into the Matroska-based WebM format. Decoding processes in web environments rely on browser implementations of the (MSE) API, which enables JavaScript-driven assembly of media segments for <video> elements, supporting progressive playback of WebM streams with , , or payloads. This pipeline appends encoded buffers to SourceBuffer objects, facilitating low-latency decoding without full file downloads, though it requires codec-specific demuxing to handle interleaved video and audio tracks. Distinct features include alpha channel support in profiles (denoted as VP9a), introduced in , which encodes transparency alongside luma and chroma, enabling for overlays and animations without separate matte tracks. and also provide lossless modes, invoked via encoder flags such as -lossless 1 in libvpx-vp9, preserving exactly at the cost of larger file sizes compared to lossy quantization. For streaming, spatial and temporal layering—configurable in / via single-layer spatial setups with multi-frame temporal structures—supports scalable video coding, where decoders can selectively render base or enhancement layers to match available bitrate, optimizing for variable network conditions in adaptive protocols. These mechanisms enhance error resilience by isolating layer dependencies, reducing propagation of artifacts from dropped packets.

Licensing and Intellectual Property

Royalty-free licensing model

The royalty-free licensing model of WebM relies on permissive open-source licenses for its core components, including the and video codecs provided via the reference library under a BSD license, which permits unrestricted use, modification, redistribution, and commercial implementation without royalty fees. Similarly, support for the video codec in WebM aligns with its royalty-free structure, drawing from the Alliance for Open Media's specifications licensed under terms like Apache 2.0 and BSD that avoid mandatory payments. Audio codecs such as and Opus follow comparable open licenses, ensuring the overall format remains unencumbered for developers and users. Initiated by through the WebM Project in May 2010, this model emphasizes no direct royalty demands from the project stewards, contrasting sharply with royalty-bearing formats like H.264, which require licensing through patent pools such as . The approach facilitates seamless integration into <video> elements across browsers, promoting widespread adoption in web applications without financial barriers tied to codec usage. This licensing framework has enabled contributions from multiple stakeholders while maintaining Google's stewardship, prioritizing over proprietary controls.

Patent landscape and encumbrances

In March 2013, Google entered into a licensing agreement with MPEG LA, the administrator of the H.264/AVC patent pool, effectively conceding that its VP8 video codec—core to the WebM format—infringed on certain H.264 patents held by pool members. The deal granted Google rights to sublicense VP8 implementations and related techniques in the successor VP9 codec, clearing potential infringement claims from MPEG LA participants while extending coverage to VP9 but not future codecs. This arrangement imposed indirect financial obligations on Google, undermining the absolute royalty-free assertion for VP8/WebM adopters reliant on Google's patent grants. Earlier, in February 2011, MPEG LA solicited submissions of essential patents for to evaluate forming a royalty-bearing pool, prompting scrutiny of potential encumbrances shortly after Google's open-sourcing of WebM. Despite identifying claimed essential patents, MPEG LA did not establish a VP8-specific pool or impose royalties, averting immediate demands but highlighting to third-party assertions beyond Google's control. For , the Sisvel Video Coding Licensing Platform launched patent pools in March 2019, aggregating essential patents from non-Alliance for Open Media (AOM) members and asserting royalties on and implementations despite AOM's royalty-free pledges limited to contributor patents. Sisvel's pools charge rates such as €0.24 per -enabled display device and €0.08 for non-display units, with over 60 licensees by 2023, demonstrating practical enforcement against the "" model. These pools target finished products practicing /, exposing implementers to fees from patents not covered by Google's or AOM's grants. Ongoing litigation underscores persistent risks, with U.S. courts seeing at least seven -related cases and 56 mentioning by 2023, including assertions by holders like against streaming services for infringements potentially extending to / technologies. Such disputes reveal hidden costs to WebM's openness, as non-participant patents enable royalty demands or injunctions, compelling defensive licensing even under purportedly unencumbered standards.

Adoption and Implementation

Browser and software support

Google Chrome has provided native support for WebM playback since version 6, released in September 2010, enabling direct rendering of -encoded videos within the browser. Mozilla Firefox introduced native WebM support with version 4.0 in March 2011, including both video and audio decoding. Opera browsers have offered native compatibility since version 11.6 in December 2011, aligning with the format's emphasis on open web standards. Microsoft Edge achieved full native support for WebM starting with version 79 in 2020, following its transition to the engine, which resolved earlier partial or plugin-dependent playback. Apple Safari maintains limited native support, historically requiring extensions or third-party codecs for content, though versions from Safari 16.4 onward (released March 2023) demonstrate improved handling of VP9-encoded WebM files amid broader adoption of codecs like AV1. In multimedia libraries, FFmpeg has included encoding and decoding capabilities for WebM containers with VP8 since version 0.6, released in July 2010, facilitating integration across developer tools and applications. VLC media player supports WebM playback natively, with reliable handling of the format available in versions from the early onward, leveraging its built-in libraries without additional packs. By 2025, open-source ecosystems have achieved near-universal software compatibility for WebM through libraries such as and , enabling seamless encoding, decoding, and playback in diverse applications from video editors to command-line tools. This widespread integration stems from the format's model, reducing barriers in cross-platform development.

Hardware acceleration

NVIDIA's NVDEC hardware decoder has supported decoding since the Kepler architecture in 2012 and decoding since the Pascal architecture in 2016, with decode added in the architecture from 2020 onward. GPUs provide for decoding via Video Core Next (VCN) engines starting with the architecture in 2017, extending to decode in architectures from 2020. enables hardware decoding from the Skylake generation in 2015 and decoding from in 2020, with decode supported earlier in Haswell processors from 2013. On mobile platforms, Android devices have offered native hardware decoding for WebM's codec since 2011, facilitated by IP cores like Google's Anthill project and integrations in chipsets such as 4 from 2013. and hardware decode followed in later SoCs, with broad adoption in and Dimensity series by the late 2010s. In contrast, iOS hardware acceleration for WebM codecs has been limited; and rely primarily on software or third-party implementations, though Apple's A17 Pro chip introduced hardware decoding in September 2023 for models. Hardware encoding for WebM codecs remains less widespread than decoding, primarily available in professional-grade GPUs and integrated solutions by the mid-2020s. NVIDIA NVENC supports encoding from Turing GPUs in 2018 and from in 2022, while Intel Quick Sync added encode with Ice Lake in 2019 and encode in from 2023; AMD's architecture introduced encoding in 2022. These capabilities enhance efficiency for high-volume encoding workflows, though CPU-based software encoding persists for broader compatibility.

Usage in streaming and web applications

WebM containers, typically employing or codecs, integrate with protocols such as MPEG-DASH, enabling segmented delivery of multiple quality variants over HTTP to adjust dynamically to viewer bandwidth. This process relies on (MSE) in supporting browsers, which append WebM segments to the <video> element, facilitating seamless quality switches without full video reloads. For , tools like FFmpeg can transcode inputs into WebM segments compliant with DASH manifests, as demonstrated in server configurations from providers like . Although (HLS) predominantly utilizes fragmented MP4 segments per Apple's specification, WebM can support analogous adaptive delivery via MSE for cross-protocol compatibility in web applications, though remains the preferred standard for open formats due to broader codec flexibility. implemented WebM for streaming starting in 2010, shortly after the format's release, to enable royalty-free HTML5 playback and reduce bandwidth demands through VP8's intra-frame compression efficiency, which approximates H.264 performance while avoiding licensing fees. This adoption allowed progressive rollout of HD content without proprietary plugins, contributing to lower infrastructure costs for large-scale distribution. In real-time applications, WebM's codecs underpin WebRTC implementations for low-latency video calls and conferencing, where VP8 provides sub-second encoding/decoding cycles optimized for peer-to-peer transmission over UDP, minimizing buffering delays to under 500 milliseconds in typical setups. Developers leverage WebRTC's native support for WebM payloads in RTP streams, enabling browser-based video telephony without intermediaries, as seen in open-source libraries handling real-time VP8 negotiation via SDP. The WebM Project offers test streams and DASH live streaming guides on its resources, including GitHub repositories for sample WebM muxing and playback validation in low-latency scenarios.

Comparisons with Alternatives

Against proprietary formats like H.264

VP9, a core in the WebM container, provides superior compression efficiency compared to the H.264 (AVC) standard. According to benchmarks from 2013 to 2016, VP9 achieves approximately 50% bitrate savings relative to H.264 at equivalent perceptual quality levels, enabling smaller file sizes or reduced bandwidth usage for the same video . This advantage stems from advanced techniques such as larger block sizes up to 64x64 and improved , though it incurs substantially higher computational demands; early VP9 encoders were over 100 times slower than mature H.264 implementations like x264. AV1, an advanced supported in WebM, further extends these gains, delivering average bitrate reductions of 50% or more against H.264 in practical streaming scenarios, as measured by BD-rate metrics in 2018 evaluations across diverse content types. While AV1's decode complexity initially posed barriers—requiring up to several times more processing power than H.264—hardware optimizations in GPUs and dedicated silicon from the early onward have narrowed this gap, facilitating real-time playback in browsers and devices. These efficiency improvements position WebM as a cost-effective alternative for bandwidth-constrained applications, circumventing H.264's royalty obligations, which impose fees on endpoints exceeding certain volumes under licensing. Nonetheless, H.264's entrenched hardware ubiquity and software ecosystem—built over two decades—initially perpetuated its dominance, delaying WebM's penetration despite the open model's long-term economic incentives.

Relation to successor technologies like

The video codec, developed as a successor to , utilizes WebM as its primary container for web-based deployment and streaming applications, thereby extending the WebM format's utility without supplanting it. The (AOMedia), comprising founding members such as , , , , , , and NVIDIA, initiated AV1 development in 2015 to overcome VP9's compression inefficiencies and encoding complexity. The AV1 specification achieved bitstream freeze and public release of version 1.0 on March 28, 2018, enabling royalty-free implementation with WebM encapsulation for seamless integration into video elements. AV1 delivers approximately 30% better compression efficiency than at equivalent quality levels, as targeted by AOMedia's design goals and validated in early benchmarks, which facilitates lower bitrate streaming while preserving WebM's matroska-derived structure for metadata and with audio codecs like Opus. This advancement addresses 's limitations in handling high-resolution content and complex motion, with supporting up to 8K resolutions and progressive enhancements in later profiles. WebM's role persists as evolves, including extensions like the profile introduced in subsequent specifications for 10- and 12-bit color depths and higher frame rates, optimizing it for web-scale distribution. Ongoing AOMedia efforts, such as AV1's integration into browser APIs and hardware decode pipelines since the early 2020s, reinforce WebM's position by prioritizing low-latency, over alternative containers like MP4, which require separate codec signaling. This continuity ensures with existing WebM tooling while accommodating AV1's scalable video coding features for future ultra-high-definition web video.

Criticisms and Limitations

Performance and quality trade-offs

WebM's core codec demonstrated compression performance similar to H.264 in peak scenarios but consistently lagged in encoding speed by factors of 5 to 25 times using versus implementations, hindering real-time applications and necessitating elevated CPU demands in software-only environments prior to widespread hardware support. advanced efficiency, delivering roughly 50% bitrate reduction over H.264 for equivalent perceptual quality in benchmarks, which supports bandwidth-constrained web delivery, yet its encoding complexity resulted in 10 to 20 times longer processing durations compared to H.264, often rendering it impractical for low-latency workflows without optimized presets or accelerators. AV1 further enhances WebM's capabilities with 20-30% superior compression to HEVC, evidenced by deployments achieving proportional bandwidth reductions for high-volume streams, but incurs encoding times 10 to 20 times exceeding H.265 at comparable quality levels, amplifying resource requirements for production encoding despite ongoing optimizations in tools like SVT-AV1. At low bitrates prevalent in adaptive web streaming, and reduce common artifacts such as blocking via refined block partitioning and deblocking filters, yielding perceptually superior results to H.264 equivalents; however, under extreme constraints like 512 kbps, residual issues including edge ringing and motion-induced blurring persist in high-detail content, though less pronounced than in earlier encodes.

Compatibility and ecosystem challenges

WebM's adoption has been hampered by uneven browser support, particularly in Apple's ecosystem. Safari on macOS and provided only partial or no native support for WebM until Safari 14.1 in 2021, requiring (version 11.3) or later for full playback of VP9-encoded WebM files, while earlier versions like Safari 12–3.2 lacked it entirely. On , WebM playback was unavailable in Safari prior to , forcing developers to transcode to MP4/H.264 or use third-party apps for compatibility on iPhones and iPads. This delay stemmed from Apple's preference for proprietary-optimized formats like H.264, which prioritized hardware efficiency over open alternatives. Hardware encoding support for , the primary in WebM, lagged significantly, relying predominantly on software encoding until the late 2010s and early 2020s. While hardware decoding became widespread by the mid-2010s in GPUs from , , and , encoding —essential for efficient professional workflows—remained sparse, with full consumer-grade implementations not scaling until platforms like NVIDIA Turing () and subsequent generations. This limitation increased encoding times dramatically compared to H.264, often by factors of 5–10x on CPU-only setups, deterring adoption in time-sensitive production environments. The WebM ecosystem exhibits fragmentation, thriving in open-web browsers like Chrome and Firefox but faltering on legacy devices and closed platforms. Older hardware, including pre-2015 smartphones and embedded systems, often lacks VP9 decoders, necessitating fallbacks to VP8 or transcoding, which complicates deployment. In contrast to H.264's ubiquitous hardware optimization, WebM's decoder implementations historically demanded larger runtime footprints—evidenced by early benchmarks showing 38% CPU usage for 720p WebM playback versus 24% for H.264 on accelerated hardware—offsetting file size efficiencies with higher initial integration costs. These factors have perpetuated a bifurcated landscape, where WebM excels in royalty-free web streaming but requires hybrid codec strategies for broad device compatibility. In February 2011, , the administrator of patent pools for standards including H.264, issued a public call for patent submissions related to Google's video codec underlying WebM, signaling an intent to evaluate essential s and potentially form a royalty-bearing pool. This move followed Google's May 2010 release of as a royalty-free alternative, amid concerns from patent holders that open codecs could undermine revenue from licensed technologies. By August 2011, identified patents from 12 companies as potentially essential to implementations, heightening threats of litigation or licensing fees that could encumber WebM adoption. Google rebuffed these efforts through a cross-licensing agreement announced in 2013, under which it granted access to its VP8 s in exchange for reciprocal licenses from implementers holding related s, while securing commitments from MPEG LA and 11 other holders to forgo royalties on VP8-essential technologies. This settlement, reached on March 7, 2013, explicitly abandoned MPEG LA's VP8 pool initiative and affirmed perpetual use of the identified s, neutralizing the primary competitive threat. Critics have argued that Google's centralized control over and WebM development, as a single-entity proponent rather than a multi-vendor , risks stifling broader industry competition compared to collaborative pools like HEVC (H.265), which involve diverse licensors to balance innovation and licensing. Proponents of patent-pool models contend that Google's approach favors its dominance—evident in YouTube's heavy WebM integration—potentially discouraging neutral standards bodies and favoring leverage over shared revenue mechanisms. Such resistance from established patent aggregators underscores ongoing tensions between open-source acceleration and incumbent revenue strategies, though no formal antitrust actions directly targeted WebM's rollout.

References

  1. https://www.webmproject.org/about/
  2. https://www.webmproject.org/docs/container/
  3. https://blog.chromium.org/2020/05/celebrating-10-years-of-webm-and-webrtc.html
  4. https://cloudinary.com/guides/video-formats/webm-format-what-you-should-know
  5. https://www.loc.gov/preservation/digital/formats/fdd/fdd000518.shtml
  6. https://arstechnica.com/information-technology/2010/05/google-support-aside-webm-carries-patent-risks-from-mpeg-la/
  7. http://googlepress.blogspot.com/2009/08/google-to-acquire-on2-technologies_05.html
  8. https://www.prnewswire.com/news-releases/google-and-on2-agree-to-amend-merger-agreement-80893477.html
  9. https://www.reuters.com/article/idUS3097266726/
  10. https://www.sandiegouniontribune.com/2010/02/19/google-finishes-125m-buy-of-on2-technologies/
  11. https://developers.googleblog.com/en/google-chrome-at-google-io-2010/
  12. https://www.streamingmedia.com/Articles/News/Online-Video-News/Google-Open-Sources-VP8--67265.aspx
  13. https://sg.finance.yahoo.com/news/2010-05-19-google-launches-open-webm-web-video-format-based-on-vp8.html?bcmt=1
  14. https://www.cnet.com/culture/google-tries-freeing-web-video-with-webm/
  15. https://www.webmproject.org/vp9/
  16. https://aomedia.org/about/story/
  17. https://permadi.com/2010/06/webm-file-structure/
  18. https://www.loc.gov/preservation/digital/formats/fdd/fdd000342.shtml
  19. https://www.matroska.org/technical/diagram.html
  20. https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/MIME_types/Common_types
  21. https://www.webmproject.org/about/faq/
  22. https://groups.google.com/a/webmproject.org/g/webm-discuss/c/-i1BOfIe8QI
  23. https://www.webmproject.org/docs/encoder-parameters/
  24. https://wiki.webmproject.org/ffmpeg/vp9-encoding-guide
  25. https://www.w3.org/TR/media-source-2/
  26. https://axel.isouard.fr/blog/2016/05/24/streaming-webm-video-over-html5-with-media-source
  27. https://developer.mozilla.org/en-US/docs/Web/API/Media_Source_Extensions_API
  28. https://wiki.webmproject.org/alpha-channel
  29. https://stackoverflow.com/questions/34856236/convert-mov-with-alpha-to-vp9-webm-with-alpha-using-ffmpeg
  30. https://imagekit.io/blog/vp8-vs-vp9/
  31. https://trac.ffmpeg.org/wiki/Encode/VP9
  32. https://bitmovin.com/blog/vp9-codec-status-quo/
  33. https://appleinsider.com/articles/13/03/07/google-admits-its-vp8webm-codec-infringes-mpeg-h264-patents
  34. https://www.cnet.com/tech/services-and-software/google-reaches-deal-with-mpeg-la-over-its-vp8-video-codec/
  35. https://www.streamingmedia.com/Articles/News/Online-Video-News/MPEG-LA-and-Google-Settle-What-Does-it-Mean-88324.aspx
  36. https://techcrunch.com/2013/03/07/google-and-mpeg-la-sign-licensing-agreement-covering-googles-vp8-video-codec-clearing-the-way-for-wider-adoption/
  37. http://www.fosspatents.com/2011/02/mpeg-la-puts-googles-webm-video-format.html
  38. https://www.wired.com/2011/02/mpeg-la-starts-the-search-for-vp8-patents/
  39. https://www.theguardian.com/technology/blog/2011/feb/15/mpeg-video-coding-standard
  40. https://www.iam-media.com/article/sisvel-launches-new-video-licensing-platform
  41. https://streaminglearningcenter.com/codecs/sisvel-announces-patent-pools-for-vp9-and-av1.html
  42. https://www.sisvel.com/licensing-programmes/audio-and-video-coding-decoding/video-coding-platform-av1/
  43. https://www.sisvel.com/insights/aoms-av1-patents-arent-free-youre-just-not-paying-directly-for-them/
  44. https://www.iam-media.com/article/recent-high-profile-av1-and-vp9-assertions-are-not-the-first-in-us-courts
  45. https://opensource.stackexchange.com/questions/15425/sisvel-and-the-patent-grant-of-vp8-vp9
  46. https://www.lambdatest.com/web-technologies/webm
  47. https://www.lambdatest.com/web-technologies/webm-safari
  48. https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Video_codecs
  49. https://www.afterdawn.com/guides/archive/how_to_play_webm_files_page_3.cfm
  50. https://images.videolan.org/vlc/
  51. https://ffmpeg.org/ffmpeg-formats.html
  52. https://www.webmproject.org/
  53. https://developer.nvidia.com/video-codec-sdk
  54. https://wiki.archlinux.org/title/Hardware_video_acceleration
  55. https://www.intel.com/content/www/us/en/docs/onevpl/developer-reference-media-intel-hardware/1-1/overview.html
  56. https://www.cnet.com/culture/google-releases-anthill-to-bake-vp8-into-hardware/
  57. https://www.flatpanelshd.com/news.php?subaction=showfull&id=1694598394
  58. https://www.reddit.com/r/ffmpeg/comments/1e85k43/vp9_encoding_on_gpu/
  59. https://www.red5.net/blog/av1-vs-vp9-vs-vp8-comparison-for-live-streaming/
  60. https://developer.mozilla.org/en-US/docs/Web/API/Media_Source_Extensions_API/DASH_Adaptive_Streaming
  61. https://wiki.webmproject.org/adaptive-streaming/instructions-to-playback-adaptive-webm-using-dash
  62. https://www.wowza.com/docs/how-to-transcode-live-streams-to-webm-for-mpeg-dash-playback
  63. https://github.com/shaka-project/shaka-player
  64. https://www.videoexpertsgroup.com/glossary/webm
  65. https://groups.google.com/a/webmproject.org/g/webm-discuss/c/PxQwjCc0-HY
  66. https://www.nanocosmos.net/blog/webrtc-latency/
  67. https://github.com/webmproject/webmlive
  68. https://wiki.webmproject.org/adaptive-streaming/instructions-to-do-webm-live-streaming-via-dash
  69. https://news.ycombinator.com/item?id=10888898
  70. https://blogs.gnome.org/rbultje/2015/09/28/vp9-encodingdecoding-performance-vs-hevch-264/
  71. https://iphome.hhi.de/marpe/download/Performance_HEVC_VP9_X264_PCS_2013_preprint.pdf
  72. https://engineering.fb.com/2018/04/10/video-engineering/av1-beats-x264-and-libvpx-vp9-in-practical-use-case/
  73. https://developer.nvidia.com/blog/improving-video-quality-and-performance-with-av1-and-nvidia-ada-lovelace-architecture/
  74. https://imagekit.io/blog/vp9-vs-h264/
  75. https://bunny.net/academy/streaming/what-is-av1-encoding-and-vp9-codec/
  76. https://aomedia.org/
  77. https://aomedia.org/about/members/
  78. https://www.wowza.com/blog/av1-codec-aomedia-video-1-explained
  79. https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/codecs_parameter
  80. http://compression.ru/video/codec_comparison/h264_2010/vp8_vs_h264.html
  81. https://www.red5.net/blog/h264-vs-h265-vp9/
  82. https://netflixtechblog.com/performance-comparison-of-video-coding-standards-an-adaptive-streaming-perspective-d45d0183ca95
  83. https://bitmovin.com/blog/av1-encoding-guide/
  84. https://www.linkedin.com/pulse/hevc-vs-av1-vvc-we-end-block-based-era-jan-devos-1htke
  85. https://imagekit.io/blog/av1-vs-vp9/
  86. https://groups.google.com/a/webmproject.org/g/codec-devel/c/CD921b8brEk/m/EI22UrlQCQAJ
  87. https://caniuse.com/#feat=webm
  88. https://www.videoproc.com/resource/how-to-play-webm-on-iphone.htm
  89. https://news.ycombinator.com/item?id=16319651
  90. https://iternumdigital.com/webm-videos-advantages-and-disadvantages-for-your-website/
  91. https://www.streamingmediaglobal.com/Articles/Editorial/Featured-Articles/WebM-vs.-H.264-A-Closer-Look-68594.aspx
  92. https://www.streamingmedia.com/Articles/Editorial/Featured-Articles/Googles-WebM-to-Face-Patent-Challenge-73786.aspx
  93. https://www.wired.com/2011/08/mpeg-la-12-companies-own-patents-essential-to-googles-vp8-codec/
  94. https://www.webmproject.org/cross-license/vp8/agreement/
  95. https://arstechnica.com/information-technology/2013/03/google-mpeg-la-agree-to-royalty-free-terms-for-vp8-video-codec/
  96. https://blog.patentology.com.au/2013/05/there-aint-no-such-thing-as-free-video.html
  97. https://www.theguardian.com/technology/blog/2011/jan/17/google-webm-vp8-video-html5-h264-winners-losers
  98. https://www.zdnet.com/article/google-and-mpeg-la-settle-long-running-vp8h-264-patent-dispute/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.