How this page finds your graphics card
Web pages draw 3D graphics through WebGL, and WebGL can tell a page which graphics driver it runs on. Chrome, Edge and other Chromium browsers share it through the WEBGL_debug_renderer_info extension as a renderer string such as ANGLE (NVIDIA, NVIDIA GeForce RTX 4070 Direct3D11 vs_5_0 ps_5_0, D3D11). The page turns that into a plain name, here “NVIDIA GeForce RTX 4070”, and shows the full string underneath so you can see exactly what the browser said. The part after the name tells you which graphics API the browser translates WebGL to: Direct3D 11 on Windows, Metal on a Mac, OpenGL or Vulkan on Linux and OpenGL ES on Android.
Where the browser supports WebGPU, the page also asks for a WebGPU adapter and lists what it reports: the vendor, the GPU architecture (such as Ampere, RDNA 3 or Xe), its optional features and its limits. On a laptop with two graphics processors it asks for the high-performance one as well, and names both when they differ.
Why the name can be missing or vague
A GPU name narrows down who you are, so browsers limit it to make fingerprinting harder. MDN notes that the renderer information depends on the browser’s privacy settings. What you will see:
- Chrome, Edge, Brave, Opera: usually the exact model.
- Firefox: a sanitized name. Since Firefox 91 it reports a representative card from the same family, and since Firefox 92 it gives that name to every page through the standard renderer parameter (Mozilla bug 1722113). The vendor and family are right; the model number may not be.
- Safari, and every browser on iPhone and iPad: “Apple GPU”, whatever the chip.
- Privacy modes such as Firefox’s resist fingerprinting setting hide it completely.
The WebGPU specification takes the same approach: adapter identifiers should be “as broad as possible while still being useful”, and browsers may leave them out entirely, which is why WebGPU often gives only a vendor and an architecture. This page shows what your browser reports and never guesses beyond it. For the exact model, use the steps under Find the exact model in your system: Task Manager or dxdiag on Windows, About This Mac, or lspci on Linux.
Is hardware acceleration on?
If the renderer is SwiftShader, llvmpipe, lavapipe or the Microsoft Basic Render Driver, the browser is drawing with the processor instead of the graphics card. The page also creates a WebGL context with failIfMajorPerformanceCaveat, an option the WebGL specification defines so that a browser refuses the context when rendering would be much slower than native, in practice when it falls back to software. Chrome, Edge and other Chromium browsers honour it; Firefox has ignored it by default since version 86 (Mozilla bug 1678652), so in Firefox the page goes by the renderer name alone. Either sign turns on the warning with the steps for your browser. Software rendering usually means the acceleration setting is off, the graphics driver is missing or on the browser’s blocklist, or the browser is running in a virtual machine or over remote desktop.
How to read the benchmark
The benchmark draws a fractal shader over a 1920 × 1080 image as fast as the GPU allows, first with WebGL 2 and then, if your browser has it, with WebGPU. The image is rendered offscreen and each batch of frames is timed until the GPU confirms it has finished, so a 60 Hz display doesn’t cap the result at 60 fps. The result is the median frames per second and frame time, plus the frame time of the slowest 5%.
It is a test of browser graphics, not a full GPU benchmark: it stresses shader arithmetic and fill rate, but not video memory, geometry, ray tracing or the CPU side of a game. It is best for comparisons on the same device: plugged in against on battery, Chrome against Firefox, before and after a driver update, or with acceleration on and off. Battery saver, browser energy saving modes and a hot laptop all lower the score. The test stops by itself if you switch tabs, because browsers slow down background tabs.
WebGL and WebGPU support
WebGL 2 works in every current browser. WebGPU is newer. According to web.dev, Chrome and Edge have had it since version 113 on Windows, macOS and ChromeOS and since 121 on Android 12 and later, and Safari 26 ships it on macOS, iOS and iPadOS 26. Chrome 144 began rolling it out on Linux, starting with Intel Gen12 and newer GPUs (Chrome for Developers). Firefox added it on Windows in version 141, on Apple silicon Macs with macOS 26 in 145, and on Apple silicon Macs with any macOS version in 147 (Firefox 145 and 147 release notes). If the browser supports WebGPU but reports no adapter, the GPU or driver is usually blocked, or the driver is too old.
While you are checking your hardware, measure your display’s real rate with the refresh rate test, look for stuck pixels with the dead pixel test, and test your gamepad with the controller tester.