- Official website
- WebGPU specification
- gpuweb on GitHub
- WebGPU API Proposal for Apple Webkit in 2017
- GPU on the Web Community Group at W3C
| Status | Working Draft (WD) |
|---|---|
| Year started | 18 May 2021 |
| First published | 18 May 2021 |
| Latest version | W3C Working Draft (As of 2023) |
| Organization | W3C |
| Committee |
|
| Editors |
|
| Related standards | |
| Domain | |
| Website | www |
WebGPU is the working name for a potential web standard and JavaScript API for accelerated graphics and compute, aiming to provide "modern 3D graphics and computation capabilities". It is developed by the W3C GPU for the Web Community Group with engineers from Apple, Mozilla, Microsoft, Google, and others.[1]
Unlike WebGL, WebGPU is not a direct port of any existing native API. It is based on APIs provided by Vulkan, Metal, and Direct3D 12 and is intended to provide high performance across mobile and desktop platforms.[2] Mobile platforms will be limited in creation of WebGPUDevice objects that will require modern graphics APIs (mentioned above).[note 1]
The first conceptual prototype called NXT was showcased in early 2017 by the Chromium team.[3]
The Google Chrome Development Team has named it as a "successor" to the WebGL/2 JavaScript APIs.[4][5]
On June 8, 2016, Google showed "Explicit web graphics API" presentation to the WebGL working group (during the bi-annual face to face meeting).[6] The presentation explored the basic ideas and principles of building a new API to eventually replace WebGL, aka "WebGL Next".
On January 24, 2017, Khronos hosted an IP-free meeting dedicated to discussion of "WebGL Next" ideas, collided with WebGL working group meeting in Vancouver.[7] Google team presented the NXT prototype implementing a new API that could run in Chromium with OpenGL, or standalone with OpenGL and Metal. NXT borrowed concepts from all of Vulkan, Direct3D 12, and Metal native APIs. Apple and Mozilla representatives also showed their prototypes built on Safari and Servo correspondingly, both of which closely replicated the Metal API.
On February 7, 2017, Apple's WebKit team proposed the creation of the W3C community group to design the API. At the same time they announced a technical proof of concept and proposal under the name "WebGPU", based on concepts in Apple's Metal.[8][9][10] The WebGPU name was later adopted by the community group as a working name for the future standard rather than just Apple's initial proposal.[2] The initial proposal has been renamed to "WebMetal" to avoid further confusion.[11]
The W3C "GPU for the Web" Community Group was launched on February 16, 2017. At this time, all of Apple, Google, and Mozilla had experiments in the area, but only Apple's proposal was officially submitted to the "gpuweb-proposals" repository.[12][13][14] Shortly after, on March 21, 2017, Mozilla submitted a proposal for WebGL Next within Khronos repository, based on the Vulkan design.[15][16]
On June 1, 2018, citing "resolution on most-high level issues" in the cross-browser standardization effort, Google's Chrome team announced intent to implement the future WebGPU standard.[2]
WebGPU uses its own shading language called WGSL that was designed to be trivially translatable to SPIR-V, until complaints caused redirection into a more traditional design, similar to other shading languages. The syntax is similar to Rust.[17]Tint is a Google-made compiler for WGSL.[18]Naga is a similar project developed for the needs of wgpu-rs.[19]
Both Chrome and Firefox support WebGPU with SPIR-V, with work ongoing for the WGSL front-end. Safari used to support a prototype of WebGPU with WSL, but it is now obsolete and removed in anticipation of progress in WebKit implementation that follows upstream specifications of both WebGPU and WGSL.[20]