WebGPU Test
Find out instantly whether WebGPU works in this browser and on this graphics card. The test lists the GPU adapter, every limit and optional feature, then runs a real compute benchmark (GFLOPS), a memory copy test and a 1080p render benchmark on your GPU.
Last updated:
Adapter
- Status
- Checking…
Benchmark
Click Run benchmark to measure your GPU (about 6 seconds).
| Limit | Your adapter | WebGPU default |
|---|---|---|
| No adapter yet. | ||
- Status
- Checking…
How to use the WebGPU Test
- Open the page: the WebGPU check runs automatically and shows Supported or Not supported at the top.
- Read the adapter details: vendor, architecture and whether the browser is using a software fallback instead of your GPU.
- Browse limits and features to see what your GPU allows, for example the largest texture or buffer size.
- Click Run benchmark to measure compute speed, memory copy speed and rendering frame rate. Close other heavy tabs first.
- Click Copy report to paste the results into a bug report or forum post.
What the WebGPU test checks
| Check | What it means |
|---|---|
| WebGPU API | navigator.gpu exists: the browser has WebGPU built in and enabled. |
| GPU adapter | requestAdapter() returned a GPU. If not, the browser is blocking your GPU or driver. |
| Device created | requestDevice() succeeded, so pages can actually allocate GPU resources. |
| Render test | A WGSL shader was compiled and a frame was drawn to the canvas without errors. |
| Fallback adapter | WebGPU is running on the CPU in software instead of on your graphics card. |
Understanding the benchmark numbers
- Compute (GFLOPS): about one million GPU threads each run a loop of 4-wide fused multiply-add instructions. FLOPs = threads × loops × 64, divided by the best measured time. The loop count adapts so each run takes long enough to measure accurately.
- Buffer copy (GB/s): a 64 MB buffer is copied back and forth on the GPU with
copyBufferToBuffer. It reflects video memory bandwidth (each copy both reads and writes, so raw memory traffic is twice the number shown). - Render 1080p (frames/s): a full-screen Mandelbrot fractal with up to 128 iterations per pixel is drawn into an off-screen 1920 × 1080 texture as fast as possible, without waiting for the screen's refresh rate.
Timing uses the browser's clock around queue.onSubmittedWorkDone(), so a small amount of overhead is included and results are slightly conservative. Integrated laptop GPUs, discrete gaming cards and phone GPUs can differ by more than 10 times. Power-saving mode, a laptop running on battery and other busy tabs all lower the scores.
WebGPU vs WebGL
WebGL is based on OpenGL ES and has been available in every browser for over a decade. WebGPU is designed after modern native APIs (Vulkan, Metal and Direct3D 12): it has lower CPU overhead, explicit pipelines, and general-purpose compute shaders, which WebGL lacks. That is why in-browser machine learning (for example running language or image models locally), physics simulations and advanced renderers increasingly require WebGPU. If WebGPU is missing, most sites fall back to WebGL or WebAssembly on the CPU, which is slower.
Frequently asked questions
What is WebGPU?
WebGPU is the modern web standard for using the graphics card from a web page, the successor to WebGL. Besides 3D graphics it supports general compute shaders, which is why browser-based AI models, video effects and games use it. Shaders are written in WGSL, the WebGPU Shading Language.
Which browsers support WebGPU?
Chrome and Edge support WebGPU since version 113 on Windows, macOS and ChromeOS, and on Android since version 121 on many devices. Safari supports it since Safari 26 on macOS, iOS and iPadOS. Firefox enabled it on Windows in version 141, with other platforms following. On Linux, Chrome still needs a flag on many systems.
Why does it say WebGPU is supported but no adapter was found?
The browser has the WebGPU API, but it refused to give the page a GPU. This happens when your graphics driver is blocklisted for stability, hardware acceleration is turned off in the browser settings, the page runs inside a virtual machine or remote desktop, or the GPU process crashed. Update the graphics driver, enable hardware acceleration and restart the browser.
What does fallback adapter mean?
A fallback adapter is a software implementation (for example SwiftShader) that runs WebGPU on the CPU instead of the graphics card. It is far slower and is used when no supported GPU is available. If the test reports a fallback adapter, your GPU is not being used.
How is the GFLOPS number calculated?
The compute shader runs a fixed number of fused multiply-add (FMA) operations on 4-component vectors in every GPU thread. Each FMA counts as two floating point operations. GFLOPS = total operations ÷ measured time ÷ 10⁹, taking the best of several runs. It shows achievable shader throughput, which is usually below the GPU's theoretical peak.
Is the benchmark safe for my computer?
Yes. It runs for only a few seconds and uses the same GPU features as any web game. Laptops may speed up their fans briefly. If the driver resets, the test stops and reports a lost device; nothing is changed on your computer.
Is any data sent to a server?
No. Every check and benchmark runs locally in your browser and nothing is uploaded. The report is only copied to your clipboard when you click Copy report.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.