WebGPU Browser Support and Adoption Statistics | Web3D Survey

2 min read Original article ↗

This chart shows what share of recent reports can successfully use WebGPU.

77.4%

overall WebGPU support

0.04% use the fallback adapter.

Share of all recent reports where navigator.gpu exists and requestAdapter() returns an adapter.

Browser version is only part of the story. WebGPU support also depends on the operating system, GPU, and browser engine. Use this section when you need to know where support drops on Android, Linux, iOS, macOS, Windows, or ChromeOS.

This table shows how often WebGPU support is reported on each platform.
PlatformSupport
Android73.01%
Chromium OS91.34%
iOS81.2%
Linux12.05%
Mac OS86.81%
Windows84.63%

Use browser support to see which browser families report WebGPU most often. Results are aggregated across operating systems for each family.

This table shows how often WebGPU support is reported in each browser family.
BrowserSupport
Chrome/Chromium77.6%
Edge91.62%
Firefox59.64%
Opera87.18%
Other73.96%
Safari75.8%
Samsung Internet76.32%

Vendor and architecture data help explain support patterns that browser-version charts miss. Use this section when you want to understand whether a feature gap comes from the browser, the platform, or the GPU family behind it.

This table shows what share of recent WebGPU reports is attributed to each GPU vendor.
VendorShare
intel30.46%
apple30.24%
nvidia18.51%
amd8.82%
arm6.13%
qualcomm5.6%

Feature support is where many rollout decisions get made. A browser may support WebGPU in general and still miss the feature you need. Check this section before you rely on options such as compressed textures, subgroups, or query features.

Limits decide how far you can push a device. Use this section to see the values real browsers report for texture sizes, buffer sizes, bind groups, and compute workgroup dimensions. These numbers help you choose safe defaults and decide when to request higher limits.

WGSL language features affect shader authoring and portability. Check this section when you want to know if newer language features are common enough to use without a custom fallback.