DevCoreTools

User Agent Parser

Paste a user agent string to inspect browser, operating system, device, rendering engine, and automation hints.

User agent string

Paste one browser, crawler, API client, or automation user agent string.

Processed locally in your browser Limit User agent text. Your input is processed in your browser and is not uploaded or sent to a server. Avoid pasting production secrets, access tokens, private keys, passwords, or sensitive customer data unless you understand the risk.
0 input characters0 product tokens0 warningslow confidence

Parsed result

Browser, OS, device, engine, bot hints, warnings, and JSON report.

Waiting for inputUnknown
Parsed user agent details appear here.

Load a sample or paste a user agent string to inspect browser, OS, device type, rendering engine, and bot or automation hints.

User agent parsing guide

Decode copied user agent strings without calling a remote parser or fingerprinting the current visitor.

Browser and version

User agent strings often contain compatibility tokens, so the parser prioritizes modern product tokens such as Chrome, Edge, Safari, Firefox, and crawler names.

OS and device hints

Platform sections can reveal Windows, macOS, iOS, Android, Linux, phone, tablet, or desktop hints, but exact models are available only when the string exposes them.

Rendering engines

Engine labels are inferred from tokens such as AppleWebKit, Gecko, Trident, and Chromium-family compatibility markers.

Bots and crawlers

Common crawler names such as Googlebot, Bingbot, social preview fetchers, and generic bot tokens are flagged when they appear in the text.

Spoofing and reduced UA

User agents are easy to spoof, and modern browsers can freeze or reduce details. Treat the output as a debugging hint, not a security decision.

Parser vs headers parser

Use this tool for a single User-Agent value. Use HTTP Headers Parser when you need to inspect the full request or response header block around it.

Keep working

View all API & Auth tools
HTTP Headers Parser / FormatterParse, format, inspect, and export HTTP headers locally with structured warnings.MIME Type LookupLook up MIME types and file extensions locally with Content-Type header examples.HTTP Status Code LookupLook up HTTP response status codes locally with meanings, examples, and API notes.URL Parser / Query String ParserEncoding & DecodingParse full URLs, relative URLs, and query strings into structured parts.JSON FormatterJSON ToolsFormat, validate, inspect, and export JSON locally.Text Diff CheckerText & Code ToolsCompare plain-text blocks and highlight line-level and word-level changes locally.
Learn more: JWT Guide

FAQ

Does this parse my current browser automatically?

No. The tool treats pasted text as input. It does not fingerprint the current visitor or read the live browser user agent automatically.

Can user agent strings be trusted?

No. Clients can spoof user agents, browsers may reduce detail, and proxies or test tools can rewrite them. Use the result as a best-effort debugging aid.

Why does Chrome also include Safari and AppleWebKit?

Many browsers include compatibility tokens for historical web behavior. The parser uses product-token priority to avoid labeling Chromium browsers as Safari.

Can this identify every device model?

No. Some Android strings expose a model, while iOS and modern desktop browsers usually hide or generalize device details.

When should I use HTTP Headers Parser instead?

Use HTTP Headers Parser for complete copied header blocks, duplicate header behavior, security headers, CORS, cache directives, and surrounding API context.