Graphics card and WebGL

A site gets the graphics card name as a ready string and computes the WebGL picture itself. Here you see the string, the number from the picture, and whether the browser has a WebGPU road.

Your values right now

The strings and the number below are read from your browser on this page.

WebGL vendor: Medindo…
WebGL renderer: Medindo…
Number from the WebGL picture: Medindo…
WebGPU available: Medindo…

Tudo nesta página é medido no seu navegador e nunca sai dele. Sem requisições, sem registros, sem conta.

The string and the picture

The vendor and the renderer come as a pair and describe the card in words. The picture is drawn on that same card, and its pixels give a number a site stores beside the string.

When the string argues with the picture

An expensive card's name beside software-rendered pixels is a ready contradiction. The same goes for WebGPU: a named card without a second road to the same hardware looks like a forgery.

What ARMANOS does

The card name reaches a site as a pair from the platform's list, and the vendor and the renderer do not change apart. Cores and memory follow the named card.

The Fingerprint self-test in the program (profile menu > Test fingerprint) reads the WebGL picture by two roads and compares the bytes: two roads to one picture have to agree.

How to compare two profiles

Open the page in two profiles. The card strings have to differ, and the number from the picture has to be particular to each of the two.

What this check does not show

The card state on a rented server. With no card the software path draws, and the string honestly names it.
A second monitor and a second card. A window opened on a laptop's other card answers with that card's name.
The precision of the number. It is taken from part of the pixels rather than the whole picture, and it serves comparison, not reproduction.

Where this is decided

The readings are measured in your browser, and the promises below are backed by files you can open.

Readings on the page come from an allowed list: apps/web/components/site/LiveReadout.tsx
The WebGL picture is read by two roads and they agree: apps/desktop/test/две-дороги-webgl-исполняются.js
Cores and memory do not diverge from the named graphics card: apps/desktop/test/fingerprint-consistency.js

Questions

Why does the renderer say ANGLE or Direct3D?: That is how a browser on Windows draws WebGL: through a layer on top of the system interface. It is an ordinary string of a live machine.
What does «no» for WebGPU mean?: The browser has no second road to the graphics card. On a machine without a card that is an honest answer, and beside an expensive card's name it is a contradiction.
Is anything sent out?: No. The picture is drawn and computed in your browser.

Next to this

Two profiles give two different answers

In ARMANOS these values are decided inside the browser engine before the page gets anything. Open two profiles, run the check in both and compare.

Download opens at launch All tools