Method & result interpretation

What does this WebGL test check?

The report attempts to create separate WebGL 1 and WebGL 2 contexts on small temporary canvases. For each available API it reads the renderer, vendor, version, shading language, texture and viewport limits, and supported extensions. No sustained rendering workload starts when you open this page. Press the detection button when you are ready.

A successful result means this browser can create that context with its current settings. A blocked context can reflect browser policy, disabled acceleration, a driver restriction or a resource limit. It does not by itself identify a faulty graphics card.

How to read renderer names and limits

The renderer is the name supplied by the browser and graphics driver. It can mention ANGLE, Metal, an integrated GPU or a software implementation. Privacy settings may hide the detailed renderer; the report then distinguishes a generic value from unavailable information rather than guessing your physical GPU model.

Maximum texture size is the largest supported dimension, not the amount of installed memory. Texture units describe how many texture inputs a shader can use. Viewport limits bound drawing dimensions. Extensions expose optional functionality and can differ between WebGL 1 and WebGL 2 on the same computer.

Use the report to investigate a test that will not start

For example, if WebGL 1 succeeds but WebGL 2 cannot create a context, the homepage WebGL2 texture workload cannot run in the same environment. Save the report, check acceleration settings and the WebGL troubleshooting guide, then repeat after changing one setting. If a renderer is hidden, treat the hardware identity as unknown.

Detection uses temporary contexts and releases them when the browser exposes the context-loss extension. Otherwise the canvases are discarded for browser cleanup. Rechecking reads the current environment; it does not install drivers or change your browser configuration.

What the report cannot measure

WebGL capability values do not reveal installed or free VRAM, GPU temperature, power, fan speed or hardware health. This page does not write and verify all memory bytes. Use the texture test for a repeatable rendering workload, the frame-time tool for browser scheduling, and native diagnostics when you need hardware memory verification.

The JSON copy and download are generated on your device. Reports include browser and renderer information, so review a file before sharing it. Detection results are not uploaded by this tool.