What is this tool?
This user agent parser decodes a browser's user agent string into readable parts: browser and version, rendering engine, operating system, device type, vendor and model, and CPU architecture. It uses the open-source UAParser.js rules plus its own list of over 80 bots, including search engines, AI crawlers such as GPTBot and ClaudeBot, link-preview bots, SEO tools and HTTP libraries. With the field empty it checks your own browser and adds Client Hints (which tell Windows 11 from 10 and reveal the real browser brand) and browser signals like screen size and time zone, and flags a user agent that does not match its Client Hints. Results update as you type, and Bulk mode parses thousands of lines from a log into a table you can export as CSV or JSON. Everything runs on the page; nothing leaves your device.
How to Use
- Leave the field empty to see your own browser, pick a sample, or paste any user agent string.
- Read the cards for browser, engine, operating system, device and CPU; bots get their own card with type and operator.
- For your own browser, check the Client Hints and Browser signals cards and the spoofing check.
- Copy the result as text or JSON.
- For logs, switch to Bulk, paste one user agent or access-log line per line, and export the table as CSV or JSON.
Frequently Asked Questions
Why does it say Windows 10 or 11 instead of telling me which one?
Windows 11 browsers still send Windows NT 10.0 in the user agent, so a pasted string cannot tell the two apart. For your own browser, Chromium-based browsers expose Client Hints, and the tool reads the platform version from them to show 10 or 11 exactly.
Why is Brave shown as Chrome?
Brave sends the same user agent as Chrome, so a pasted Brave string can only be identified as Chrome. When you check your own browser, the Client Hints brand list is used, which names Brave, Edge or Opera correctly.
How does it decide a visitor is a bot?
It matches over 80 known bots by name (Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot, facebookexternalhit, AhrefsBot, curl, python-requests and more), each with a type and operator, then falls back to generic words like bot, crawler and spider. A bot that pretends to be Chrome is still reported as the bot. User agents can be faked, so treat the flag as a hint and confirm real search-engine bots with a reverse DNS lookup.
Can I parse a whole access log?
Yes. Switch to Bulk and paste one user agent per line, or raw Apache or Nginx combined-log lines; the user agent is taken from the quoted field. You get counts of bots, phones, tablets and desktops, the top browsers and systems, and a table you can download as CSV or JSON.
Other tools
There are more calculators, converters and editors on Wivrix. If something is missing, tell us.