How do I use this User-Agent parser?

Paste a UA string (or click Use my browser / a sample agent). The page shows browser, engine, OS, device, and bot status immediately. Nothing is uploaded.

What is a User-Agent string?

It is the HTTP header browsers and clients send to identify themselves (browser, OS, engine, and sometimes device). Servers and analytics tools parse it for compatibility and traffic analysis.

Can it detect bots and crawlers?

Yes. Common crawlers such as Googlebot, Bingbot, GPTBot, and CLI clients like curl are flagged with bot = yes and a bot name when recognized.

Is my User-Agent uploaded?

No. Parsing runs only in this tab. Strings never leave your browser.

Will every UA parse perfectly?

No. User-Agent strings are informal and spoofable. This tool covers common browsers, OS values, devices, and bots; obscure or custom agents may show Unknown for some fields.

How do I parse my current browser?

Click Use my browser. The tool fills the input with navigator.userAgent from this tab and parses it locally.

Does this replace server-side UA libraries?

No. Use it for quick local inspection and log debugging. Production traffic classification should still use your server or CDN tooling.

How is this different from the Regex Tester?

The Regex Tester lets you write custom patterns. This page ships ready-made browser / OS / device / bot extraction for typical User-Agent strings.

Developer Tools

User-Agent Parser

Paste any HTTP User-Agent string and get browser, engine, operating system, device type, vendor/model when available, CPU architecture hints, and bot/crawler detection - entirely…

Parsing runs in your browser. User-Agent strings never leave this tab.

User-Agent string

Sample agents

Browser

Chrome 131.0.0.0

Engine

Blink 131.0.0.0

Operating system

Windows 10 / 11 (NT 10.0)

Device type

Desktop

Vendor

Not detected

Model

Not detected

CPU architecture

amd64

Bot / crawler

About User-Agent Parser

Paste any HTTP User-Agent string and get browser, engine, operating system, device type, vendor/model when available, CPU architecture hints, and bot/crawler detection - entirely in your browser. Use sample agents for Chrome, Safari, Firefox, Edge, Googlebot, Bingbot, GPTBot, and curl, or click Use my browser to parse the UA of this tab. Nothing is uploaded. Pair it with the Regex Tester when you are writing UA-matching rules, or the JWT Decoder for other request-header debugging.

How to Use User-Agent Parser

Paste a User-Agent string into the input, or click Use my browser.
Or pick a sample agent (Chrome, Safari, Firefox, Edge, Googlebot, Bingbot, GPTBot, curl).
Read browser, engine, OS, device type, vendor, model, CPU, and bot status.
Copy the summary when you need the fields in a ticket or log note.
Everything runs locally - the UA string never leaves this tab.

User-Agent Parser Examples

Chrome on Windows desktop

A modern Chrome Windows UA resolves to Chrome + Blink, Windows 10/11, desktop, and amd64 - with bot = no.

Safari on iPhone

An iPhone Safari UA shows Safari + WebKit, iOS, mobile device, Apple / iPhone.

Googlebot crawl string

Googlebot presets mark bot = yes, device type bot, and browser name Googlebot so you can confirm crawler logs.

GPTBot AI crawler

OpenAI GPTBot strings are flagged as bots with bot name GPTBot - useful when auditing AI crawler traffic.

curl CLI client

A bare curl/8.x UA is detected as a bot/client named curl with its version - common in API access logs.

Common Use Cases

Decode UA strings from access logs or CDN reports
Confirm Googlebot / Bingbot / GPTBot vs spoofed browsers
Check mobile vs desktop vs tablet for a captured UA
Document browser and OS versions for a support ticket
Test sample agents before writing UA-based feature flags

Frequently Asked Questions about User-Agent Parser

How do I use this User-Agent parser?: Paste a UA string (or click Use my browser / a sample agent). The page shows browser, engine, OS, device, and bot status immediately. Nothing is uploaded.
What is a User-Agent string?: It is the HTTP header browsers and clients send to identify themselves (browser, OS, engine, and sometimes device). Servers and analytics tools parse it for compatibility and traffic analysis.
Can it detect bots and crawlers?: Yes. Common crawlers such as Googlebot, Bingbot, GPTBot, and CLI clients like curl are flagged with bot = yes and a bot name when recognized.
Is my User-Agent uploaded?: No. Parsing runs only in this tab. Strings never leave your browser.
Will every UA parse perfectly?: No. User-Agent strings are informal and spoofable. This tool covers common browsers, OS values, devices, and bots; obscure or custom agents may show Unknown for some fields.
How do I parse my current browser?: Click Use my browser. The tool fills the input with navigator.userAgent from this tab and parses it locally.
Does this replace server-side UA libraries?: No. Use it for quick local inspection and log debugging. Production traffic classification should still use your server or CDN tooling.
How is this different from the Regex Tester?: The Regex Tester lets you write custom patterns. This page ships ready-made browser / OS / device / bot extraction for typical User-Agent strings.

JWT Decoder

Decode JWT header, payload, and signature in your browser. Encode HS256 test tokens on the same page. Free JSON Web Token decoder - nothing uploaded.

Regex Tester

Test JavaScript regular expressions in your browser. See match groups, flags, and highlights - nothing is uploaded.

Hash Generator

Generate SHA-256, SHA-1, SHA-384, and SHA-512 hashes from any text. HMAC lives on the same page. Get the lowercase hex digest instantly in your browser - nothing is uploaded.

Bcrypt Hash Generator

Free bcrypt hash generator and verifier in your browser. Hash passwords with configurable rounds, then verify hashes locally - nothing is uploaded.