Skip to content
All fingerprint checksEnvironment & locale

navigator.pdfViewerEnabled is true

Check id pdf-viewer

What an ordinary browser yields

true on a desktop Chrome profile with the built-in viewer; false or absent is legitimate on mobile, WebKit, or policy-restricted builds.

What a detector infers

A direct read of `navigator.pdfViewerEnabled`. It is N/A when the property is not exposed at all, passes when true, and is marked false otherwise — at 'info' severity, so it is contextual and not scored. On its own the flag proves little: false is entirely normal on mobile Chrome, on WebKit, and wherever enterprise policy disables the built-in viewer. Its real job in this audit is to supply the premise for the plugins check above, which only demands a populated plugin array when this flag claims a viewer exists. Read the two lines together, not separately.

How to resolve it

No fix required in isolation — this is a reading, not a verdict. Only act on it if it contradicts the plugin list (see has-plugins) or the platform you are presenting.

What is a headless browser?

Read in the wild by

PerimeterX / HUMAN

Collects navigator.pdfViewerEnabled as its own boolean field, in the same payload that separately carries the navigator.plugins name list and plugin count.

main.min.js (stample/ifood/source): `t[0][hQ(877)]=hU.pdfViewerEnabled`, where hQ(877)="JxcSHWJ3FCY=" — PX_SDK_Reverse_Engineering.md:1647 `| 130 | JxcSHWJ3FCY= | boolean | true | - | hQ(877) |`. Same EV2 payload, field 91 — PX_SDK_Reverse_Engineering.md:1608 `| 91 | T386NQoaPg4= | object | ["PDF Viewer","Chrome PDF Viewer","Chromium PDF Viewer"] | 8022 | plain |`, populated by CC(), which pushes `hU[hQ(382)][i].name` over `hU.plugins.length` (hQ(382)="plugins").

CreepJS

CreepJS, a research demo rather than a production detector, reads navigator.pdfViewerEnabled and counts a false reading toward its "like headless" rating.

src/headless/index.ts — inside the `likeHeadless` object: `pdfIsDisabled: ('pdfViewerEnabled' in navigator && navigator.pdfViewerEnabled === false)`, scored via `likeHeadlessRating = +((likeHeadlessKeys.filter((key) => likeHeadless[key]).length / likeHeadlessKeys.length) * 100).toFixed(0)`

Every attribution traces to a published artifact. See the sources and their limits.

Nearby checks in Environment & locale

See all 23 checks in Environment & locale
Who builds this test

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 Environment & locale 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 Environment & locale — the family pdf-viewer belongs to.