User Agent Parser

Parse user agent strings into structured components. Identify browser, operating system, device type, rendering engine, and architecture.

Your Current User Agent:

User Agent String:

Try a sample:

How It Works

A user agent string is an identifier that HTTP clients send with every request to tell the server what software is making the request. This parser breaks it down into structured fields.

Token Structure

A typical UA string is a sequence of product tokens in the format Name/Version, sometimes followed by parenthesized comments:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Mozilla/5.0 — Compatibility token (nearly universal)
(Windows NT 10.0; Win64; x64) — Platform comment with OS and architecture
AppleWebKit/537.36 — Rendering engine token
(KHTML, like Gecko) — Compatibility comment
Chrome/131.0.0.0 — Browser product token
Safari/537.36 — Legacy compatibility token

Detected Fields

Field	Description
Browser	Name and version of the web browser (Chrome, Firefox, Safari, Edge, etc.)
Operating System	OS name and version (Windows, macOS, Linux, Android, iOS)
Device	Device type (Desktop, Mobile, Tablet, Console, Bot)
Engine	Rendering engine (Blink, WebKit, Gecko, Trident)
Architecture	CPU architecture (x86_64, ARM64, ARM, x86)

Common Rendering Engines

Blink — Chrome, Edge, Opera, Brave (based on WebKit)
WebKit — Safari, older Chrome
Gecko — Firefox
Trident — Internet Explorer
EdgeHTML — Legacy Microsoft Edge

Why User Agents Matter

Content Negotiation: Servers can deliver different content based on browser capabilities
Analytics: Track browser and device usage statistics
Compatibility: Detect and work around browser-specific issues
Security: Identify potentially malicious bots or scrapers

Limitations

UA strings can be freely spoofed by the client
Many browsers disguise themselves as others for compatibility
Modern browsers are freezing UA strings in favor of User-Agent Client Hints (Sec-CH-UA headers)
Feature detection is preferred over UA sniffing for web development

Feedback

Help us improve this page by providing feedback, and include your name/email if you want us to reach back. Thank you in advance.

Share with