Your graphics card identity, WebGL capabilities, and CPU core count, read directly from your browser. Nothing is ever uploaded.
What Is a GPU & WebGL Info Checker?
This tool creates a WebGL rendering context (trying WebGL2 first, then falling back to WebGL) and reads back everything the browser is willing to reveal about your graphics hardware and its capabilities: the GPU vendor and renderer name (when your browser doesn't mask it), the WebGL/GLSL version strings, hard limits like maximum texture and viewport size, and the full list of supported WebGL extensions - plus CPU-adjacent info like logical core count and approximate device memory, where your browser exposes it.
It's useful for confirming which GPU a browser is actually rendering with (helpful when a laptop has both integrated and discrete graphics), checking whether a device supports WebGL2, or quickly seeing what 3D rendering capabilities are available before building or troubleshooting a WebGL-based app or game.
Common Ways to Use This Tool
Frequently Asked Questions
Some browsers, especially Firefox and Safari in their default configuration, mask the real GPU vendor/renderer string (showing something generic instead) as a privacy and anti-fingerprinting measure. Chrome and Edge usually expose the real string via the WEBGL_debug_renderer_info extension unless a privacy extension or flag blocks it. This is expected, intentional behavior - not a bug in this tool.
No. This tool creates a local WebGL context and reads its capabilities directly with JavaScript - nothing is uploaded or transmitted anywhere.
WebGL2 is a newer, more capable version of the WebGL 3D graphics API, roughly equivalent to OpenGL ES 3.0, with more built-in features than the original WebGL (based on OpenGL ES 2.0). This tool tries to create a WebGL2 context first and automatically falls back to WebGL if WebGL2 isn't supported by your browser or GPU driver.
It gives useful signals - GPU vendor/renderer, max texture size, and supported extensions all matter for 3D performance - but it isn't a benchmark. It reports capabilities and identity, not frame rate or real-world performance under load.
navigator.hardwareConcurrency reports logical processors (including simultaneous multithreading/hyper-threading), which can be higher than your physical core count, and some browsers cap the reported value for privacy reasons.