Developer

User Agent Parser

Decode any User-Agent string into a clean breakdown — browser, engine, OS, device, and version — for log triage, bug reports, and analytics QA.

Tool Summary Answer Block

This tool accepts structured input and returns deterministic output in the browser with no server upload.

Tool name: User Agent Parser
Input intent: Provide source content to transform, validate, or analyze.
Output intent: Receive normalized output suitable for copy, reuse, or debugging.
Example input: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4 Safari/605.1.15
Example output: browser: Safari 17.4 engine: WebKit 605.1.15 os: macOS 10.15.7 device: Desktop

User-Agent stringDrop file

Presets:

Browser

Safari

17.4

Engine

WebKit

605.1.15

Operating system

macOS

10.15.7

Device

Desktop

—

JSON view

Parsed JSONRead-only

{
  "browser": {
    "name": "Safari",
    "version": "17.4"
  },
  "engine": {
    "name": "WebKit",
    "version": "605.1.15"
  },
  "os": {
    "name": "macOS",
    "version": "10.15.7"
  },
  "device": {
    "type": "Desktop",
    "model": "",
    "vendor": ""
  },
  "isBot": false
}

Tool Introduction

Decode any User-Agent string into a clean breakdown — browser, engine, OS, device, and version — for log triage, bug reports, and analytics QA.

Tool Overview

The User-Agent header is a historical mess: every browser claims to be Mozilla, lots of stacks lie about who they are, and important hints are hidden in trailing tokens. This parser uses a sequence of well-known signatures (in the right order) to identify the real browser and engine, then extracts the OS and the device type. It surfaces the parts that matter — browser, engine, OS, device, raw version — and flags ambiguous strings instead of guessing wildly. Great for triaging support tickets and validating server-side analytics.

Use Cases

Triage a bug report by extracting the user’s browser and OS from a noisy UA string.
Quickly validate analytics dashboards against raw logs.
Build a quick allow/deny list by inspecting the UA your real users send.

Input/Output Examples

Input Intent

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4 Safari/605.1.15

Output Intent

browser: Safari 17.4
engine: WebKit 605.1.15
os: macOS 10.15.7
device: Desktop

FAQ

How accurate is the detection?+

For mainstream browsers and operating systems, very accurate. For obscure or spoofed UAs the parser will still surface what it can find and flag the rest as Unknown.

Can it detect bots and crawlers?+

Yes — known crawlers (Googlebot, Bingbot, AhrefsBot, etc.) are recognized and labelled as bots so you can filter them out of analytics.

Is anything sent to a server?+

No. UA parsing happens entirely in your browser; nothing is uploaded.