Learning objectives
After reading this article you will be able to:
- Separate screen dimensions, viewport and pixel ratio
- Read CPU and memory values as browser-reported hints
- Explain expected differences between device specifications and a browser report
Screen size, viewport and pixel ratio
Screen information describes the reported display; viewport information describes the area available to the page.
| Field | What it describes | Why it can vary |
|---|---|---|
| Screen dimensions | Display dimensions exposed by the browser | Display choice, scaling and privacy policy |
| Viewport dimensions | The current page’s layout area | Window resizing, sidebars and browser UI |
| Device pixel ratio | Ratio of device pixels to CSS pixels | Display scaling and browser zoom |
A CSS pixel is a layout unit, so the dimensions shown by a webpage need not match the panel’s advertised physical resolution. Moving a window to a different display can also alter several fields.
For repeat checks, record the window size, zoom and display. If you intentionally change one, interpret the related fields together.
CPU, memory and touch information
Browsers expose selected resource and input hints rather than a complete hardware inventory.
hardwareConcurrency reports a number of logical processors available to the browser, which may be limited. Device memory, where supported, is a coarse hint and may be rounded or capped. It should not be treated as an exact reading of installed RAM.
Touch capability is another hint. A laptop may have a touchscreen, and a browser may limit what it reports. One field is a weak basis for deciding whether a visitor uses a phone, tablet or desktop.
Comparing two windows on the same computer
Shared display and hardware values are expected when profiles use the same underlying device.
Profiles can isolate cookies while reporting the same screen dimensions. To evaluate data isolation, check site storage or sessions. To evaluate reported device settings, compare the individual fields with the profile configuration.
A meaningful consistency check asks whether the combination is plausible and matches the intended settings. Making every field different is not a useful goal by itself.
Why these everyday fields matter
Common values can still become informative in combination with language, platform and rendering behavior. Understanding their source also makes routine troubleshooting simpler: a viewport change points to layout conditions, while a reported platform mismatch points elsewhere.
Interpreting the result
- Browser-reported values may be reduced, rounded or limited.
- The physical display and the browser’s layout units are different measurements.
- A matching screen or core count does not establish shared login data.
Frequently asked questions
Why does the report show less memory than my computer has?
The API can expose a coarse or capped estimate. Check browser support and reporting rules before interpreting it as a hardware problem.
Does resizing my window change my fingerprint?
It changes viewport-related observations. Whether a site includes those fields in its fingerprint depends on its method.
Should every profile have a different screen resolution?
Choose settings for your actual workflow and verify their consistency. Shared dimensions alone do not demonstrate an isolation failure.