Browser name + version, OS name + version, device category (desktop, mobile, tablet), and engine (WebKit, Gecko, Blink). The common fields.

Good for common browsers. Older or niche UAs (embedded devices, crawlers, custom UAs) may miss — the parser prioritizes the top 95% of traffic.

Known bot UAs (Googlebot, Bingbot, etc.) are flagged. Sophisticated bots that spoof a browser UA can't be detected from UA alone.

What about Client Hints?

Client Hints (Sec-CH-UA-*) are the modern replacement for User-Agent. The tool parses UA format; Client Hints are a separate header set.

User-Agent Parser | DevTools Surf

DevTools Surf

Example: User-Agent Parser

A worked example, rendered from real sample data. Sign in to run the tool on your own input.

Input

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Output

═══ Parsed User-Agent ═══
Browser: Chrome 120.0.0.0
Engine: Blink 120.0.0.0
Operating system: macOS 10.15.7
Device type: desktop
Vendor: Apple
Model: Mac
CPU architecture: unknown
Mobile: no
Bot or automation: no
Raw length: 117 characters

─── Findings ───
⚠ This is a reduced (frozen) User-Agent. Chrome 100+ freezes the platform, version and model tokens, so minor version, exact OS version and device model are no longer available here.
ℹ Request the high-entropy values through the Client Hints API (navigator.userAgentData.getHighEntropyValues) or the Sec-CH-UA-* request headers instead.
ℹ User-Agent is client-supplied and trivially forged — never use it for access control or security decisions.

─── Equivalent Client Hints ───
Sec-CH-UA: "Chrome";v="120", "Not?A_Brand";v="99"
Sec-CH-UA-Mobile: ?0
Sec-CH-UA-Platform: "macOS"
Sec-CH-UA-Platform-Version: "10.15.7"
Sec-CH-UA-Arch: "unknown"
Sec-CH-UA-Model: "Mac"
Sec-CH-UA-Full-Version-List: "Chrome";v="120.0.0.0"

About User-Agent Parser

User-Agent Parser preview - Networking tool

Parse browser, OS, device from a User-Agent string. Part of the DevTools Surf developer suite. Browse more tools in the Networking collection.

Use Cases

Analyzing server logs to identify browser version distribution
Detecting bot crawlers in web traffic analytics
Debugging browser-specific rendering issues from error reports
Parsing User-Agent headers for conditional feature detection

Tips

Paste a User-Agent string to identify browser and OS version
Detect mobile vs desktop devices from the parsed output
Identify bot traffic by recognizing crawler User-Agent patterns

Fun Facts

User-Agent strings became notoriously convoluted because browsers historically pretended to be other browsers to receive compatible content.
Chrome's User-Agent string includes 'Mozilla/5.0' and 'Safari' despite being neither, a legacy of the 'browser compatibility wars.'
Google proposed freezing the User-Agent string in 2020 with User-Agent Client Hints (UA-CH) to reduce fingerprinting surface.

FAQ

What does it parse?: Browser name + version, OS name + version, device category (desktop, mobile, tablet), and engine (WebKit, Gecko, Blink). The common fields.
How accurate is it?: Good for common browsers. Older or niche UAs (embedded devices, crawlers, custom UAs) may miss — the parser prioritizes the top 95% of traffic.
Does it detect bots?: Known bot UAs (Googlebot, Bingbot, etc.) are flagged. Sophisticated bots that spoof a browser UA can't be detected from UA alone.
What about Client Hints?: Client Hints (Sec-CH-UA-*) are the modern replacement for User-Agent. The tool parses UA format; Client Hints are a separate header set.

Related Networking Tools

IP Address Lookup HTTP Status Reference DNS Record Explainer WebSocket Frame Decoder Port Reference Lookup MIME Type Lookup Certificate Decoder HPKP Generator