User Agent Parser

The User Agent Parser breaks down the cryptic user-agent strings that browsers send with every web request into readable columns you can actually use. You paste one string per line, and the tool identifies the browser, its version, the operating system, and the broad device category for each entry, presenting the whole batch as a tidy table. Instead of squinting at a long string packed with tokens and version numbers, you get the facts that matter at a glance.

User-agent strings are notoriously messy because of decades of backwards-compatibility tokens. Chrome pretends to be Safari, Edge pretends to be Chrome, and mobile browsers pile on extra identifiers. This parser applies a set of well-ordered heuristics that check for the most specific signatures first, so an Edge string is recognised as Edge rather than being mistaken for the Chrome token it also contains, and mobile and tablet devices are told apart from desktops.

All parsing happens in your browser, which means the strings you paste, often pulled from your own server logs or analytics, are never uploaded or stored. You can analyse a single string while debugging a support ticket or a whole list exported from your access logs, then copy the resulting table for a spreadsheet or report without any account or network dependency.

Features

• Identifies major browsers including Chrome, Firefox, Safari, Edge, Opera, Samsung Internet and Internet Explorer.
• Extracts the browser version number so you can spot outdated clients that may need extra testing.
• Detects the operating system and, where present, its version for Windows, macOS, iOS, Android, Linux and ChromeOS.
• Classifies each entry as desktop, mobile, tablet or bot using device and platform signals.
• Checks specific signatures before generic ones so Edge and Opera are not misreported as Chrome.
• Processes an entire pasted list at once and returns a clean, sortable, exportable table of results.
• Runs entirely in your browser with no upload, keeping log data and visitor details private.

How to use User Agent Parser

1. Copy user-agent strings from your server logs, analytics or browser developer tools.
2. Paste them into the input box with one complete string on each line.
3. Read the table to see the detected browser, version, operating system and device for each entry.
4. Sort or scan the columns to find outdated browsers, unexpected bots or specific platforms.
5. Copy or download the table to include the parsed results in a report or spreadsheet.

Benefits

• Support engineers quickly understand which browser and OS a user reported an issue from.
• Developers audit access logs to see which platforms and versions they most need to test against.
• Analysts summarise visitor technology without pasting each string into an opaque external service.
• QA teams reproduce bugs by identifying the exact browser and device behind a failing request.
• Site owners spot crawler and bot traffic that should be treated differently from real visitors.
• Because parsing is local, sensitive log data and visitor strings never leave your browser.

A user-agent string is a single line of text that a browser includes with requests to describe itself, but it is riddled with legacy tokens for historical compatibility. Almost every modern browser still contains the words Mozilla and often Safari or Chrome, which is why naive detection so often gets it wrong. This parser orders its checks from most specific to least specific so the true browser wins.

Version detection reads the number that follows the browser's own token, giving you a quick way to flag clients running old, potentially insecure releases. Operating-system detection recognises the common Windows, macOS, iOS, Android, Linux and ChromeOS markers and, where the string includes them, extracts version numbers, converting the underscore-separated Apple format into familiar dotted numbers along the way.

All analysis runs in your browser and nothing is transmitted, so the tool is safe for confidential server logs and internal analytics. User-agent strings can be spoofed and new browser builds appear constantly, so treat the results as a strong heuristic rather than a guarantee. For high-stakes decisions, combine this with client hints or server-side signals rather than relying on the user agent alone.