User Agent Parser

Your data never leaves your browser

Parse a user agent string into browser, engine, OS, and device type.

Brie — Bug Reporting Tool

Found a bug while testing?

Brie captures screenshots, console logs, network data, and session replays in one click — so developers get the full context without the back-and-forth.

Install Brie — It's FreeLearn more →

About User Agent Parser

Paste any User-Agent string and instantly see its structured breakdown. The tool detects the browser name and version (Chrome, Firefox, Safari, Edge, Opera, Samsung Internet, UC Browser), the rendering engine (Blink, Gecko, or WebKit), the operating system and version (Windows 10/11, macOS, Linux, Android, iOS, iPadOS), and the device category (Desktop, Mobile, or Tablet). Useful for debugging cross-browser issues, reading server logs, and verifying test environment configurations.

How to use

  1. Paste a User-Agent string into the input panel.
  2. The parsed components appear immediately in the output panel.
  3. Copy individual values or the full breakdown for use in bug reports or logs.

More QA & Testing Tools

HTTP Status Code Reference

Browse the complete reference of HTTP status codes grouped by category.

Cookie Parser

Parse raw Cookie or Set-Cookie header strings into a readable table with decoded values.

cURL to Code

Convert a cURL command into JavaScript fetch, Python requests, or Node.js axios code.

Frequently Asked Questions

FAQs about User Agent Parser

What is a User-Agent string?

A User-Agent string is a text identifier sent by browsers and HTTP clients in request headers. It tells servers which browser, operating system, and device the client is using so the server can tailor its response.

Which browsers are detected?

The tool detects Chrome, Firefox, Safari, Microsoft Edge, Opera, Samsung Internet, and UC Browser, along with their version numbers.

How is device type determined?

Device type is inferred from keywords in the UA string: "Mobi", "iPhone", "iPod", and "BlackBerry" indicate Mobile; "iPad" and Android tablets without "Mobile" indicate Tablet; everything else is classified as Desktop.

Why does Chrome show a Safari token?

Chrome and most Chromium-based browsers include "Safari/537.36" in their UA string for historical compatibility reasons. The parser detects the Chrome-specific "Chrome/" token first to correctly identify the browser.

Is the parsed data sent anywhere?

No. Parsing happens entirely in your browser using JavaScript. No data is transmitted to any server.