Why can the detected operating system version differ from my device?

System names are inferred from User-Agent tokens, which may be reduced or kept for compatibility. For example, Windows 11 can report NT 10.0, while Chrome may reduce parts of its version string. Optional Client Hints can provide additional platform information when the browser allows it. Missing values are reported as unavailable. Neither a UA nor a hint independently proves the actual device or operating system.

How should I interpret screen size and device pixel ratio?

Screen and viewport dimensions are reported in CSS pixels, which are different from physical monitor pixels. At a device pixel ratio of 2, a width of 100 CSS pixels typically maps to 200 rendering pixels. System scaling, browser zoom and privacy protections can change these reports. A viewport also covers a different area from the entire screen. The sampled animation FPS is separate from these dimensions and is not a monitor specification.

Do local fingerprints prove a unique browser or device?

No. SHA-256 produces 64 hexadecimal characters describing the supplied test output, not a guaranteed unique identity. Different devices can produce identical outputs, and driver, font or browser changes can alter results on one device. This page hashes Canvas pixels, WebGL parameters and offline audio locally. It does not upload or save them. If a component fails, its status is shown and a combined fingerprint is not produced from error text.

Browser detection

Inspect browser, OS, screen, network and API support; parse User-Agents and export reports

Computed in your browser

Review the current environment first. Start extended diagnostics and local fingerprints with their buttons; custom UA parsing is separate from the current report.

Browser and OS names are inferred from the UA and can be spoofed. Memory and network values are browser estimates; exposed plugins do not list installed extensions. Request IP is what this site saw when loading the page. Reload the page to obtain a new request IP.

Find a field, API or value

Only fields with results

Run optional diagnostics

Extended diagnostics read available Client Hints, GPU, battery, storage estimates, media device counts and existing permission states, and write then remove a temporary storage test key for this origin. No location, camera or microphone permission is requested. FPS samples foreground animation callbacks for about 1 second; it is not the monitor refresh rate. Fingerprints are SHA-256 hashes computed locally without uploading or saving them, and do not prove device uniqueness.

Parse a User-Agent

Up to 8192 characters; samples demonstrate parsing. Input stays on this page and does not change the current browser report. Compatibility tokens, reduced versions and spoofing affect inference. UA alone cannot prove a real device or version.

Full detection report (JSON)

Example

Input

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Edg/131.0.0.0

Example result

Edge 131.0.0.0 / Blink / Windows 10

This is a UA parsing example, not a diagnosis of your device. Windows 11 may retain the Windows NT 10.0 compatibility token; use available Client Hints to interpret the result.

Technical details & limits

UA parsing uses local mumuy/browser 1.3.4 through parse only, without upstream network or extension probes. Native fields read browser APIs; API presence does not guarantee permission or successful operation. Client Hints are browser-controlled. Screen sizes use CSS pixels; memory and network values are estimates. Local Canvas, WebGL-parameter and offline-audio SHA-256 hashes do not prove uniqueness.

About this tool

Inspect browser-visible OS, screen, device, language, time zone and network information, plus API, CSS and media support. Parse custom User-Agents, run optional diagnostics and local fingerprints, and export JSON with explicit availability states.

How to use

Review the initial report, search fields or show only available results.
Optionally read extended information, sample FPS or generate local fingerprints.
Parse a pasted UA separately, or copy and download the current browser JSON report.

Input & output

Input: Current browser environment, plus an optional custom UA of up to 8192 characters.
Output: Grouped fields with sources and availability states, UA parsing and a local JSON report.
Limits: No extension scans, media device identifiers, external connectivity probes, incognito or VPN verdicts, or device authenticity scores.

Notes

Request IP is what this site saw when loading the page; request UA can differ from browser UA. Permissions are queried without requesting access. Reports may contain device and network information; choose what to share.

FAQ

Why can the detected operating system version differ from my device?: System names are inferred from User-Agent tokens, which may be reduced or kept for compatibility. For example, Windows 11 can report NT 10.0, while Chrome may reduce parts of its version string. Optional Client Hints can provide additional platform information when the browser allows it. Missing values are reported as unavailable. Neither a UA nor a hint independently proves the actual device or operating system.
How should I interpret screen size and device pixel ratio?: Screen and viewport dimensions are reported in CSS pixels, which are different from physical monitor pixels. At a device pixel ratio of 2, a width of 100 CSS pixels typically maps to 200 rendering pixels. System scaling, browser zoom and privacy protections can change these reports. A viewport also covers a different area from the entire screen. The sampled animation FPS is separate from these dimensions and is not a monitor specification.
Do local fingerprints prove a unique browser or device?: No. SHA-256 produces 64 hexadecimal characters describing the supplied test output, not a guaranteed unique identity. Different devices can produce identical outputs, and driver, font or browser changes can alter results on one device. This page hashes Canvas pixels, WebGL parameters and offline audio locally. It does not upload or save them. If a component fails, its status is shown and a combined fingerprint is not produced from error text.

Related tools

Browser detection · Inspect browser, OS, screen, network and API support; parse User-Agents and export reports — Browser detection — Tool illustration · dayeku.com