Skip to content

Choose your path

Built around the job you need to finish

Inspect unverified browser/OS/platform claims with explicit unknowns and compare optional manually supplied Client Hints without authenticating a device.

Compatibility triager

Distinguish mobile OS and browser tokens correctly.

Compare Android, iPhone, iPad, Edge and Safari samples, then inspect reported version versus engine.

Mobile systems are not mistaken for generic desktop tokens; reported values remain claims.

Analytics reviewer

Compare two untrusted identity sources.

Provide supported and unsupported Client Hints brands; inspect raw hints, UA-only and combined inference.

No blanket hint-precedence claim; original hints and uncertainty stay visible.

Mobile privacy-aware tester

Inspect a single UA without automatic device collection.

Explicitly load this browser’s UA or paste a crawler claim, clear/retry and copy on a narrow screen.

No high-entropy collection or automatic persistence; bot token is not treated as authentication.

Was this tool helpful?

Reference & details

How it works

Parse reported tokens

Bowser 2.14.1 identifies browser, OS, platform and engine patterns. Android and iOS are distinguished from generic Linux/macOS tokens, and Safari Version is separate from its engine build. Unknown fields remain explicit.

Compare supplied hints

Optional Client Hints JSON is manually supplied and retained separately. Bowser uses selected supported hints for inference; not every brand or platform field overrides a UA token. No high-entropy hints are collected automatically.

Keep uncertainty visible

UA strings can be spoofed, reduced or frozen. A crawler token is only a claim; Windows NT 10.0 and desktop-mode iPadOS are ambiguous. Use feature detection and independent security controls. UA/hints each allow 8,192 characters; worker timeout is 10 seconds.

Updated: August 2026

Example Scenarios

Compare Android, iPhone and iPad tokens without misclassifying them as desktop Linux or macOS.

Supply selected Client Hints and compare the raw hints, UA-only inference and combined parser result.

Inspect a Googlebot-like token without treating it as bot verification, authorization or proof of a real browser.

FAQ

No. The result is a heuristic reading of supplied claims. It cannot authenticate a device, browser or crawler and should not control access.

Many clients omit, reduce or freeze tokens. Unknown is more honest than inventing a model or exact OS. Windows NT 10.0 alone does not distinguish Windows 10 from 11.

Use JSON keys brands, mobile, platform, platformVersion, architecture, model and wow64. Types are checked. Raw hints remain visible even when the parser does not use a particular field to change inference.

It loads only this browser’s reported navigator.userAgent value after you click. It clears supplied hints and does not request high-entropy device information.

No automatic history or Project persistence is used. Processing runs locally; parser assets may need a connection on first use. Review logs for sensitive data before pasting or sharing.

About User-Agent Parser

Compare reported browser and operating-system tokens without mistaking a string for a verified device. Optional Client Hints remain visible beside UA-only inference.