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

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

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.

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.

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

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.

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.