the screen times devicePixelRatio is a panel a monitor actually has
Under a Windows claim at 100% browser zoom and a DPR other than 1, screen × DPR is a real panel resolution. N/A at DPR 1, under zoom or pinch-zoom, off Windows, and for unusual screens that are not a stock size either (severity: warn).
What a detector infers
On Windows, screen.width and screen.height are reported in scaled pixels — the physical panel divided by the display scale — and at 100% browser zoom devicePixelRatio IS that display scale. So screen × devicePixelRatio recovers the physical panel: a 1920×1080 panel at 125% reports 1536×864 at DPR 1.25, because Windows derives one number from the other.
The broken shape is a DPR changed on its own: DPR 1.25 on an untouched 3440×1440 screen implies a 4300×1800 panel that no manufacturer makes, while 3440×1440 is itself a native ultrawide at 100%. Measured on a shipped stealth build's lightweight mode, exactly that.
The row is scoped so that a list of panels cannot convict an honest machine: it fails only when the implied panel is unknown AND the reported screen is itself a native size at 100%, only on a Windows claim, only when DPR is not 1, and only when zoom is provably 100%.
How to resolve it
Change devicePixelRatio and the screen together: at DPR d on a W×H panel the screen must report W/d × H/d, with availWidth and availHeight scaled the same way — or keep DPR at 1.
Nearby checks in Screen & display
- pointer coordinates agree with the window's own position
event-coords-vs-window-geometryA pointer event carries viewport coordinates (clientX/Y) and screen coordinates (screenX/Y), and the browser derives the second from the… - screen.width/height backed by the display (matchMedia)
screen-matchmediaThis check reads window.screen.width/height, then asks the CSS media-query engine the same question via matchMedia("(device-width: Npx) and… - devicePixelRatio matches matchMedia resolution
dpr-matchmediaThe check compares window.devicePixelRatio against the layout engine's own answer, querying matchMedia with a min-resolution/max-resolution… - screen dimensions are a plausible physical size
screen-plausibleA pure sanity range on screen.width and screen.height: both must be at least 200px and no more than 16384px. - the available screen area fits inside the screen
screen-avail-within-boundsThe available screen area is a subset of the screen by definition: availWidth and availHeight describe what is left of width and height… - screen.colorDepth decomposes into the CSS color media feature
color-depth-vs-media-colorscreen.colorDepth and the CSS color media feature describe one display in two different units: total bits per pixel, and bits per colour… - the reported colour gamut is carryable by the reported colour depth
colour-gamut-vs-colour-depthscreen.colorDepth and the colour-gamut media query are two readings of one panel, and a measured sweep of a deployed identity matcher found… - screen has an OS chrome inset (avail < screen on either axis)
taskbar-presentscreen.availWidth/availHeight describe the area left over after the OS reserves space for its own chrome — a Windows taskbar, a macOS dock…
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 Screen & display 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 Screen & display — the family dpr-screen-vs-panel belongs to.