WebGL?Test not run
The standard way for web pages to draw accelerated 2D and 3D graphics.
Check your browser's graphics capabilities, inspect the GPU information it exposes, monitor performance, and run an interactive graphics benchmark. Everything runs locally in your browser.
The standard way for web pages to draw accelerated 2D and 3D graphics.
A newer version of WebGL with extra features and better efficiency.
A newer, lower-level graphics and compute API that is not available everywhere.
Detection only asks the browser what it supports. The WebGPU device check is optional and releases the device straight away.
Modern browsers may restrict or mask these strings for privacy. The renderer string does not reliably identify the physical GPU: it may describe integrated graphics, a virtual GPU, a software renderer or the device the browser picked.
Renders many lit, textured 3D spheres with depth testing and a per-pixel lighting loop. Choose a preset, then start. Only one test can run at a time.
Phone or tablet detected, so the defaults are set to the lightest workload.
Ready. Nothing runs until you press Start Benchmark.
Elapsed: 0:00Remaining: 0:15
The benchmark scene appears here while it runs.
Scoring: Score = Average FPS × preset weight (Low 10, Medium 30, High 80) × (resolution scale)². The same settings always use the same formula. Scores from different presets or scales must not be compared as if they were equivalent. This measures performance on this specific browser workload, not a universal GPU score, and it is not equivalent to 3DMark, FurMark or professional benchmarks. The first 15 frames are treated as warm-up and excluded.
Source: Idle
Current FPS?
—
Average FPS
—
Minimum FPS
—
Maximum FPS
—
Frame time?
—
Frames
—
Frame time is the gap between consecutive animation frames, and each frame is counted once. Current FPS uses roughly the last half second. Minimum and maximum come from the slowest and fastest single frames. FPS is limited by your display's refresh rate and is not a hardware specification. If the tab is hidden, browsers throttle animation, so tests stop automatically.
A continuous WebGL workload with a time limit. It never starts on its own and you can stop it at any moment.
Heavy graphics workloads can increase your device's power consumption and heat. Avoid running this on a hot, low-battery or poorly ventilated device. You can stop at any time with the Stop button. This tool does not measure temperature.
Not running.
Elapsed
—
Current FPS
—
Average FPS
—
Frame time
—
The stress test scene appears here while it runs.
The stress test stops when the time limit is reached, when you press Stop, when the tab is hidden or when you leave the page. It does not measure temperature or physical stability. If the graphics context is lost, it waits for the browser to restore it.
Eight panels to inspect gradients, color bands, transparency, textures, shaders, 3D geometry and antialiasing. It is a visual browser graphics check, not a test of your monitor's physical panel or every graphics card feature.
Not running.
The visual test appears here while it runs.
Look for smooth gradients without visible steps in the top strip of panel 1, distinct and accurate colors in panel 2, correct blending over the checker in panel 3, and smooth edges in panels 7 and 8. Turn antialiasing on and off to compare. The status line shows whether the browser actually provided it. The demo stops by itself after 5 minutes.
Dedicated GPU memory is not exposed reliably by this browser.
Browsers do not give web pages a trustworthy way to read dedicated video memory. The values below are technical limits of the graphics API, not memory sizes, and must not be read as VRAM. Integrated graphics also share system memory.
Uploads small textures one at a time up to a fixed safety limit (128 MB, or 64 MB on touch devices) or 3 seconds, then frees everything. It does not measure VRAM and does not try to use up your graphics memory.
Not run.
No benchmark result yet. Run the benchmark above to see results here.
Results stay in this page only and are never uploaded. There are no rankings or comparisons with other GPUs, because no reliable reference data is available.
See whether WebGL, WebGL 2 and WebGPU are supported in your browser.
Review the renderer, limits and extensions the browser exposes.
Pick a preset and resolution scale, keep other tabs closed, then press Start Benchmark.
Follow FPS and frame time live. Stop at any moment.
Inspect gradients, colors, transparency and edges.
Use Copy Results and compare only runs with the same settings.
For fair comparisons between runs, keep the same preset, resolution scale and duration, close other heavy apps and keep the tab visible. Results depend on your browser, operating system, driver and display refresh rate.
All graphics tests run in your browser. Hardware information and benchmark results are not uploaded, need no account, and are not saved in cookies, local storage or a database. Browsers may limit or mask graphics information for privacy and security reasons. Read the full Privacy Policy.
Open this page, check the WebGL, WebGL 2 and WebGPU status cards, then run the graphics benchmark. The benchmark draws a 3D scene in your browser and measures frames per second and frame time. It tests how your browser and graphics setup handle this specific workload. It is not a full hardware diagnosis.
Look at the WebGL and WebGL 2 status cards at the top of the tool. Supported means the browser created a context, and the benchmark can run. If it says Initialization failed, check that hardware acceleration is enabled in your browser settings, update your graphics driver and browser, and close other tabs that use heavy graphics.
Not reliably. Browsers may show a renderer string through WebGL, but it can be generic, masked for privacy, or describe a software renderer, a virtual GPU or the graphics device the browser chose. Treat it as a hint, not a guaranteed identification of your physical card.
No. Web pages cannot read GPU temperature, fan speed, power draw, clock speeds or utilization. This tool does not show those values and never estimates them. Use your operating system or the graphics driver tools for that information.
Not in any reliable way. Browsers do not expose dedicated video memory directly, and values such as maximum texture size are limits, not memory amounts. This tool therefore says that dedicated GPU memory is not exposed reliably rather than showing a guess.
The score is the average FPS multiplied by a fixed weight for the chosen preset and by the square of the resolution scale. It only describes how your browser and graphics setup handled this tool's workload, so compare scores only between runs with the same preset, resolution scale and duration. It is not equivalent to 3DMark, FurMark or other professional benchmarks, and it is not a universal GPU rating.
WebGPU depends on the browser version, operating system, graphics driver and hardware, and some browsers still have it disabled or limited. It may also be blocked on a given device. The rest of this tool does not need WebGPU, and the WebGL benchmark works independently.
Yes. Integrated graphics work with WebGL like any other GPU. Start with the Low or Medium preset and a lower resolution scale. The browser decides which graphics device to use, so on laptops with two GPUs it may not be the one you expect.
It is designed to be conservative. It never starts automatically, shows a warning first, has a visible Stop button, uses a limited duration and stops when the tab is hidden. Heavy graphics work still increases power use and heat, so avoid running it on a device that is already hot, on low battery or poorly ventilated, and stop it if the device feels uncomfortably hot. The tool does not measure temperature.
No. It runs entirely in your browser using its built-in graphics features. Nothing is downloaded or installed, and the results are calculated locally and not uploaded.