User Agent Parser and Browser Detector

Paste a user agent string and read the browser, operating system, device type, a...

SecureFastFree

Updated

Parsed entirely in your browser with JavaScript. Nothing you paste is uploaded, logged, or sent to any server.

Quick answer

To parse a user agent string, paste it into the box and it is broken apart into four fields: the browser and version, the operating system and version, the device type (desktop, mobile, tablet, or bot) with any vendor and model, and the rendering engine such as Blink, WebKit, or Gecko. The parser uses ordered rules so the hard cases come out right: Edge, Opera, and Samsung Internet are told apart from Chrome, and Chrome on iOS is read from its CriOS token rather than mislabelled Safari. Everything runs in your browser with JavaScript, so the string you paste is never uploaded, and you can copy the full result as JSON.

SSL Secured
256-bit Encryption
Cloud Processing
Mobile Friendly

Parser Features

Browser and Version - Chrome, Edge, Firefox, Safari, Opera, Samsung Internet, IE, and more
OS and Version - Windows, macOS, iOS, iPadOS, Android, Chrome OS, and Linux
Device and Model - Desktop, mobile, tablet, or bot, plus vendor and model when present
Rendering Engine - Blink, WebKit, Gecko, and Trident with the engine version
Bot Detection - Googlebot, bingbot, YandexBot, and generic crawler patterns
Copy as JSON - One-click structured JSON of every parsed field

Why Use User Agent Parser and Browser Detector?

Browser and Version

See the browser name and exact version, with the tricky cases handled correctly: Edge and Opera are told apart from Chrome, and Chrome on iOS is not mistaken for Safari.

Operating System

Read the operating system and version, from Windows 10 and macOS to iOS, iPadOS, Android, Chrome OS, and Linux, with the Windows NT and Apple version numbers translated for you.

Device Type and Model

Classify the device as desktop, mobile, tablet, or bot, and pull the vendor and model when the string carries it, such as an Apple iPhone or a Google Pixel 7.

Rendering Engine

Identify the layout engine (Blink, WebKit, Gecko, or Trident) with its version, so you know what actually renders the page behind the browser name.

Bot and Crawler Detection

Spot search engine crawlers and automated agents such as Googlebot, bingbot, and YandexBot, with a clear BOT badge and the device type set to bot.

Nothing Leaves Your Browser

Every string is parsed on your device with JavaScript. It is never uploaded, logged, or stored, so you can safely paste real server logs or headers.

Common Uses for the UA Parser

Read Analytics and Logs

Turn raw user agent lines from access logs into readable browser, OS, and device data.

Reproduce Browser Bugs

Pin down the exact browser, version, and engine from a bug report so you can reproduce the issue.

Separate Bots From Users

Flag Googlebot, bingbot, and other crawlers in your traffic to keep analytics and rate limits honest.

Test Detection Logic

Confirm how your own server or client-side code will classify a given user agent before you ship it.

How It Works

1

Paste a user agent string

Paste a UA from a request header, a server log, or an analytics report into the box, or click Use my browser to fill in your own.

2

Read the parsed cards

The browser, operating system, device, and engine appear instantly in labelled cards, each with its version and any vendor or model that was found.

3

Copy the JSON

Copy the structured result as JSON with one click to drop into a test, a bug report, or your own code, or try a sample string to compare.

Tips and Notes

Try the Sample Strings

Use the sample buttons to see how Chrome, Safari, an iPhone, Android, Firefox, Edge, and Googlebot each parse, then compare the cards side by side.

Parse Your Own Browser

Click Use my browser to fill in your live user agent and see exactly what your browser reveals to every site you visit.

A UA Can Be Faked

User agents are easy to spoof, so never rely on them alone for security or access control. Treat the result as a strong hint, not proof of identity.

Frequently Asked Questions

Paste the user agent into the box on this page and it is broken apart at once into browser, operating system, device, and rendering engine. A UA string is a single line that a browser or bot sends with every request, and the parser reads it with an ordered set of rules: the most specific tokens are checked first so that, for example, Edge and Opera are not reported as Chrome. The whole thing runs in your browser, so nothing you paste is uploaded.
A user agent string is a line of text that a browser, app, or bot includes in the User-Agent header of every HTTP request to identify itself. It usually names the browser and version, the operating system, and sometimes the device model and rendering engine. Servers read it to serve the right content, gather analytics, or recognise crawlers, though it can be changed or faked, so it is a hint rather than proof.
Order is the whole trick. Edge, Opera, Samsung Internet, and Brave all include a Chrome token in their user agent because they are built on Chromium, so a naive parser calls them all Chrome. This tool checks the more specific markers first: Edg for Edge, OPR for Opera, and SamsungBrowser before it ever falls back to the Chrome token, so each browser is named correctly.
On iPhone and iPad every browser is required to use Apple's WebKit engine, so Chrome and Firefox on iOS still show a WebKit engine and a Safari token in their string; this parser reads the CriOS and FxiOS markers to still name the real browser. On desktop and Android, Chrome-family browsers use the Blink engine, which is why the engine card reads Blink even though the browser name is Chrome, Edge, or Opera.
Yes. The parser recognises common crawlers and automated agents including Googlebot, bingbot, YandexBot, DuckDuckBot, Applebot, and generic bot, spider, and crawler patterns. When one is found it sets the device type to bot and shows a BOT badge on the browser card, which is useful for reading server logs and separating real visitors from automated traffic.
Yes, because nothing is sent anywhere. All parsing happens locally in your browser with JavaScript, so the string you paste never leaves the page and is gone when you close the tab. That makes it safe to analyse real request logs, headers, or a customer's reported user agent without exposing any of it to a server.

Related Tools

JWT Decoder

Decode and inspect JSON Web Tokens

Regex Tester

Build and test regular expressions live

JSON Formatter

Format, validate, and beautify JSON

URL Encoder

Encode and decode URL components

Base64 Encoder

Encode and decode Base64 strings