← ALL TOOLS
// NETWORK & UTILITY · BROWSER

User-Agent Parser

Break a User-Agent string into browser, engine, operating system and device type.

NETWORK · IN YOUR BROWSER
Leave empty to parse your own browser's.

Runs in your browser; nothing you type leaves this page. Too long to share as a link.

HISTORY

Your last 5 runs appear here for 7 days, on this device only.

RESULT

Fill in the form and run the tool; the result appears here.

User-Agent Parser breaks a browser or client User-Agent string down into its browser and version, rendering engine, operating system and a device type guess (desktop, mobile, tablet or bot). Leave the field empty to parse your own browser's string.

How to read the result

The result table shows each parsed field alongside the original raw string, so you can see exactly what was matched from what was sent.

Defender tips

  • Never make a security decision (access control, feature gating for a specific browser) based on User-Agent alone; it is entirely client-supplied and trivially changed by anyone who wants to.
  • Use it for analytics and compatibility triage, where a wrong or spoofed value only affects a chart, not a security boundary.
  • Expect more Unknown or generic fields from privacy-focused browsers and from User-Agent Client Hints, which deliberately reduce what is exposed by default.

FAQ

Why do some User-Agent strings show Unknown for most fields?

Bots, minimal HTTP clients and some privacy-hardened browsers send sparse or deliberately generic User-Agent strings that do not match common browser signatures.

What is UA-CH and how does it differ from a classic User-Agent?

User-Agent Client Hints is a newer, opt-in mechanism where the browser reveals detail (exact version, platform) only when a server explicitly asks for it, rather than broadcasting everything in a single string on every request.

Why are some strings ambiguous between two browsers?

Many browsers include compatibility tokens from other browsers in their User-Agent string for historical reasons (a Chromium-based browser typically also claims to be Safari and Chrome), so parsing is heuristic, not exact.