Navigator properties

Your browser describes the environment around it.

Ordinary page JavaScript can ask your browser about its identity, languages, logical processors, memory bucket, touch support, and runtime state. Each answer is modest. Together, they form a structured profile that can be recognized, cross-checked, and combined into a larger browser fingerprint.

Permission: Usually none
Read by: Page JavaScript
Strength: Combination + consistency

window.navigator

One built-in object exposes several overlapping descriptions of the browser and device.

Navigator inspector

Read what this browser makes available.

This demonstration reads a small set of properties locally. The values remain in this page and are not transmitted or stored by the demonstration.

local-inspector.js

const profile = {
  browser: navigator.userAgent,
  platform: navigator.platform,
  languages: navigator.languages,
  cores: navigator.hardwareConcurrency,
  memory: navigator.deviceMemory,
  touch: navigator.maxTouchPoints,
  automated: navigator.webdriver
};

Live local outputBrowser self-description

Nothing is sent

Browser claim: Waiting to inspect
Platform: —
Languages: —
Logical processors: —
Memory bucket: —
Touch points: —
PDF viewer: —
Automation flag: —

A value may be unavailable, reduced, or standardized by the browser. That absence is also observable.

Property families

Navigator is not one signal.

The interface is a directory of browser capabilities and state. Fingerprinting code selects properties that help classify the browser, approximate the device, or test whether the surrounding story is internally consistent.

01Browser identity
navigator.userAgentnavigator.userAgentDatanavigator.vendornavigator.platform
Browser family, operating-system claims, device class, and implementation quirks.
02Hardware shape
navigator.hardwareConcurrencynavigator.deviceMemorynavigator.maxTouchPoints
Bucketed or approximate clues about processors, memory, and input hardware.
03Preferences
navigator.languagenavigator.languagesnavigator.cookieEnablednavigator.doNotTrack
Language order and browser-level privacy or storage preferences.
04Runtime state
navigator.webdrivernavigator.pluginsnavigator.pdfViewerEnablednavigator.globalPrivacyControl
Automation, built-in capabilities, and browser-specific feature exposure.

Consistency checks

Values tell a story. Mismatches tell another one.

A collector can compare properties that describe the same environment from different angles. Agreement increases confidence in the profile. A contradiction can suggest emulation, automation, spoofing, or an unusual configuration.

A mismatch is evidence, not proof. Touch-capable laptops, compatibility modes, privacy defenses, and browser bugs can all produce unusual combinations.

What the browser claims“Windows desktop Chrome”

Collector outputcoherent platform · automated runtime

Illustrative consistency check. Real systems assign different weights and may use many more signals.

User-Agent and Client Hints

Reducing one string did not remove the browser description.

Browsers have reduced some detail in the traditional User-Agent string. Chromium also exposes User-Agent Client Hints: a smaller default set of claims plus additional values that a site can request. The mechanism changes how detail is delivered, not whether browser identity can contribute to a fingerprint.

Legacy surface

One long string

Mozilla/5.0 (…) AppleWebKit/537.36 (…) Chrome/153.0.0.0 Safari/537.36

navigator.userAgent remains easy to read, but some version and platform detail may be frozen or reduced.

Client Hint surface

Defaults and requested detail

Available by defaultbrands · mobile · platform

May be requestedarchitecture · bitness · model · full versions

Support and returned values differ by browser. High-entropy values can also be limited by browser policy or Permissions Policy.

Normalized observationprofile_7C2

+screen · WebGL · fonts · headers · network

combined fingerprint8d31…a09f

Synthetic values. A production fingerprint may normalize and hash a much larger observation set.

The combination

Common answers can still form an uncommon profile.

“Windows,” “English,” and “eight gigabytes” each describe large crowds. Their intersection is smaller. Add ordered languages, processor count, touch support, graphics output, viewport, headers, and network behavior, and the profile can become stable enough to recognize later.

PropertyPopulation matching

Platformlarge crowd

+ language ordernarrower

+ hardware shapesmaller still

+ other surfacesrecognizable profile

Meaningful defenses

The goal is a less distinctive and more coherent browser story.

Changing a single property can create a new contradiction. Stronger defenses reduce detail, standardize answers across users, and keep related layers consistent.

01
Standardize
Report the same small set of values for a large population so one browser blends into an anonymity set.
02
Reduce granularity
Bucket or freeze details such as device memory, processor count, platform versions, and User-Agent fields.
03
Keep layers consistent
Align JavaScript properties, request headers, Client Hints, display behavior, and the rest of the exposed profile.
04
Limit unnecessary access
Restrict high-detail APIs and requested Client Hints when they are not needed, while accounting for compatibility.