User-Agent Parser
NetworkParse User-Agent strings into browser, OS and device info with Chrome, Firefox and Safari detection, and flag likely bots for cleaner traffic and log analysis.
Chrome · 120.0.0.0Blink · 120.0.0.0Windows · 10Desktopamd64Related Tools
About User-Agent Parser
The User-Agent string a browser sends crams the OS, browser, engine, and device into one long line that's hard to read. This tool parses UA strings locally in your browser, identifying browser name and version, rendering engine, operating system, and device type — useful for analyzing access logs, debugging compatibility issues, or auditing analytics. For example, pasting a Chrome UA string identifies the browser, version, OS and device type without reading fields by hand.
How to Use
- Open the User-Agent Parser tool
- Enter the address or query parameters
- Adjust the output options as needed
- Click the Query button; results appear in real time
- Copy or export the result
Use Cases
- Log analysis — Extract browser and OS distribution from server access logs to understand your audience.
- Compatibility triage — Paste a reporter's UA to confirm whether their browser version triggers a known bug.
- Device routing — Determine if a UA is phone, tablet, or desktop to validate responsive or redirect logic.
- Bot detection — Tell a real browser apart from a crawler or bot UA with telltale signatures.
- Analytics check — Verify your own tracking classifies browser versions the same as a standard parser.
- Support ticket triage — Parse a UA string from a bug report to immediately identify the browser and OS the user is on.
- Feature flag targeting — Check how a UA string is classified to verify feature-flag or A/B test targeting rules.
FAQ
Can I trust the UA string?
No. A UA can be freely spoofed by users or scripts, so it must not drive security decisions — only statistics and compatibility hints.
Why do so many UAs contain Mozilla/5.0?
A historical artifact. To pass early browser sniffing, every browser kept the Mozilla prefix; today it is a meaningless compatibility token by convention.
Can it identify the exact phone model?
Some Android UAs include a model string that can be read; iOS devices report only iPhone/iPad for privacy, so the specific model cannot be distinguished.
Why does Chrome's UA mention Safari and AppleWebKit?
Chrome uses Blink, derived from WebKit, and keeps the AppleWebKit and Safari tokens for compatibility with legacy sniffing — this is normal.
Is the UA being phased down?
Yes. Major browsers are rolling out User-Agent Reduction and Client Hints, removing some details from the UA string over time, so analytics should adapt.