WebGL GPU Test - What Graphics Card Do I Have?
Graphics card and WebGL test
Which graphics chip your browser draws with, what WebGL and WebGPU can do on this device, and a live 3D scene to see the frame rate.
Reading WebGL…
FPS is capped by your screen’s refresh rate (often 60 or 120). A capable GPU stays at that cap even with 512 cubes; if the number drops a lot, the graphics path is the bottleneck.
Everything is read and drawn in your browser. Nothing is sent to our server and nothing is stored.
How the GPU test works
Websites draw 3D graphics through WebGL, and newer ones through WebGPU. Both run on your graphics chip, and WebGL can tell a page which chip and driver it is using. This page reads that information, explains it in plain words and lets you watch a small 3D scene to see whether graphics are really accelerated.
How to use it
- 1 Open the page: the GPU name, vendor and graphics API appear at the top, with a warning if rendering runs in software.
- 2 Press "Start 3D test" and pick 1, 64 or 512 cubes to see how the frame rate holds up.
- 3 Check the limits and raw strings below, or press "Copy details" to send them to tech support.
How the browser knows your graphics card
WebGL offers an extension called WEBGL_debug_renderer_info that returns the "unmasked" vendor and renderer strings – the real chip and driver path. Many browsers on Windows, macOS and Linux run WebGL through ANGLE, a translation layer, so the string often looks like "ANGLE (NVIDIA, NVIDIA GeForce …, D3D11)". This page splits that string into vendor, model and graphics API (Direct3D, Metal, Vulkan or OpenGL). Some browsers deliberately return a generic name instead, because the exact GPU helps to fingerprint a device.
Software rendering: SwiftShader and llvmpipe
If the renderer is called SwiftShader, llvmpipe, lavapipe or "Basic Render Driver", the browser is not using your graphics card at all: the CPU imitates one. That happens when hardware acceleration is switched off, the driver is blocked or broken, or in remote desktops and virtual machines. Pages with maps, games or video effects then feel sluggish. The page also asks the browser for a context that refuses slow paths; if that is denied, it warns even when the name looks normal.
Laptops with two GPUs
Many laptops have an integrated GPU inside the processor and a separate, faster one. To save battery, the browser often runs on the integrated chip, so this page may show that one even though the faster card exists. On Windows you can assign the browser to the high-performance GPU in the system graphics settings; afterwards restart the browser and reload this page.
WebGL 2, WebGPU and what the limits mean
WebGL 2 adds features such as 3D textures and multisampled render targets and is what most current web 3D content expects. WebGPU is the newer, lower-level API that is still rolling out across browsers and systems. The tiles show limits reported by the driver: the maximum texture size (commonly 8192 or 16384 pixels on current hardware), viewport, texture units and anisotropic filtering. Higher values let pages use larger, sharper images, but they say little about raw speed – the 3D scene is a better hint for that.