UA

User-Agent Parser

Parse browser, OS, device from UA string

API & HTTP
🔒 100% client-side — your data never leaves this page
Maintained by Evan•Updated: September 30, 2026
Options
Input

Paste one User-Agent string and check browser, OS, and device type first; scenario switching is available in Advanced mode.

Output
Browser—
Browser version—
OS—
Device type—
Engine—
🔒 Processed locally in your browser
Page reading mode

The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.

About this tool

Infer browser family, version, OS, device class and engine from common User-Agent tokens. Results are heuristics for reading logs, not verified device identity, bot detection or feature support. Input is saved as a local browser draft and can be cleared.

Production Snippets

Compatibility tokens require ordered interpretation

text

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 Chrome/120.0.0.0 Safari/537.36 OPR/106.0.0.0
Browser: Opera
Version: 106.0.0.0
Engine: Blink (inferred)

Frequently Asked Questions

Why can Chrome appear inside an Opera or Edge UA?

Chromium-based browsers include compatibility tokens. The parser checks Edge and Opera before generic Chrome; the presence of Chrome alone is not enough to label the browser.

Can Safari on iPhone be recognized?

The parser checks the Version and Safari tokens even when a Mobile token sits between them. It also recognizes common iOS browser tokens; these describe the supplied string and cannot prove the actual installed software.

Is the detected device or engine definitive?

No. UA reduction, spoofing and desktop-mode tablets can hide details. Unrecognized clients may show Unknown, and this tool does not retrieve Client Hints or probe browser capabilities.

Is parsing enough for feature detection or bot blocking?

No. Test the required feature in the browser, and use server-side evidence for abuse controls. A UA string can be copied by another client and is not a trusted identity signal.

Where does the pasted UA go?

Parsing runs locally. The page stores the text and options in localStorage so it can restore a draft; Clear removes the saved text. This storage is separate from sending a request to the UA’s claimed browser or device.

Keep browsing