The parsed browser, engine, operating system and device appear here once you paste a User-Agent string.
A User-Agent parser reads the User-Agent request header a browser sends and breaks it into the browser name and version, the rendering engine, the operating system, and the kind of device the request came from. Every HTTP request carries this string, and it is the single most common way a server learns what is on the other end of a connection without asking. The header itself is defined in RFC 9110, the HTTP semantics specification, and its format is an unstructured list of product tokens and comments that has grown historically messy.
That messiness is the reason a parser exists. A modern Chrome string still begins with "Mozilla/5.0" and still contains the word "Safari", because browsers spent two decades copying each other tokens to pass server sniffing tests. Edge carries "Chrome", Opera carries "Chrome", and Safari on an iPhone reports its real version in a separate "Version/" token rather than the "Safari/" one. Reading a User-Agent by eye is therefore error-prone: the tokens that look most obvious are frequently the ones left in for backward compatibility rather than the ones that identify the actual client.
This tool applies the detection order those quirks demand. It tests for the browsers that embed another browser token first, so Edge is not misread as Chrome and a Chrome-on-iOS string is not misread as Safari. It maps the Windows NT kernel number to its marketing name, converts the underscore-separated iOS and macOS versions back to dotted form, and classifies the request as desktop, mobile, tablet, or bot. It also flags known crawler and automation signatures, which is the field most useful when you are reading a web-server access log rather than debugging a single browser.
Everything runs in your browser. The string you paste is never uploaded, which matters because a real User-Agent from your own traffic can hint at the exact device and build a visitor is using. There is no signup, no rate limit, and no network request, so you can paste production log lines without sending them anywhere.
Drop in a UA string from your access logs, a browser console (navigator.userAgent), or a request header. Or load one of the built-in samples.
The browser, engine, operating system, device type, CPU architecture and bot flag are detected instantly as you type. There is no button to press.
See at a glance whether the request came from a desktop, phone, tablet, or a crawler such as Googlebot, with the device model where the string exposes it.
Copy the parsed table as tab-separated text to paste into a spreadsheet, a bug report, or your log-analysis notes.
Tests Edge, Opera and Samsung before Chrome, and reads Safari from its Version/ token, so embedded compatibility tokens do not cause a misread.
Translates Windows NT kernel numbers to names, restores dotted iOS and macOS versions, and recognises Android, Chrome OS and Linux.
Labels each string as desktop, mobile, tablet or bot, and surfaces the Android or Apple device model when the User-Agent includes it.
Matches a broad set of search-engine, social and automation signatures such as Googlebot, Bingbot, curl and headless Chrome, for log analysis.
Turn a username and password into an HTTP Basic Authentication header, curl command and fetch snippet, and decode existing Basic auth tokens back.
Check one name across hundreds of TLDs at once. RDAP first, WHOIS fallback, and a verdict of available, taken or unknown — never a guess
Decode JWT headers and payloads, inspect claims, and check token expiry
Create soft-UI (neumorphic) elements with a live preview and controls for distance, blur, intensity, radius, surface color, and flat/concave/convex/pressed shapes - then copy the CSS.
0 comments
No comments yet. Be the first to share your thoughts!