the WebGL2 element-count limits are reported beside the renderer that claims them
Contextual only. There is no single correct pair — the values are shown beside the renderer string so the two can be read together.
What a detector infers
MAX_ELEMENTS_INDICES and MAX_ELEMENTS_VERTICES are hints the driver publishes about how many indices and vertices it draws efficiently in one call. They matter here because of where they sit: right beside the WebGL limits a persona rewrites, and just far enough off the well-known list to be forgotten.
A build that carefully clamps the famous limits — texture size, uniform vectors, varying vectors — and leaves these two alone ends up describing a discrete GPU everywhere except in two parameters that still describe the software rasteriser actually doing the work. This row is REPORTED and never scored, and the reason is a rule this page learned expensively.
Naming a verdict here would require a table of plausible pairs per driver and per generation; this audit already shipped one value table — a set of V8 heap sizes — which went stale and began telling people with an ordinary Chrome that their browser was implausible. So the values are shown next to the renderer that claims them, and the judgement is left to a reader who knows what the named GPU should do.
How to resolve it
If a persona rewrites GPU limits, rewrite these alongside the rest and keep them consistent with the GPU the renderer string names. Clamping the well-known limits while leaving the element-count hints reporting the real rasteriser is the specific inconsistency this row exists to make visible.
Read in the wild by
CloakBrowser issues
A stealth-browser tracker records these two element-count limits left unclamped beside a spoofed discrete-GPU renderer string.
CloakHQ/CloakBrowser #102, #56, #174 (WebGL limits vs spoofed renderer)
CloakHQ/CloakBrowser#102Clearcote (measured)
A reference point for reading the row, and the reason it does not score: real discrete hardware answers with the signed-32-bit maximum rather than a modest number, so 'plausible' here spans the entire positive integer range and no threshold would survive the next driver.
stock desktop Chromium on Windows, ANGLE/D3D11 on an RTX 3070: MAX_ELEMENTS_INDICES 2147483647, MAX_ELEMENTS_VERTICES 2147483647
Every attribution traces to a published artifact. See the sources and their limits.
Nearby checks in Render & GPU
- a constant signal renders at exactly the amplitude it was given
audio-render-dc-integrityThe companion to the silence check below, and the input that one structurally cannot see. - the same audio render reproduces itself
audio-render-reproducibilityAn OfflineAudioContext render involves no output device and no clock. - a browser that implements EME can satisfy its mandatory ClearKey baseline
eme-clearkey-baselineEncrypted Media Extensions is the DRM entry point, and it has one part that cannot be missing. - one canvas encodes the same pixels through toBlob and toDataURL
canvas-toblob-vs-todataurlA canvas has three exits — getImageData, toDataURL and toBlob — and a build that perturbs canvas readback has to perturb all three… - the WebGPU preferred canvas format is reported beside the claimed platform
webgpu-canvas-format-readoutnavigator.gpu.getPreferredCanvasFormat() returns the texture byte order the platform's compositor wants to be handed — and that preference… - drawing the same scene twice produces the same pixels
canvas-repeat-render-determinismCanvas noise is usually reasoned about as a trade: give up a stable hash, gain an unlinkable one. - reading the same framebuffer twice returns the same bytes
webgl-repeat-readback-determinismThe same assertion as the canvas row beside it, asked one layer down the graphics stack, and separate from it because a build can be… - MathML scripts are shaped with real metrics, not flattened to text
mathml-metrics-vs-osMathML metrics sit in the long tail of a deployed collector's signal inventory, read through an <mmultiscripts> element.
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Render & GPU checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Render & GPU — the family webgl-max-elements-readout belongs to.