User Agent Parser
Decode any User-Agent string into browser, OS, device, and engine info. 100% client-side.
111 chars
🌐Browser
Chrome
Version 120.0.0.0
🖥️Operating System
Windows
Version 10 / 11
💻Device
Desktop
⚙️Rendering Engine
Blink
Version 120.0.0.0
📋 Parsed JSON
{
"browser": {
"name": "Chrome",
"version": "120.0.0.0"
},
"os": {
"name": "Windows",
"version": "10 / 11"
},
"device": {
"type": "Desktop",
"brand": "",
"model": ""
},
"engine": {
"name": "Blink",
"version": "120.0.0.0"
}
}📚 Sample User-Agents
🔒 100% private: All parsing happens in your browser. Your UA strings never leave your device.
About User Agent Parser
A User-Agent string is sent by every web browser with each HTTP request. It identifies the browser, version, operating system, device type, and sometimes additional metadata like the rendering engine. Web developers use User-Agent strings for analytics, feature detection, mobile redirects, bot filtering, and A/B testing. But UA strings are notoriously cryptic — a modern Chrome UA on Windows looks like "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36". This tool decodes any UA string into human-readable fields: browser name and version, OS name and version, device type (desktop/mobile/tablet/bot), and rendering engine. It also parses your own browser's UA in one click and supports bulk parsing.
How It Works
- Paste a User-Agent string into the input box.
- See it parsed into browser, OS, device, and engine info.
- Click "Use My Browser UA" to auto-fill your current UA.
- Use bulk mode to parse multiple UA strings (one per line).
✨ Key Features
- ✓Parse browser name and version (Chrome, Firefox, Safari, Edge, Opera, Brave, IE, Vivaldi)
- ✓Parse OS name and version (Windows, macOS, Linux, iOS, Android, Chrome OS)
- ✓Detect device type (desktop, mobile, tablet, bot)
- ✓Detect rendering engine (Blink, WebKit, Gecko, Trident, EdgeHTML)
- ✓Detect mobile devices (iPhone, iPad, Samsung, Xiaomi, etc.)
- ✓One-click parse of your own browser UA
- ✓Bulk mode — parse many UA strings at once
- ✓Copy any field with one click
- ✓Device-type icons for quick identification
- ✓100% client-side — no data sent to any server
🎯 Common Use Cases
- →Debugging why a website displays differently in different browsers
- →Analyzing server logs to understand visitor demographics
- →Testing mobile detection logic
- →Verifying User-Agent spoofing
- →Filtering bot traffic in analytics
- →Understanding what your own browser reports
- →Bulk-parsing log entries to count OS/browser usage
- →Detecting unsupported browsers before showing a warning
💡 Advanced Tips & Pro Insights
- ▸Modern browsers often have spoofed UA strings for compatibility. Chrome on iOS reports "Safari" because Apple requires all browsers to use WebKit. Real detection requires feature detection, not UA strings.
- ▸User-Agent strings are being deprecated by some browsers (Chrome is reducing their information). For robust detection, use feature detection (Modernizr, CSS @supports) or Client Hints.
- ▸"Mozilla/5.0" at the start of every modern UA is a legacy compatibility token — it does not mean the browser is Mozilla/Firefox.
- ▸Bot UAs often contain "bot", "crawler", "spider", "Googlebot", "Bingbot", "Yandex", "Baidu". Filter these in analytics for accurate human traffic stats.
- ▸Chrome User-Agent Reduction (since Chrome 101+) freezes the minor version to "0.0.0" and the OS version to a limited set of values — this reduces fingerprinting but also reduces UA accuracy.
Frequently Asked Questions
Is this User-Agent parser free?▾
Yes, this User-Agent parser is completely free with no signup, email, or usage limits.
Is my data safe?▾
Yes, 100% safe. All parsing happens in your browser. Your UA strings are never sent to any server.
What is a User-Agent string?▾
A User-Agent (UA) is an HTTP header sent by browsers and other clients that identifies the browser, version, operating system, and device. It is used for analytics, feature detection, and content negotiation.
Why does Chrome report "Safari" in its UA?▾
Chrome includes "Safari/537.36" for compatibility with websites that check for Safari. Real Safari is identified by the absence of "Chrome" and presence of "Safari" plus "Version/X.X".
Why does my UA start with "Mozilla/5.0"?▾
This is a legacy token that browsers have included since the 1990s for compatibility with websites that only supported Netscape (Mozilla). It does not mean the browser is Firefox.
How do I detect mobile devices?▾
Mobile UAs contain "Mobile", "Android", "iPhone", "iPad", "Windows Phone", etc. However, mobile detection by UA is unreliable — use CSS media queries (@media (max-width: ...)) or feature detection for responsive design.
What are Client Hints?▾
Client Hints are a newer, more privacy-respecting alternative to User-Agent strings. Browsers send them only when the server requests them. They provide structured data (device type, platform, browser brand) without the cryptc UA string.
Can I parse multiple UA strings at once?▾
Yes. Enable bulk mode, paste one UA per line, and see all parsed at once. Useful for analyzing log files or analytics exports.