All tools
All tools › User-Agent Parser ● Live Developer Tools

How User-Agent Parser works

  1. Paste a full user-agent string into the input box — for example, one copied from a server access log or a browser's DevTools network panel.
  2. Leave the box empty to instead inspect the user-agent of the browser tab you're currently using.
  3. Read the summary lines for Browser, OS, Device, and Engine, followed by the original raw string for reference.
  4. Copy the output with the Copy button to paste into a bug report, support ticket, or QA note.
  5. Repeat with different strings to compare how the same site is reported across browsers or devices.
  • Decode an unfamiliar user-agent string from a server access log while investigating a traffic spike or bot pattern.
  • Attach a readable browser/OS/device summary to a bug report instead of pasting the raw, hard-to-read UA string.
  • Confirm which browser and OS a customer was using from a support ticket that includes their user-agent.
  • Sanity-check analytics segment definitions by parsing sample user-agent strings from your own traffic logs.

The string you paste (or your browser's own user-agent if you leave it blank) is parsed entirely in your browser's memory using plain string matching — nothing is sent to a server.

  • Detection is based on substring matching against a small set of known tokens, not a full user-agent parsing database — uncommon or minority browsers will often show as Unknown.
  • It cannot detect bots, crawlers, or specific device models, and it cannot verify whether a user-agent string has been spoofed.
  • Browser and engine detection order can misclassify unusual combinations, since it checks for tokens like Edg/ and Chrome/ in a fixed priority sequence.

User-Agent Parser

User-Agent Parser extracts readable browser, operating system, device, and engine hints from a user-agent string. It is useful for logs, support tickets, QA, and analytics checks.

User-Agent Parser Runs locally

User-Agent Parser

Extract browser, OS, device, and engine hints from a user-agent string. Everything runs locally in this tab.

Output
Browser: Unknown
OS: Unknown
Device: Desktop
Engine: Unknown

Node.js/22
Similar tools

More Developer Tools tools

See all tools →
LiveDeveloper Tools

.dockerignore Generator

Generate .dockerignore rules to exclude unnecessary files from Docker images. Keep builds fast and images lean by specifying what Docker should ignore during COPY commands and build context.

dockerignoredockerbuild context
LiveDeveloper Tools

.gitignore Generator

Generate .gitignore files from templates for popular frameworks and languages (Node.js, Python, React, .NET, Go). Copy-paste ready for your project with no manual configuration needed.

gitignoregitnode
LiveDeveloper Tools

Base64 Encoder / Decoder

Encode text or files to Base64, or decode Base64 strings back to text.

base64encodedecode
LiveDeveloper Tools

Binary Text Converter

Convert plain text to binary and binary back to readable text.

binarytext encodingascii
LiveDeveloper Tools

chmod Calculator

Convert Unix permissions between rwx and octal notation.

chmod calculatorunix permissionslinux
LiveDeveloper Tools

Content Security Policy Generator

Build a starter Content Security Policy (CSP) header with preset rules for common scenarios. Understand CSP directives, generate production-ready headers, and improve website security against injection attacks.

cspsecurity headersweb security
Guide

How to use

  1. Paste a full user-agent string into the input box — for example, one copied from a server access log or a browser's DevTools network panel.

  2. Leave the box empty to instead inspect the user-agent of the browser tab you're currently using.

  3. Read the summary lines for Browser, OS, Device, and Engine, followed by the original raw string for reference.

  4. Copy the output with the Copy button to paste into a bug report, support ticket, or QA note.

  5. Repeat with different strings to compare how the same site is reported across browsers or devices.

Scenarios

Use cases

  • Decode an unfamiliar user-agent string from a server access log while investigating a traffic spike or bot pattern.

  • Attach a readable browser/OS/device summary to a bug report instead of pasting the raw, hard-to-read UA string.

  • Confirm which browser and OS a customer was using from a support ticket that includes their user-agent.

  • Sanity-check analytics segment definitions by parsing sample user-agent strings from your own traffic logs.

Good to know

Limitations & Privacy

Private by design

The string you paste (or your browser's own user-agent if you leave it blank) is parsed entirely in your browser's memory using plain string matching — nothing is sent to a server.

  • Detection is based on substring matching against a small set of known tokens, not a full user-agent parsing database — uncommon or minority browsers will often show as Unknown.

  • It cannot detect bots, crawlers, or specific device models, and it cannot verify whether a user-agent string has been spoofed.

  • Browser and engine detection order can misclassify unusual combinations, since it checks for tokens like Edg/ and Chrome/ in a fixed priority sequence.

FAQ

Frequently asked questions

Is User-Agent Parser free to use?

Yes. The tool is free and runs directly in your browser with no account required.

Does this tool upload my data?

No. Processing happens locally in the browser tab. Your input is not sent to a server.

What is this tool best for?

It is best for reading a raw user-agent string from a server log, support ticket, or analytics export and getting a readable browser/OS/device/engine summary in one pass.

What happens if I leave the input blank?

The tool falls back to your own browser's live user-agent string, so you can see how your current setup is detected before pasting one from elsewhere.

Which browsers and operating systems does it recognize?

It distinguishes Microsoft Edge, Chrome, Firefox, and Safari by checking for their distinct tokens (Edg/, Chrome/, Firefox/, Safari/), and detects Windows, macOS, Android, iOS, and Linux from standard platform substrings. Anything outside those patterns is reported as Unknown rather than guessed.

How does it tell WebKit/Blink apart from Gecko?

It looks for the AppleWebKit token (used by both Chromium-based browsers and Safari) versus the Gecko/ token used by Firefox. It does not distinguish WebKit from Blink specifically, since both share the AppleWebKit marker in their UA strings.

Can it parse spoofed or custom user-agent strings?

It parses whatever text you provide using substring matching, so a spoofed or hand-edited string will produce whatever result its tokens imply — the tool has no way to verify authenticity.

Does it identify bots, crawlers, or specific device models?

No. It only classifies device type as Mobile or Desktop using a simple pattern match. It does not have a bot/crawler signature database or a device-model lookup.