Browser GPU
Chrome 146 WebGPU update: what it means for browser GPU tests
Chrome's WebGPU work keeps changing what a browser can ask from the graphics stack. In the Chrome 146 WebGPU update, Google highlighted compatibility mode work for OpenGL ES 3.1, transient attachments, WGSL updates, and Dawn changes.
For BottleneckRadar, the important point is not that every device should suddenly score higher. The important point is that browser GPU diagnostics need to separate rendering performance from API availability. WebGL remains the broad fallback signal, while WebGPU is a newer capability signal that can change as browsers ship more support.
Why WebGPU support can be uneven
WebGPU depends on the browser, operating system, graphics API, driver, and hardware. A desktop GPU may expose WebGPU in one browser and not another. An older laptop may run WebGL correctly while WebGPU remains unavailable or limited. Privacy settings, enterprise policies, remote desktop sessions, and virtual machines can also hide capabilities.
How to read a browser GPU result
- A low WebGL render score can point to disabled hardware acceleration or a slow integrated GPU path.
- WebGPU unavailable does not automatically mean the GPU is bad; it can be a browser support issue.
- A browser update can change capability detection, so old screenshots may not match current results.
If a GPU-heavy website or game feels slow, test with the current browser and a second browser before replacing hardware. The difference often reveals whether the issue is hardware performance or browser support.