CIDR Toolbelt
Merge, overlap-check, and diff IPv4 CIDR lists for security groups.
OpenTurn a raw user-agent string into a browser, version, OS and mobile flag you can read.
Or press Sample to load your own browser's string.
Click Run to read browser, version and OS.
Browser, os, version and mobile fields are listed.
Copy or download it for a bug report.
A bug report includes a pasted user agent and you need to know quickly whether it came from Edge or Chrome on Windows or a phone. Reading the string by eye is confusing because almost every browser claims to be Mozilla, Safari and Chrome at once. This parser picks out the parts that matter.
Paste a user-agent string and click Run. The output is JSON with the raw string, a browser family (Edge, Chrome, Firefox or Safari, otherwise Unknown), a version number, an operating system (Windows 10/11, macOS, Android or Linux, otherwise Unknown) and a mobile flag that is true when the string mentions Mobile, Android or iPhone. Sample loads the user agent of the browser you are using right now, which is a handy way to see what your own browser sends. Copy and Download save the JSON.
Detection uses a short set of patterns, so treat it as a quick read rather than a full device database. Browsers built on Chromium, such as Opera or Brave, are reported as Chrome, and the version is taken from the first version token in the string, which for Edge is usually the Chrome version. Windows 11 still sends Windows NT 10.0, so the two cannot be told apart from the string alone. iPhone and iPad strings contain 'like Mac OS X', so they currently come out as macOS; for iPhones the mobile flag is the more reliable signal.
To inspect the full set of request headers, use the HTTP headers tool. For user agents across a whole session, a HAR summarizer works from a browser network export. Parsing happens in your browser.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Those browsers are built on Chromium and include a Chrome token in their user agent. The parser only checks for Edge, Chrome, Firefox and Safari, so other Chromium browsers fall under Chrome.
No, and neither can any parser that relies on the string alone. Both send Windows NT 10.0. Sites that need the difference use the User-Agent Client Hints headers instead.
It is better to test for the feature directly in JavaScript or CSS. User agents can be changed, shortened by browsers, or copied from other browsers, so they are best used for analytics and support triage.