TextArray
100% local

User-agent parser

Decode user-agent strings into browser, engine, OS and device type.

Input
Output

User-agent parser

Paste a user-agent string and this tool breaks it down into the browser and its version, the rendering engine, the operating system and the device type. It reads the strings you meet every day in server logs, bug reports, analytics exports and support tickets — and because every non-empty line is parsed as one user agent, you can drop in hundreds of log lines at once and get a numbered breakdown for each.

Detection covers the browsers that matter in real traffic: Chrome, Safari, Firefox, Edge, Opera, Samsung Internet, Vivaldi, UC Browser and Internet Explorer, plus common bots and crawlers such as Googlebot, Bingbot, GPTBot, ClaudeBot, curl and wget. The engine (Blink, WebKit, Gecko, Trident, EdgeHTML), the OS with its version (Windows, macOS, iOS, Android, ChromeOS, Linux) and the device class — desktop, mobile, tablet or bot — come out alongside. Switch the output format to JSON to feed the parsed records into a script or a spreadsheet.

A user-agent string is a hint, not the truth. Modern browsers freeze or reduce parts of it, iPads on iPadOS 13 and later introduce themselves as Macs, and client hints have replaced much of what the string used to carry. When a field cannot be read with confidence, the tool says Unknown rather than guessing.

Everything runs locally in your browser. Log lines often sit next to IP addresses and other personal data, so nothing you paste here is ever uploaded — the parsing happens on your device and the text never leaves it.

FAQ

Why does a field say Unknown?
The tool only reports what the string actually contains. Rare browsers, trimmed log fields and made-up user agents simply do not carry the token being looked for, and guessing would be worse than admitting it.
Can a user-agent string lie?
Yes, easily. Any client can send any string, browsers freeze or reduce parts of it, and iPads on iPadOS 13+ report themselves as Macs. Treat the result as a strong hint, not as proof.
Why is the JSON output in English?
JSON is data for machines — scripts, dashboards and spreadsheets expect stable field names and values. The text format is the one that follows your interface language.
Can I parse many user agents at once?
Yes. Each non-empty line is parsed as one user agent, so you can paste a whole column exported from your logs and get a numbered block per line.
Are my log lines uploaded anywhere?
No. The tool runs entirely in your browser, which matters here: log excerpts often contain IP addresses and other data you should not paste into random web services.