SmartKitio

User-Agent Parser

Paste a User-Agent string to extract a browser version token, a rendering-engine guess, the first OS fragment in the parentheses, and whether the string looks mobile.

Your input stays in your browser. Nothing is uploaded.

This looks up codes locally. It does not fetch a remote URL.

Browser
—
Engine
—
OS
—
Mobile
No

About this tool

The parser is a small set of regular expressions, not a full UA database. It looks for Edg, OPR, Chrome, Firefox, Safari, or SamsungBrowser plus a version, then guesses Gecko, WebKit, or Blink from other tokens. The OS field is the first clause inside the parentheses, so it is a hint, not a normalised name. Chromium-based browsers still contain “Chrome/”, and many mobile strings contain “Safari/”, so the first listed match can be surprising. Nothing is fetched; the text never leaves this tab.

How to use it

  1. Paste a User-Agent from DevTools, a log file, or navigator.userAgent.
  2. Read the browser token, engine, OS fragment, and mobile flag.
  3. Treat the result as a starting point. Confirm unusual clients against the raw string.

When to use it

  • Reading a UA from server logs
  • Checking what your own browser sends

Examples

  • Chrome on Windows

    A typical Windows Chrome string reports Chrome/version, Blink, and an OS fragment that starts with “Windows”.

  • Empty input

    An empty string returns blank fields and mobile = false.

FAQ

Is this as accurate as ua-parser-js?
No. It is a lightweight guess for common desktop and mobile browsers, not a maintained device catalog.
Does it send the string to a server?
No. Parsing is local.
Why might Edge show as Chrome?
Older matching order can prefer Chrome/ when it appears first. Check the raw string for Edg/.