📖 Online User-Agent Analyzer: Debug HTTP Headers Like a Pro
User-Agent (UA) is a critical HTTP header field that identifies the client – it contains browser name/version, operating system, device model, rendering engine, CPU architecture and more. ng.cc's online User-Agent analyzer lets you parse any UA string instantly, accurately detecting Chrome, Edge, Firefox, Safari, IE browsers, Windows, macOS, Android, iOS, Linux operating systems, and mobile, tablet, desktop device types. All parsing is done locally in your browser – zero network requests.
🌍 Full browser detection
Chrome, Edge, Firefox, Safari, Opera, IE, Edge Legacy, CriOS, etc. Version numbers automatically extracted.
💻 OS identification
Windows 7/8/10/11, macOS, Android, iOS, Linux, Chrome OS, Ubuntu, and more.
📱 Device type classification
Accurately distinguishes mobile, tablet, and desktop. Recognizes iPadOS dual‑mode (desktop vs mobile UA).
⚙️ Get your own UA
One‑click to retrieve your current browser's User‑Agent string – perfect for testing responsive layouts and server‑side device detection.
🎯 User-Agent Use Cases
- 🔧 Server‑side device detection: Serve different image sizes, CSS/JS assets based on UA for responsive websites.
- 📊 Traffic analysis: Parse UA from access logs to gather browser/OS statistics.
- 🕵️ Crawler identification: Detect search engine bots (Googlebot, Bingbot) or malicious robots.
- 🧪 Compatibility testing: Simulate different device UAs to test mobile/desktop website behavior.
- 🔐 Security policies: Block or force upgrades for outdated browsers based on UA.
💡 UA Structure Explained
🔹 Standard format
Mozilla/5.0 (platform; OS; device) AppleWebKit/engine (rendering engine) Browser/version
🔹 Common tokens
- Windows: Windows NT 10.0 → Win10/11, Windows NT 6.1 → Win7
- macOS: Macintosh; Intel Mac OS X 10_15_7
- iOS: iPhone; CPU iPhone OS 15_0 like Mac OS X
- Android: Linux; Android 13; SM-S908U
- 64‑bit architecture: Win64; x64, or WOW64 (32‑bit app on 64‑bit OS)
❓ Frequently Asked Questions
❓ Q1: Why does my site still see my original device after I change UA in DevTools?
Changing UA in browser DevTools only affects request headers for that tab – it does not alter the navigator.userAgent property used by JavaScript. This tool uses navigator.userAgent to get your "real" UA. Use DevTools' "mobile emulation" to test different UAs in the browser.
❓ Q2: Why does my iPad sometimes show up as a Mac?
Since iPadOS 13, Safari sends a desktop‑class UA (Macintosh; Intel Mac OS X ...) by default for better desktop site compatibility. You can switch to "Request Mobile Website" in Safari settings. This tool detects the actual device using the iPad keyword and touch‑capability hints.
❓ Q3: Does it support WebViews inside mobile apps?
Yes. For example, WeChat in‑app browser (MicroMessenger), TikTok (Aweasome), QQ Browser, etc. are all detected and shown as the browser name. Custom app fields may appear in the browser name.
❓ Q4: Why can't I see the exact OS version for some UAs?
Some browsers or apps deliberately hide detailed version numbers for privacy reasons. For example, newer Chrome on Windows no longer sends the Windows minor version; iOS 16+ simplified the version format. This tool extracts whatever is available; if none, it shows only the OS family.
❓ Q5: Is my UA data sent to any server?
Absolutely not. This is a static HTML page – all parsing rules run inside your browser's JavaScript engine. You can go offline and it still works. The UA strings you debug, including your own, never leave your device.
❓ Q6: Can I parse multiple UAs at once?
Currently it's a single‑line parser. Batch parsing is planned for the future. For processing many UAs, you can paste them one by one or use a command‑line tool like ua-parser-js.
🔗 Recommended Tools
This UA analyzer is part of the ng.cc developer toolkit. You might also like:
⚡ All parsing is done locally – your UA strings never leave your browser.