Développeurs

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.

Résumé de l'outil

Cet outil accepte une entrée structurée et renvoie une sortie déterministe dans le navigateur, sans envoi au serveur.

Nom de l'outil: User Agent Parser
Intention d'entrée: Fournissez le contenu source à transformer, valider ou analyser.
Intention de sortie: Recevez une sortie normalisée prête à être copiée, réutilisée ou déboguée.
Entrée d'exemple: 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
Sortie d'exemple: 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
}

Introduction à l'outil

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

Vue d'ensemble de l'outil

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.

Cas d'usage

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.

Exemples d'entrée/sortie

Intention d'entrée

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

Intention de sortie

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

Questions fréquentes

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.