About the User Agent Parser
The user agent parser inspects the browser and platform signals available to this page. It provides a readable snapshot for debugging compatibility, support reports, and content-negotiation behavior.
How to use this tool
Open the page in the browser you want to inspect; no text entry is required. Review the raw user-agent string alongside parsed browser and platform fields, language preferences, viewport information, and available capability signals. When diagnosing a user report, record the complete relevant output and the feature that failed rather than relying only on a browser name or version label.
How to read the result
The user-agent string is a compatibility identifier and often contains legacy tokens that do not describe the browser literally. Platform and vendor values are browser-provided hints. Language fields reflect browser preferences, while viewport and display values depend on the current window and device scale. Modern browsers reduce or freeze parts of the user agent to limit fingerprinting, so precise operating-system or device identification may be unavailable by design.
Limits and privacy
User-agent parsing is heuristic and should not be used as proof of identity, security posture, or exact hardware. Strings can be changed by users, extensions, automation, privacy features, and proxies. Feature detection is usually safer than browser sniffing when deciding whether code can use a web API. The parsing and display happen locally in the browser; the tool does not submit these displayed values as a separate diagnostic request.
Common questions
- Why does my user agent contain names of other browsers?
- Historical compatibility tokens let browsers receive sites built for older engines. They should not all be interpreted as installed browsers.
- Can a user-agent string identify a device exactly?
- Usually not, and modern privacy protections intentionally reduce that precision. Treat parsed device details as hints.