Browser diagnostics

Tell a reduced User-Agent from an actual device version

·

A browser can report Android 10 even when the phone runs another Android version. If a support ticket contains only a User-Agent header, check for reduction before filing a bug against an operating-system release. The parser highlights the available hints and leaves the missing version and model unknown.

User-Agent Parser

Compare a reduced Android string with an iPhone example

Choose Load comparison example in User-Agent Parser. The first column contains a reduced Android Chrome string. The second contains a Safari example with an iPhone platform comment. Compare the matched client token, version and model rows.

Chrome/143.0.0.0 tells you the Chrome major version is 143. In this pattern, Android 10 and K are Chromium’s fixed platform and model values. Check the product tokens below the table and the platform comment in the input. Confirm the actual Android version and model with the reporter if you need them.

Compare a reduced Android string with an iPhone example
FieldReduced Android ChromeSafari on iPhone
Browser or clientGoogle ChromeSafari
Client version143 (major only)17.5
Matched client tokenChrome/143.0.0.0Version/17.5
Rendering engineBlinkWebKit
OS versionUnknown17.5
Device modelUnknownUnknown

Chromium User-Agent Reduction rollout and example strings

Read browser tokens in their context

Both sample strings contain AppleWebKit and Safari tokens. A Chrome report uses the more specific Chrome token, and the Safari report uses Version/17.5 for the browser version. Product tokens and parenthesized comments can include compatibility information. Treat the browser and engine labels as interpretations of the string.

For a client with no browser engine, replace the second value with curl/8.5.0. The report identifies the HTTP client and its version, with rendering engine and operating system unknown. Download the JSON report if you need to retain both source values with their results. Unknown fields are represented by null.

IETF HTTP Semantics, User-Agent header field

Use the saved request when investigating a server-side report

Paste the User-Agent header value recorded alongside the affected request. The button for this browser reads navigator.userAgent in the current tab. Use it to compare the live label with the report. A reduced value or a different browser context can account for differences.

A named crawler token is a claim from the string. When a decision depends on the identity of the sender, verify the request with the relevant provider’s documented method and the separately captured request details.

IETF HTTP Semantics, User-Agent header fieldChromium User-Agent Reduction rollout and example strings

Common questions

Can the header distinguish Windows 10 from Windows 11?

Both can report Windows NT 10.0 in the legacy User-Agent. The parser shows Windows and leaves the release unknown.

Does a Mobile token prove I have a touchscreen?

The token describes a reported client form factor. Check input capabilities and responsive behavior separately when testing a site.

Why is the browser version missing from an embedded app?

An embedded browser may expose engine and platform tokens while omitting a product version. Ask for the app version separately when diagnosing a support report.

Sources

Put it into practice.

Related guides