User-Agent Parser
Parse a User-Agent string into a practical browser, operating system, device, engine, and bot summary.
Ready to use
Browser-side · no account · results stay on this page
A User-Agent parser summarizes broad browser, OS, device, and bot signals.
Exact User-Agent interpretation can be messy, so use the result as a practical QA aid.
Use raw log values
Paste the full User-Agent string from logs or browser tools.
Treat result as a hint
Compatibility tokens can make exact detection ambiguous.
Example
Chrome on macOS is identified from Chrome and Mac OS X tokens.
Assumption
The string follows common browser User-Agent patterns.
Limitation
Spoofed, unusual, or very new User-Agent strings may not be exact.
Support
Summarize browser reports.
Logs
Inspect request metadata.
Bot checks
Spot obvious crawlers.
QA
Compare device signals.
Does this identify every browser reliably?
No. It is a lightweight parser for QA notes, not a full user-agent database.
Can it detect bots?
It flags common bot words such as bot, crawler, spider, and related tokens.
How is the User-Agent string processed?
Parsing is handled in the browser for this tool based on the current public implementation.
Why are User-Agent strings hard to parse?
Many browsers include compatibility tokens and overlapping engine names, so exact detection requires careful review.
Does this identify every browser reliably?
No. It is a lightweight parser for QA notes, not a full user-agent database.
Can it detect bots?
It flags common bot words such as bot, crawler, spider, and related tokens.
How is the User-Agent string processed?
Parsing is handled in the browser for this tool based on the current public implementation.
Why are User-Agent strings hard to parse?
Many browsers include compatibility tokens and overlapping engine names, so exact detection requires careful review.
Suggested workflow
Request debugging workflow
Parse User-Agent, inspect headers, then check URL details.