Read your result
Driver strings
Vendor and renderer describe the graphics driver path exposed to this browser context. A system with several adapters can use a different path in a game or desktop app. Even a detailed model name here is not independent proof of a physical card.
WebKit, ANGLE and software-renderer names can be broad or indirect. The tool preserves the returned text; it does not look up a model, invent VRAM or grade hardware health.
Missing information
Unknown is missing information, not a hardware fault.
Available WebGL with Unknown driver fields means context creation succeeded but debug information was hidden or incomplete. Unavailable WebGL means no context was returned for this attempt. Neither observation means a GPU is absent or VRAM is zero. Keep privacy protections enabled.
A real browser example
- WebGL support
AvailableA context was returned. This is not a hardware pass.
- Driver vendor
Google Inc. (Apple)The vendor string exposed to this context.
- Driver renderer
ANGLE (Apple, ANGLE Metal Renderer: Apple M4, Unspecified Version)A driver path, not a verified card inventory.
- Source
WEBGL_debug_renderer_infoThe API extension that supplied these strings.
- Limit
The browser returned a generic or software driver string. The physical GPU model is unknown.Keep this limit with any copied result.
Three steps
- Check: press Check browser GPU info for one fresh read. Nothing is read on page load.
- Read: start with WebGL support, then vendor, renderer and Source. Use the Limit row to interpret missing or generic information.
- Keep or clear: Copy visible info copies only the five displayed fields. Reset or Finish clears them; checking again replaces the previous result.
Scope and details
No benchmark, stress test, VRAM estimate or hardware diagnosis. For installed adapters, use your operating system’s device information.
| Check | How it is measured | Fails when |
|---|---|---|
| WebGL support | Whether this click obtains a temporary WebGL context. | No context is returned, or the browser blocks context creation. This is not proof of a physical hardware fault. |
| Driver vendor and renderer | The literal vendor and renderer strings from the WebGL debug information extension. The exact source constants are explained below. | The extension is unavailable, a value is empty or not a string, or a read throws. Missing fields stay Unknown. |
| Source and limits | The API used for the displayed strings, together with whether a result is generic, partial, or unavailable. | The context is lost during the read. Old strings are discarded rather than combined with an incomplete new result. |
API, privacy and resource details
API and resource lifetime
Source names WEBGL_debug_renderer_info. getParameter reads UNMASKED_VENDOR_WEBGL and UNMASKED_RENDERER_WEBGL from that extension. This follows MDN’s WEBGL_debug_renderer_info documentation, reviewed October 9, 2026.
Each click makes one synchronous WebGL read, without drawing frames, polling or requesting WebGPU. The listener and local canvas/context references are discarded after the read. WEBGL_lose_context requests explicit release when available; otherwise the browser decides when underlying driver resources are destroyed.
A lost or failed context discards old strings. Check again for a fresh attempt; repeated failure still does not diagnose hardware. Reset, Finish and another check clear copy feedback, including late clipboard replies.
Privacy and limits
No GPU field is saved to site storage, uploaded or sent to tool analytics. There is no background scan or run history. Clipboard copying happens only on request; if it fails, the visible fields remain selectable.
The check cannot measure VRAM, temperature, power use, stability, benchmark performance or hardware health. Use your operating system's documented device information for installed adapters, and the affected application's support process for its faults.
The screen test checks a panel visually. The monitor refresh rate test observes browser frame timing. Neither can fill in a missing GPU identity.
Questions
Can this GPU checker tell me my exact graphics card?
It reports the graphics driver vendor and renderer strings exposed to this WebGL context. Those can mention a model, describe a translation layer, or be generic. The page does not certify a physical adapter or choose which installed card another application uses.
Why is WebGL available but the GPU name unknown?
Creating a context and obtaining debug driver strings are different API steps. Your browser may support WebGL while hiding WEBGL_debug_renderer_info, or return empty values. Unknown preserves that missing-information boundary without suggesting that hardware is absent.
Should I turn off privacy protection to reveal a renderer?
No. Keep your privacy protections enabled. The check accepts unavailable or generic information and explains the limitation. You can consult your operating system's device information instead of exposing more browser information to a website.
Does checking a renderer benchmark or stress my GPU?
No rendering workload or frame loop is started. The page creates one temporary context, reads its permitted strings, and discards it. This is not an FPS benchmark, a video-memory estimate, or a way to decide whether a graphics card is healthy.
What happens if Copy visible info fails?
The page reports the clipboard failure instead of claiming a successful copy. You can select the displayed text manually. Reset, Finish and a new check clear copy feedback, and a late clipboard reply cannot restore a cleared result. No browser identity fields are added to the copied text.