User Agent Parser
Parse any user agent string instantly. Detect browser, operating system, device type, and rendering engine — free, online, no installation needed.
Updated May 2026
Paste the full HTTP User-Agent header from any client or log file.
How to parse a user agent string
Your own user agent is detected automatically
1. Paste the UA string
Your current browser's user agent is pre-filled — replace it with any string from a server log or bug report.
2. Read the summary cards
Browser, OS, device type, and rendering engine show up instantly, no spec-reading required.
3. Copy the results
Click Copy or press `Shift+Enter` to copy the full breakdown as plain text.
When you'd reach for a user agent parser
The scenarios that come up most for people who use this tool
Debugging access logs
Figure out which browser or client made a request without reading the UA spec by hand.
Bot and crawler detection
Check whether a string belongs to a legitimate bot (Googlebot, Bingbot) or a spoofed agent pretending to be one.
Building adaptive interfaces
Confirm exactly what a UA string reports before you build progressive enhancement or feature detection around it.
Cross-browser QA
Verify the exact browser version from a bug report before trying to reproduce the issue.
What you can extract from a user agent
Six structured fields pulled from one raw string
Browser and version
Chrome 124, Firefox 125, Safari 17, Edge 124, and so on.
Operating system
Windows 11, macOS, Android 14, iOS 17, Linux, Chrome OS.
Device type
Desktop, Mobile, Tablet, or Bot/Crawler.
Rendering engine
Blink (Chrome/Edge), Gecko (Firefox), WebKit (Safari), Trident (IE).
CPU architecture
x86_64, ARM64, ARM, i686.
Browser vendor
Google, Mozilla, Apple, Microsoft, Samsung.
Parsing examples
Common mistakes when reading a UA string
Assuming legacy tokens name the real engine
like Gecko shows up in browsers that never touched Gecko — it's a compatibility token, and the parser filters it out.
Trusting a "Bot/Crawler" label blindly
Malicious bots sometimes spoof real browser strings specifically to avoid being flagged, so treat detection as a signal, not proof.
Not knowing where to find your own UA
Open DevTools (F12), go to the Console, and type navigator.userAgent to get the exact string your browser sends.
Why use this tool
It turns raw UA strings — packed with legacy compatibility tokens that exist for historical reasons — into structured, readable fields, without you having to read the specification by hand.
Everything runs in your own browser — no string is ever sent to a server, which makes it safe to paste UAs pulled from sensitive access logs.
Frequently asked questions
It's a tool that reads the User-Agent string sent by browsers and HTTP clients and breaks it into structured fields: browser name and version, operating system, device type, and rendering engine. It saves you from manually decoding the raw string against the HTTP spec.
References
Related Tools
- URL Encoder Developer Encode any URL or text to percent-encoding instantly in your browser. Follows RFC 3986. Free, no sign-up required.
- HTTP Status Code Reference Developer Complete HTTP status code reference — all 1xx, 2xx, 3xx, 4xx, and 5xx codes explained with meanings, use cases, and SEO impact.
- JWT Decoder Developer Decode and inspect JSON Web Tokens instantly — view header, payload, verify HMAC signatures, and generate JWT code in PHP, JavaScript, Python, and Java.
- User Agent Generator Developer Free online User Agent Generator. Create custom UA strings for Chrome, Firefox, Safari, Edge, bots & mobile devices instantly. No signup required.
- ASCII Table Generator Developer Free ASCII table generator — create plain-text tables in MySQL, Markdown, Unicode and more styles. Paste CSV or type data, copy output in one click. No signup.
