QiLing Tools

🕵️User-Agent Parser - Detect Browser, OS, Device & Bots Online

Reading server logs, debugging compatibility issues or writing bot rules all require understanding User-Agent strings. The page automatically shows your current browser's UA and its breakdown; paste any UA from a log and it identifies the browser (Chrome, Safari, Edge, Firefox, Samsung Internet, WeChat and more) with version, the engine (Blink, WebKit, Gecko), the OS (Windows, macOS, iOS, Android, HarmonyOS, Linux) with version, the device type (phone, tablet, desktop, TV) and common phone models, and flags search engine crawlers, AI bots and scripted clients such as curl or Python. Built-in examples and JSON output included.

Free · No sign-up · Runs in your browserLast updated:

Loading tool...

How to use User-Agent Parser

  1. 1Your UA is filled in automatically; paste another User-Agent to analyze it
  2. 2Review the browser, engine, OS, device and bot detection results
  3. 3Click examples to compare devices or copy the result as JSON

FAQ

Why is Windows 11 shown as Windows 10 / 11?
Browsers on Windows 11 still report Windows NT 10.0 in the UA, so the two cannot be told apart from the string alone. Use User-Agent Client Hints (navigator.userAgentData) on the client if you need the exact platform version.
Why does Chrome's OS version look wrong?
Chrome applies UA Reduction, freezing details such as the Android model and macOS version (macOS always reads 10.15.7). This is intentional browser behavior, not a parsing error.
How reliable is bot detection?
It recognizes common crawlers like Googlebot, Bingbot, Baiduspider, GPTBot and ClaudeBot plus clients like curl and Python by UA patterns. Since UAs are easy to spoof, strict bot filtering should also use reverse DNS and rate analysis.
Is my data uploaded?
No. Everything runs locally in your browser with no network upload and is discarded when you close the page, so it is safe for internal or sensitive data.