User-Agent Parser
Parse User-Agent strings
What Is This Tool?
The User-Agent Parser reads a browser's User-Agent string and extracts the likely browser name and version, operating system, device type, and rendering engine. It is pre-filled with your own browser's User-Agent on load, but you can paste any UA string to inspect it.
How to Use
Your current browser's User-Agent is loaded automatically, or paste any UA string you want to inspect.
Click Parse to detect the browser, OS, device type, and rendering engine.
Copy the result summary, or click Example to load a sample UA string.
Features
- Detects Chrome, Firefox, Safari, Edge, Opera, and Internet Explorer
- Detects Windows, macOS, Android, iOS, Linux, and Chrome OS
- Heuristic mobile / tablet / desktop device classification
- Detects rendering engine (Blink, Gecko, WebKit, Trident)
- Pre-fills with your own browser's User-Agent string
- 100% client-side — nothing leaves your browser
Examples
Input: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
Output: Browser: Chrome 124.0.0.0 · OS: Windows 10/11 · Device: Desktop · Engine: Blink
Common Use Cases
- Debugging a browser-specific bug report by inspecting the reported UA string
- Checking what browser and OS a piece of server log data came from
- Verifying how your own browser identifies itself
- Understanding UA strings collected in analytics data
Frequently Asked Questions
Is User-Agent parsing 100% accurate?
No. User-Agent parsing is inherently heuristic and best-effort. Browsers can spoof, omit, or freeze parts of their UA string (a trend called "UA string freezing"), so results should be treated as a strong guess rather than a guarantee.
Why does my browser show a different result than I expect?
Many browsers include multiple engine tokens for compatibility (for example Chrome-based browsers also include "Safari" and "AppleWebKit" tokens). This tool checks the most specific and reliable tokens first to reduce false positives.
Can this detect bots or crawlers?
This tool is designed for standard browser UA strings and does not include a bot/crawler signature database, so results for non-browser UA strings may show as "Unknown".
Is my User-Agent string sent anywhere?
No. Parsing happens entirely in JavaScript in your browser. Nothing is uploaded or logged.
Why does it say "Unknown" for device type?
Device type is inferred from common substrings like "Mobile", "iPhone", "Android", and "iPad". Unusual or custom UA strings that omit these tokens may not be classified confidently.
Does this work for mobile browsers?
Yes, it recognizes common mobile UA patterns including iOS Safari, Chrome on iOS, and Android Chrome, and classifies them as Mobile or Tablet based on the string content.