User Agent Parser & Analyzer
Instantly decode any User Agent string to reveal the browser, operating system, rendering engine, device type, CPU architecture, and bot status — all privately in your browser.
🔒 Everything runs locally in your browser. No data is sent to any server.
Parsed Results
Full UA String
Ready to Analyze
Your browser UA will be auto-loaded on page start. Paste any UA string above or pick an example below to get started.
Common User Agent Examples
Click any row to instantly load that User Agent string into the analyzer.
| Label | User Agent String | Load |
|---|---|---|
| Chrome 124 – Windows 11 | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 | Use → |
| Firefox 125 – macOS | Mozilla/5.0 (Macintosh; Intel Mac OS X 14.4; rv:125.0) Gecko/20100101 Firefox/125.0 | Use → |
| Safari 17 – macOS Sonoma | Mozilla/5.0 (Macintosh; Intel Mac OS X 14_4_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4.1 Safari/605.1.15 | Use → |
| Edge 124 – Windows 10 | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 Edg/124.0.0.0 | Use → |
| Mobile Safari – iPhone iOS 17 | Mozilla/5.0 (iPhone; CPU iPhone OS 17_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4.1 Mobile/15E148 Safari/604.1 | Use → |
| Chrome – Android (Samsung) | Mozilla/5.0 (Linux; Android 14; SM-S928B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.6367.82 Mobile Safari/537.36 | Use → |
| iPad – iPadOS 17 | Mozilla/5.0 (iPad; CPU OS 17_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4.1 Mobile/15E148 Safari/604.1 | Use → |
| Googlebot 2.1 | Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) | Use → |
| Bingbot | Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) | Use → |
| Internet Explorer 11 – Windows 7 | Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko | Use → |
| Opera – Windows | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 OPR/110.0.0.0 | Use → |
| curl (CLI HTTP client) | curl/8.6.0 | Use → |
How to Use the UA Parser
- Auto-detect — On page load, your browser's UA is loaded automatically for instant analysis.
- Paste custom UA — Paste any UA string from server logs, analytics, or documentation into the text area.
- Click Analyze — Hit the "Analyze" button or simply type to trigger real-time parsing.
- Read the dashboard — Eight labeled result cards display every detected property at a glance.
- Use examples — Click any row in the examples table to test common UA strings instantly.
What Gets Detected
- Browser Chrome, Firefox, Safari, Edge, Opera, IE — with exact version number.
- Engine Blink, Gecko, WebKit, Trident — the rendering core powering the browser.
- OS Windows (with NT version mapped to marketing name), macOS, Linux, Android, iOS.
- Device Desktop, Mobile, Tablet, or Bot/Crawler category.
- CPU x64 (64-bit), x86 (32-bit), or ARM architecture.
- Bot Named bot detection (Googlebot, Bingbot, curl, etc.).
Technical Notes on User Agent Strings
UA String Format
A typical UA follows the pattern: Mozilla/5.0 (Platform; Details) Engine/Ver Browser/Ver. The "Mozilla/5.0" prefix is a legacy artifact present in virtually all modern browsers for historical server compatibility.
Windows NT Version Map
NT 10.0 → Windows 10/11 · NT 6.3 → Windows 8.1 · NT 6.2 → Windows 8 · NT 6.1 → Windows 7 · NT 5.1 → Windows XP.
UA Reduction & Freezing
Google Chrome began "UA Reduction" (Phase 6) in Chrome 110+, gradually freezing parts of the UA string to improve privacy. The OS version, device model, and build information are being reduced to fixed strings. This is why Client Hints (via HTTP headers like Sec-CH-UA) are the recommended modern alternative.
Spoofing Warning
UA strings can be freely modified by any HTTP client. Never rely solely on UA detection for security decisions — always implement server-side validation for access control.
Frequently Asked Questions
What is a User Agent string?
A User Agent (UA) string is a text identifier sent by browsers and HTTP clients to web servers in every request. It tells the server what browser, operating system, device type, and rendering engine is being used. Web servers and analytics platforms use this to serve appropriate content, log visitor statistics, and detect crawlers.
Is my User Agent data stored or sent anywhere?
No. This User Agent Parser runs 100% client-side inside your browser using JavaScript. No UA string data is transmitted to any server, logged, or stored. Your privacy is fully protected. All parsing logic runs locally using regular expression pattern matching.
How accurate is User Agent parsing?
UA parsing via regex is highly accurate for common browsers and devices, but UA strings can be spoofed or non-standard. Browsers like Chrome intentionally include "Safari" and "Mozilla" tokens for legacy compatibility. Our parser handles these nuances by checking tokens in the correct priority order.
Why does Chrome include "Safari" in its User Agent?
For historical compatibility reasons, Chrome (and most Chromium-based browsers) include the "Safari/xxx" token in their UA string. This ensures older servers that only served content to Safari continue to work. Our parser detects Chrome before Safari to avoid misidentification.
What is the difference between Blink, Gecko, and WebKit?
These are browser rendering engines. Blink is used by Chrome, Edge, Opera, and all Chromium-based browsers. Gecko is used by Firefox. WebKit is used by Safari on Apple devices. Trident and EdgeHTML were used by older versions of Internet Explorer and early Edge respectively.
How can I detect bots and crawlers in User Agents?
Bot UA strings typically contain keywords like "bot", "crawl", "spider", "slurp", "Googlebot", "Bingbot", or "facebookexternalhit". Our parser checks for these patterns and flags the device type as "Bot/Crawler" accordingly. Always verify bot traffic server-side for security-sensitive applications.
Can I use this tool to test custom User Agent strings?
Yes! Simply paste any custom UA string into the input area and click "Analyze". The parser will immediately break down all detectable components. You can also click any row in the example table to load popular UA strings for testing.
What CPU architectures can be detected from a UA string?
Modern UA strings can include architecture hints. "x64" or "WOW64" indicates a 64-bit x86 processor. "ARM" or "aarch64" indicates ARM architecture common on mobile devices and modern Macs (Apple Silicon). "Win32" without WOW64 typically indicates a 32-bit x86 system.
Related Developer Tools
URL Parser
Break down any URL into protocol, host, path, query params, and hash fragments.
JWT Decoder
Decode and inspect JSON Web Token headers, payloads, and expiration claims.
JSON Formatter
Prettify, validate, and minify JSON data structures with syntax highlighting.
Base64 Encoder
Encode and decode text or binary data to and from Base64 format.
Regex Tester
Build and test regular expressions with live match highlighting and group capture.
URL Encoder
Percent-encode or decode URL components for safe transmission in HTTP requests.