User Agent Parser Online

User Agent Parser Quick Answer

A User-Agent string is a text value sent by a browser or other HTTP client that describes the software making the request. This parser converts that raw string into readable browser, OS, device, engine, and related details. If you only want to know what this tab is running, use Check your current browser instead.

How to Use the User Agent Parser

1. Paste a User-Agent string, pick an example, or use the current browser.
2. Results update as you type. Batch mode accepts one string per line.
3. Review browser, OS, device, engine, CPU, and bot fields.
4. Copy a summary, copy JSON, or download the file. Nothing is uploaded.

How User-Agent Parsing Works

A User-Agent is not one regex. Most browsers include compatibility tokens such as Mozilla, AppleWebKit, Safari, and Chrome even when they are not those products. This parser looks for known tokens, then applies browser-specific precedence so Edge, Opera, and Samsung Internet are not labeled Chrome.

It then reads platform tokens (Windows NT, Android, iPhone, Macintosh), device type, rendering engine, and CPU architecture when the string includes them. Known bot tokens are flagged. Client Hints, when the current browser exposes them, are shown separately and are not invented from a pasted log line.

The result panel lists product tokens such as Mozilla/5.0, AppleWebKit/537.36, and Edg/131 so you can see why a Chromium fork was not labeled Chrome. A Chrome version that ends in .0.0.0 is flagged as a reduced User-Agent. Facebook or Instagram tokens are called out as in-app browsers. Copy link can share a sample id or a short pasted string in the URL — do not put private log lines in a public link.

Example User-Agent Strings

Common User-Agent Parser Uses

Debugging browser-specific issues

Paste a UA from a bug report to see which browser and OS the reporter used. Then compare it with a known-good sample from the buttons above.

Reading server logs

Access logs store raw User-Agent headers. Batch mode turns a short list of those lines into a table you can copy or download. For one URL at a time, parse a URL separately.

Testing browser detection

Use the Edge, Opera, and Samsung samples to confirm your own code does not match Chrome first. Test regular expressions if you are writing a token check.

Mobile vs desktop

Device type is a heuristic. Android without a Mobile token is treated as a tablet. iPad is a tablet even when the string also mentions Safari. Do not use this for layout decisions — use CSS and feature detection.

Bots and crawlers

Tokens such as Googlebot or curl are labeled. A spoofed string can claim to be Googlebot. Confirm real Google crawlers with reverse DNS or published IP ranges, not this tool.

Support tickets

Copy the summary into a ticket. If the user is sitting at the computer, Check your current browser is faster than asking them to copy a header.

What Is a User-Agent String?

The User-Agent request header is a client-controlled string. Historically it named the product so servers could send compatible markup. Today it still often includes browser name and version, OS, device hints, a rendering engine, sometimes CPU architecture, and leftover compatibility tokens.

Values can be reduced, frozen, or spoofed. They do not identify a person and they are not a security check. Feature detection is usually a better way to decide what a page should do.

User-Agent Client Hints

Chromium browsers can expose structured Client Hints (navigator.userAgentData) such as brands, platform, and architecture. This page shows those hints only for the current browser. A pasted log line does not include them.

Common User-Agent Parsing Mistakes

• Checking for Chrome before Edge, Opera, or Samsung Internet.
• Assuming one token such as Linux always means a desktop OS (Android also includes Linux).
• Assuming Android always means a phone.
• Treating a User-Agent as identity, fraud proof, or access control.
• Expecting frozen or reduced UAs to include a full device model.
• Ignoring Client Hints when the live browser provides them.
• Showing a guess instead of Unknown when tokens do not match.

Frequently Asked Questions

What is a User-Agent string?

It is a client-controlled HTTP header that names the software making a request. It often includes browser, OS, and compatibility tokens such as Mozilla and AppleWebKit.

How do I parse a User-Agent string?

Paste the string into this page or pick an example. The parser applies ordered token rules and shows browser, OS, device, engine, CPU, and bot fields. Results update as you type.

What does a User-Agent string tell you?

At best it suggests a browser family, version, OS, device class, rendering engine, and sometimes CPU architecture or a bot name. It does not prove those facts and it does not identify a person.

Can I check my current User-Agent?

Yes. Use current browser fills this parser with navigator.userAgent. For a live environment card (screen, languages, capabilities), open Browser Info instead.

Can a User-Agent be spoofed?

Yes. Extensions, developer tools, and HTTP clients can send any string. Treat the parse as a best-effort reading of the text, not proof of the client.

Does this User-Agent Parser send my data to a server?

Pasted User-Agent strings are parsed in your browser and are not uploaded to EverydayTools. Site analytics, if present, are separate from the parser input.

What browsers does this parser support?

It recognizes common browsers including Chrome, Edge, Firefox, Safari, Opera, Samsung Internet, and Internet Explorer, plus several bots and HTTP clients such as curl. Unknown strings stay Unknown.

Can it detect mobile, tablet, and desktop?

It classifies device type from tokens such as Mobile, iPhone, iPad, and Android. Android without Mobile is treated as a tablet. These are heuristics, not a hardware inventory.

Can it detect Googlebot and other crawlers?

It flags known tokens such as Googlebot, Bingbot, and curl. A spoofed UA can claim the same names. Confirm real Google crawlers with DNS or published IP ranges.

Why does Chrome User-Agent contain Safari?

Chromium-based browsers historically included AppleWebKit and Safari tokens so older servers would serve modern pages. Token order, not a single Safari match, is what identifies Chrome.

What are User-Agent Client Hints?

They are structured fields some Chromium browsers expose instead of stuffing every detail into the User-Agent string. This page can show hints from the current browser only.

Is User-Agent detection reliable?

It is useful for logs and debugging and unreliable for application behavior. Prefer feature detection. Frozen or reduced UAs omit details that older strings used to include.

Can User-Agent strings identify a specific person?

No. Millions of clients share similar strings. This tool does not fingerprint users and should not be used as identity verification.

Why does my browser report an unexpected OS version?

Many browsers freeze Windows as NT 10.0 for both Windows 10 and 11. Reduced UAs may hide the real version. Client Hints can be more specific when the browser provides them.

What is a reduced User-Agent?

Chromium browsers often freeze the Chrome token as a major version plus .0.0.0 and keep Windows as NT 10.0. This parser flags that pattern and shows the product tokens so you can see what was reduced. Client Hints on this tab may still expose a fuller version.