GPU Test
Find out which graphics card your browser is using, check WebGL, WebGL 2 and WebGPU support with all key limits, and run a 10-second shader benchmark that gives a repeatable score.
Close heavy apps and plug in a laptop for a fair score.
Checking WebGPU…
How to use the GPU Test
- Open the page: your GPU name, vendor and support badges appear at once.
- Check the badges for WebGL, WebGL 2, WebGPU and whether hardware acceleration is working.
- Press Start benchmark and keep the tab in front for 10 seconds while the fractal renders.
- Read your score and the estimated 1080p frame rate. Higher is better.
- Open the detail tabs for every WebGL and WebGPU limit, then Copy report or Download report.
What the GPU test checks
| Item | What it tells you |
|---|---|
| Renderer / GPU name | The graphics chip the browser draws with. Laptops with two GPUs may show the integrated one if the browser runs in power saving mode. |
| Backend (Direct3D 11, Metal, Vulkan, OpenGL) | The native graphics API that the browser translates WebGL into, usually through the ANGLE layer. |
| Hardware acceleration | Whether a real GPU is used. Software renderers such as SwiftShader or llvmpipe run on the CPU and are many times slower. |
| WebGL / WebGL 2 | The 3D graphics APIs used by browser games, maps, 3D product viewers and design tools. |
| WebGPU | The modern API for graphics and GPU compute on the web, used by newer 3D engines and in-browser AI models. |
| Max texture size | The largest image dimension the GPU accepts in WebGL, which limits huge images in web editors and viewers. |
| MSAA samples and anisotropy | The highest antialiasing and texture filtering quality available to web apps. |
How the benchmark works
The benchmark renders a zooming Mandelbrot fractal in a fragment shader. Every pixel runs exactly 128 iterations of z = z² + c, even after it escapes, so the amount of work is the same on every frame and every device. The test draws batches of full frames, reads back one pixel to make sure the GPU has really finished, and adjusts the batch size so each batch takes about 15 to 30 ms. The first second is a warm-up and is not counted.
- Shader speed = pixels × 128 iterations × frames ÷ GPU time, shown in billions of iterations per second (G it/s).
- Score = shader speed ÷ 100 million. A score of 500 means 50 billion iterations per second.
- 1080p FPS estimate = shader speed ÷ (1920 × 1080 × 128): how many full HD frames of this shader the GPU could draw per second.
Because the measurement ignores your screen's refresh rate, the score is not capped at 60 or 144. Very slow or software GPUs automatically render at a smaller size so the page stays responsive; the score is still per pixel, so it remains comparable.
Getting a fair score
- Plug in a laptop and choose a high performance power mode: on battery many GPUs run at a fraction of their speed.
- On laptops with two GPUs, set your browser to use the high performance GPU in your system graphics settings, then reload.
- Close games, video calls and other heavy tabs, and keep this tab in front for the full 10 seconds.
- Run the test two or three times; the first run after opening the page can be a little lower while the GPU clocks up.
Frequently asked questions
How does the GPU test find my graphics card?
It creates a WebGL context and reads the renderer and vendor strings the browser exposes, including the unmasked renderer from the WEBGL_debug_renderer_info extension where available. Some browsers, such as Safari and Firefox with privacy settings, report a generic or simplified name on purpose.
Why does it say SwiftShader, llvmpipe or Software renderer?
Those are software renderers that draw graphics on the CPU. They appear when hardware acceleration is turned off in the browser, when the graphics driver is blocked or outdated, or in virtual machines and remote desktops. Turn on hardware acceleration in your browser settings and update your graphics driver, then reload.
How is the benchmark score calculated?
The benchmark draws a Mandelbrot fractal where every pixel runs 128 iterations of the same maths, so the work per frame is constant. It draws as many full frames as it can for 10 seconds, waits for the GPU to finish each batch, and counts shader iterations per second. The score is iterations per second divided by 100 million; the 1080p FPS estimate is how many 1920 by 1080 frames that speed would produce.
Can I compare my score with a game benchmark?
Not directly. This is a browser shader test that measures raw fragment shader speed through WebGL, which adds some overhead compared with native apps. It is useful for comparing devices, browsers, power modes and driver settings with the same test; previous scores are saved on this device so you can compare runs.
What is WebGPU and why is it not supported?
WebGPU is the newer graphics and compute API for the web, the successor to WebGL. It is available in recent Chrome and Edge, Safari 26 and newer, and is rolling out in Firefox. It can be missing on older browsers, on some Linux systems and when the GPU or driver is blocklisted.
What does max texture size mean?
It is the largest width or height in pixels of a single image the GPU can use in WebGL. 4096 is common on older phones, 8192 or 16384 on most laptops and desktops, and 32768 on some high end GPUs. Web apps such as image editors and 3D viewers use it to decide how large an image they can handle.
Does the test send my GPU information anywhere?
No. Everything is read and calculated in your browser. Nothing is uploaded, and saved benchmark scores stay in your browser's local storage.