GPU Hardware Acceleration

Check the recorded renderer

The renderer name is browser-reported information, not a guaranteed full hardware identity. Privacy settings can hide it, and translation layers can add backend names. An unexpected label or unavailable value is not a failed GPU. Save the browser version, actual API, and fallback reason with your report.

Why an API can be unavailable

WebGPU requires a secure context and a usable adapter; support depends on browser and platform policy. WebGL can also be disabled or blocked. Check normal browser acceleration settings and official browser or driver updates. Do not bypass security warnings or force experimental flags merely to obtain a score.

Start with a lighter path

Close other graphics-heavy tabs, choose Low, and reduce the render resolution. Try an ordinary WebGL workload if compute is unavailable. WebGPU compute requires its own supported pipeline and does not silently become a CPU test. Compare separate API paths as different configurations, even when their scene looks similar.

Handle a lost graphics context

A context can be lost after a driver reset, resource pressure, or browser decision. The interrupted run should not be treated as a completed benchmark. Stop, allow the device to recover, and retry a lighter configuration. If failures persist outside this page, use manufacturer diagnostics and record the reproduction steps.

• Open Volume Shader Benchmark
• GPU Testing Methodology