Repository navigation
Add WebGPU natively #4051
Replies: 1 comment 10 replies
And Why This Open-Source Graphics Libraries Should Support WebGPU NativelyEvidence-based proposal | October 14, 2026 Executive SummaryWebGPU is no longer a speculative browser API. It is supported across the major browser-engine families, its real-world usage is growing quickly, and established graphics engines are investing in dedicated WebGPU backends. Recommendation: Treat WebGPU as a first-class, native rendering backend, while retaining WebGL as a compatibility option. Do not limit WebGPU adoption to experimental integrations or a WebGL-only rendering architecture. The strongest case is platform readiness + adoption momentum + new GPU capabilities, not an unsupported promise that every WebGPU workload will be faster. 1. Measurable Adoption and CompatibilityGlobal browser compatibilityAccording to Can I Use's WebGPU compatibility table, global browser usage is divided into:
Source: Can I Use — WebGPU How to interpret this: These are browser-usage-weighted compatibility estimates, not proof that 87.82% of all devices can initialize WebGPU successfully. OS versions, GPU drivers, browser settings, GPU blocklists, and missing features still matter. Runtime capability checks remain necessary. The percentage is also a live metric and can change. Actual WebGPU usage on the webThe HTTP Archive's 2025 Web Almanac reports the following WebGPU usage across the sites/pages it measured:
Source: HTTP Archive — Web Almanac 2025, Generative AI (WebGPU section) The Web Almanac also cites Chrome Platform Status data indicating a 147% increase in WebGPU activations per page load over 2025. Why this matters: WebGPU usage remains small across all websites, most of which have no need for advanced GPU rendering. However, the year-over-year growth demonstrates adoption momentum. The web-wide rate should not be presented as a market-share estimate among games, visualization tools, or graphics-heavy applications. Adoption among web game developersThe Gamedev.js Survey 2025 reports that:
Source: Gamedev.js Survey 2025 Methodological caveat: This is a voluntary community survey rather than a representative census of all web game developers. It indicates developer interest and reported usage, not the percentage of shipped production games. 2. Browser Support Is No Longer Limited to One EngineImportant shipping milestones include:
Sources: Chrome Developers — WebGPU Overview, WebKit — Safari 26.0, MDN — WebGPU API WebKit explicitly described WebGPU as its preferred direction for new sites and web applications on supported Apple platforms, noting its closer mapping to Metal. Important: Availability differs by device and OS; browser-family support is not a guarantee of identical features or reliability across every supported configuration. 3. Major Open-Source Graphics Engines Have Already Made This Investment
Primary documentation: These examples do not mean WebGPU is uniformly faster or completely free of browser-specific issues. Three.js documents performance and feature differences during migration. PixiJS still describes its WebGPU renderer as experimental and recommends WebGL for production in its current documentation. This is an argument for a disciplined implementation plan, not a rushed replacement. 4. Why Native WebGPU Support MattersModern GPU capabilitiesA true WebGPU backend can expose capabilities that do not map directly to WebGL's rendering model:
Why native implementation beats a thin compatibility layerIf a library merely emulates its WebGL renderer through a WebGPU wrapper, it may carry forward the limitations of a WebGL-centric design. A dedicated backend makes it possible to handle GPU resources, pipelines, shaders, synchronization, batching, and optional compute work according to WebGPU's own model. A sensible implementation should share high-level scene APIs across backends, while allowing backend-specific internals and capabilities where necessary. Performance should be measured, not presumedWebGPU can outperform WebGL for some workloads, especially CPU-bound, draw-call-heavy, or compute-intensive scenarios. It can also underperform in simpler scenes, on particular browser/driver combinations, or with immature backend code. Do not claim a universal FPS improvement without library-specific, reproducible benchmarks. 5. Practical Implementation ProposalA maintainable path would be:
Suggested acceptance criteria
6. Ready-to-Paste GitHub IssueTitle: Proposal: Add First-Class Native WebGPU Backend (Keep WebGL Support)
7. Bottom LineThe case for native WebGPU is not that WebGL has stopped working. The case is that:
A library can preserve WebGL compatibility while investing in WebGPU as its long-term rendering path. That is a technically defensible, forward-looking proposal grounded in published data. Source Notes
|
Uh oh!
There was an error while loading. Please reload this page.
Hi,
With the ascension of Web Games and WebGPU, can you add full support for it, natively?
Today we have only
WebGPU (Dawn Native only).Thanks for this great library.
All reactions