Home/Environment checks/Browser & device

Browser and device information

Review browser-exposed User-Agent, Client Hints, device and runtime signals.

Checking. Results appear as each check finishes.

Browser values from this visit

Checking

These values are returned directly by this browser without requesting additional device permissions. They are not a complete system or hardware inventory.

Browser
Checking
System platform
Checking

Browser and system declarations

Identification combines User-Agent and Client Hints. Browser privacy controls may hide some fields.

Browser
Checking
Browser version
Checking
Rendering engine
Checking
System platform
Checking
Architecture / bitness
Checking
Browser vendor declaration
Checking
Mobile declaration
Checking
Device model
Checking
window.chrome
Checking
ProductSub
Checking
OS CPU declaration
Checking
Client Hints
Checking
User-Agent
Checking
AppVersion
Checking
Automation flag
Checking
Built-in PDF viewer
Checking
Browser plugins
Checking

Browser-exposed screen and hardware

These values are exposed to the page by the browser and are not a complete operating-system hardware inventory.

Screen resolution
Checking
Available screen
Checking
Page viewport
Checking
Outer browser window
Checking
Device pixel ratio
Checking
Screen orientation
Checking
Color depth
Checking
Pixel depth
Checking
Logical processors
Checking
Logical thread count exposed by the browser
Estimated device memory
Checking
Browser-provided bucketed estimate, not physical RAM
Maximum touch points
Checking
Media device count
Checking
Device names are not read because no permission is requested

Language, timezone and formatting

Browser settings and IP network location are shown together. Differences are consistency clues only.

Browser languages
Checking
Locale
Checking
Region code
Checking
Browser timezone
Checking
UTC offset
Checking
Calendar
Checking
Numbering system
Checking
Hour cycle
Checking
First day of week
Checking
Measurement system
Checking
IP timezone
Checking
IP country
Checking
Date sample
Checking
Number format
Checking
Currency sample
Checking
Speech voices
Checking
Voice packages
Checking

Browser feature support

Shows features available in this browser without requesting camera, microphone, location or notification permissions.

WebAuthn / passkeysChecking
Credential ManagementChecking
Web SerialChecking
Screen Wake LockChecking
Permissions APIChecking
Clipboard ReadChecking
Clipboard WriteChecking
Push ManagerChecking
BroadcastChannelChecking
SharedWorkerChecking
WebAssemblyChecking
WebGPUChecking
Storage AccessChecking
Service WorkerChecking
IndexedDBChecking
Cache StorageChecking
CompressionStreamChecking
crypto.randomUUIDChecking
structuredCloneChecking
AbortSignal.timeoutChecking
AbortSignal.anyChecking
Promise.withResolversChecking
Array.prototype.toSortedChecking
Object.groupByChecking
Set.prototype.intersectionChecking
URL.canParseChecking
navigator.userActivationChecking
WebRTCChecking
WebSocketChecking
System shareChecking
Clipboard APIChecking
Cookies
Checking
LocalStorage
Checking
SessionStorage
Checking
Storage in use
Checking
Estimated storage quota
Checking
Site-scoped browser estimate that may be rounded
Secure context
Checking
Do Not Track
Checking
Global Privacy Control
Checking
Color preference
Checking
Reduced motion
Checking

Network egress

The public address and network ownership come from the connection seen by the site; connection quality is a browser estimate.

Public IP
Checking
Address family
Checking
ASN
Checking
Network organisation
Checking
Network prefix
Checking
Network location
Checking
Request protocol
Checking
Browser online state
Checking
Estimated connection type
Checking
Estimated downlink
Checking
Estimated round trip
Checking
Data saver
Checking

Browser connection details

Shows network and browser information available during this visit; missing values are not inferred.

