The Mozilla Graphics Team announces the upcoming release of WebGPU on Windows in Firefox 141, marking a significant milestone in providing web content with a modern, high-performance interface to graphics processors. WebGPU aims to elevate the capabilities of web-based games, visualizations, and local computation. Developed under W3C standards with Mozilla's active participation since 2017, the implementation is built upon WGPU, an open-source Rust crate that offers a unified interface to low-level graphics APIs. While the initial rollout targets Windows, support for Mac, Linux, and Android is planned for subsequent months. The team acknowledges ongoing efforts to enhance performance, mitigate latency, and integrate features like importExternalTexture, inviting users to test the new API and report any issues.
Summarizing the Mozilla Gfx Team Blog Post: Shipping WebGPU on Windows in Firefox 141
WebGPU Launch & Vision: Firefox 141 will bring WebGPU to Windows, offering web content a modern, high-performance interface to GPUs. This is anticipated to significantly enhance games, visualizations, and local computation directly within the browser.
Standards & Resources: WebGPU is defined by W3C standards (WebGPU and WGSL), with Mozilla involved since 2017. Users can access tutorials at webgpufundamentals.org, explore WebGPU Samples, and refer to documentation on MDN.
Platform Rollout Strategy: Windows is the initial launch platform due to its large user base. Plans are in place to extend WebGPU support to Mac, Linux, and Android in the coming months, building on its existing availability in Firefox Nightly (except for Android).
Core Technology: WGPU: Firefox's WebGPU implementation is founded on WGPU, an independent, open-source Rust crate. WGPU provides a portable interface to underlying graphics APIs such as Direct3D 12, Metal, and Vulkan, with Mozilla being a key contributor to its development.
Ongoing Development & Known Issues: While WebGPU in Firefox 141 is functional for many use cases, further work is underway to improve performance and full compliance. Noteworthy areas of focus include:
Inter-process communication (IPC) overhead: A fix for the significant overhead caused by unbuffered IPC is scheduled for Firefox 142.
GPU task completion latency: Firefox currently uses an interval timer, which adds latency; efforts are ongoing to implement more efficient methods.
Missing importExternalTexture support: The API method allowing the GPU to directly read decompressed video content is not yet supported.
Call to Action: Users are encouraged to try WebGPU in Firefox. If problems are encountered, they should be reported in Bugzilla under the WebGPU component, with detailed instructions and about:support information attached to aid debugging efforts.