User Agent Parser
Parse browser User-Agent strings online to inspect browser name, version, operating system, rendering engine, and device classification.
Run tool
This online User Agent Parser breaks down raw User-Agent header strings into structured client details. When you paste a header value into the input field and run the parser, it evaluates the text against ordered pattern rules to identify the client browser, operating system, rendering engine, and device type. The parser recognizes major desktop and mobile browsers such as Chrome, Firefox, Edge, Opera, and Safari, alongside operating systems including Windows, macOS, Linux, Android, and iOS. It extracts dotted software release numbers whenever the pattern provides them. It also classifies the hardware form factor as Desktop, Mobile, or Tablet, and detects automated web crawlers or bots based on specific keywords. If any component is missing or does not match a recognized pattern, the tool displays Unknown for that category. Submitting an empty field displays an error notice with an example string to help you test valid header formats immediately.
Instructions
- Paste or type a complete browser User-Agent header string into the User Agent input box.
- Click the run button to analyze the header text.
- Review the resulting breakdown of browser, operating system, rendering engine, and device category.
Examples
- Input: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36. Output: Chrome 122.0.0.0 on Windows 10.0, Blink engine, Desktop device.
- Input: Mozilla/5.0 (iPhone; CPU iPhone OS 17_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4 Mobile/15E148 Safari/604.1. Output: Safari on iOS 17.4, WebKit engine, Mobile device (mobile device: Yes).
FAQ
How does the tool distinguish between browsers with overlapping tokens?
The parser uses ordered pattern checks. For instance, Chrome signatures require the Chrome token while explicitly excluding Edge, Opera, and Chromium signatures, ensuring multi-token strings resolve accurately.
Why do some fields display Unknown in the output?
When a header omits specific information or uses an unrecognized format, the tool assigns Unknown to the unidentified browser, version, engine, or operating system field.
How does the tool identify web crawlers and bots?
The parser checks for terms like bot, crawler, or spider in the string. If found, it assigns the device category Bot/Crawler and shows the bot indicator as Yes.
What happens if I submit an empty input?
Submitting an empty field produces an error message with a sample User-Agent string instead of a parsed result.