User-Agent
Checking
Sec-CH-UA
Checking
Sec-CH-UA-Platform
Checking
Sec-CH-UA-Platform-Version
Checking
Sec-CH-UA-Mobile
Checking
Accept-Language
Checking
Accept-Encoding
Checking
Sec-Fetch-Site
Checking
Sec-Fetch-Mode
Checking
Forwarded
Checking
Via
Checking
Privacy & network · A practical guide

A guide to browser and device information

Understand what a website can read, what the browser declares and which values are estimates before using them to diagnose a problem.

How accurate is browser device information?

A web page uses interfaces allowed by the browser; it does not scan the computer directly. User-Agent, Client Hints and platform fields are client declarations. Screen, processor, memory and storage values are also subject to browser policy.

These fields help diagnose rendering and compatibility, but they are not a complete hardware inventory. A missing model, reduced memory value or broad operating-system version can be normal privacy behavior.

Record browser values and request declarations
Visible to the website
Browser APIsReadExposed values
Current requestHeadersDeclarations

Exposed or estimated values, not a hardware scan.

Read these four groups differently

Identify the source before deciding whether a field answers your question.

Software declarations
UA and Client Hints describe a software environment but may be reduced, hidden or modified. Cross-check the browser’s own About page. A string is not a trusted device identity.
Screen and viewport
Screen, available area, window and viewport are different dimensions. Zoom, display scaling and browser controls affect them. Pixel ratio relates physical pixels to CSS pixels.
Hardware and storage
Processor count, memory and storage quota are exposed values or estimates. They need not equal machine specifications, free disk space or total device capacity.
Feature availability
An API existing, being permitted and successfully completing an operation are different things. Secure contexts, permissions, management policy and browser versions can restrict features.

Four useful compatibility checks

Share the fields relevant to the issue, rather than an entire environment report.

  1. Confirm the software version

    Use the browser’s About page, then compare the declarations here. Mobile browsers, embedded WebViews and desktop modes may expose different information.

  2. Check display conditions

    Record viewport size, zoom and system scaling. Layout problems usually depend on viewport width, not only the display’s physical resolution.

  3. Review support and policy

    Check HTTPS and whether privacy extensions or management policies restrict the feature. Grant only permissions needed for your task; this report does not require camera or microphone access.

  4. Compare a second setup

    Reproduce the issue in an updated browser or clean profile. Include the relevant values, version and reproduction steps rather than just a device name.

How does CHA.LA run this check?

The page reads navigator, screen, Intl, media queries and available Client Hints, checks storage and feature interfaces, and shows declarations visible in the current server request. Unsupported or failed fields remain missing instead of being invented.

Media enumeration only counts what the browser already permits. The page does not request camera, microphone or precise-location access. Counts and labels can depend on existing permissions and may not represent every physical device.

Frequently asked questions

UA strings, memory, display dimensions, permissions and missing values.

Why is reported memory lower than my installed RAM?

Browsers may round memory values and limit their range to reduce fingerprinting information. This is not a full measurement of physical RAM. Check operating-system settings for the actual installed capacity.

Why is the browser or system version different?

UA strings may be reduced or modified and can contain compatibility tokens. Client Hints are not universally supported. Review the declaration source and the browser’s own version information instead of relying only on a parsed name.

Why do screen resolution and viewport width differ?

Web layouts use CSS pixels. Window size, browser controls, zoom and operating-system scaling affect available space. Screen, outer-window and viewport measurements refer to different areas.

Is storage quota the same as free disk space?

No. StorageManager estimates usage and quota available to the current origin under browser policy. It is neither a full-disk capacity measurement nor an exact reading of remaining space.

Does an unavailable feature mean broken hardware?

Not by itself. Missing API support, an insecure context, privacy restrictions, permissions or management policy can explain it. Review software and policy, then test the actual feature you need.

Do I need camera, microphone or location permission?

This page does not request those permissions. It displays what the browser currently exposes, including potentially limited media-device enumeration. Extra permission grants are not required to complete the report.

Browser & Device Information - User-Agent and Client Hints | CHA.LA