Built and fact-checked by the DocNectar team — see our editorial standards
Key Features
Instant Calculation
Get accurate results in real time with our optimized algorithm.
Mobile Friendly
Fully responsive design. Works on all devices & screen sizes.
Privacy Focused
Your data stays on your device. We don't store any inputs.
100% Free
No hidden costs. This tool is completely free forever.
Every browser identifies itself to websites with a User-Agent string — a compact, sometimes confusing piece of text that reveals the browser, its version, the operating system, and device type.
This tool detects your own browser's User-Agent automatically, or analyzes any User-Agent string you paste in.
How it works
Leave the field blank to analyze your own browser's User-Agent, or paste in any User-Agent string to test. The tool checks the string against common signatures for major browsers (Chrome, Firefox, Safari, Edge, Opera, Internet Explorer) and operating systems (Windows, macOS, iOS, Android, Linux), in an order designed to avoid common false positives.
- Enter user-Agent string (leave blank to analyze your own browser).
- Click Calculate to see your results.
Examples
A typical desktop Chrome User-Agent
A Windows Chrome User-Agent string identifies as browser "Chrome" on operating system "Windows", detected as a desktop device.
Who should use it
- Quickly checking which browser and OS a support ticket's User-Agent string represents.
- Testing how your own code's User-Agent parsing logic should behave for different strings.
Industry applications
- Web development and QA testing
- Customer support and analytics
Advantages
- Detects your own browser automatically with no extra step.
- Lets you test any arbitrary User-Agent string, not just your own.
Limitations
- A lightweight pattern-matcher, not an exhaustive device/browser database.
Common mistakes to avoid
- Assuming User-Agent detection is 100% reliable for every possible browser and device — it's a widely-used but imperfect signal, and some browsers let users spoof or simplify their User-Agent string.
- Confusing a browser's User-Agent with its actual capabilities — modern feature detection is generally more reliable than parsing the User-Agent string.
Best practices
- Use User-Agent analysis for analytics and rough compatibility checks, but prefer feature detection (checking whether a specific API exists) for anything that actually gates functionality.
Tips
- When debugging a browser-specific issue reported by a user, ask for their User-Agent string and run it through this tool to quickly confirm which browser and OS combination to reproduce the issue on.