User-agent parser — Guide
Detect and parse Browser, Engine, OS, CPU, and Device type/model from an user-agent string.
What it is and when to use it
Paste a user-agent string and get its structure parsed into browser, engine, OS, CPU and device fields. Essential when triaging analytics, writing UA-based routing rules, or checking what a crawler's UA actually declares before you trust it.
Identifies the browser, engine, operating system and device type from a User-Agent string.
How to use it
- Paste a UA string, or fill in the current browser in one click
- Read the parsed information
- Copy the fields you need
A worked example
Fill in a sample UA
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
Copy this into the tool, or open User-agent parser
Things that trip people up
- A UA string can be forged, so it suits statistics and display but never security decisions
Questions people ask
- Can I trust the user-agent string?
- No — any client can send any string, and some browsers deliberately freeze or spoof parts of it. Treat parsed UA data as a hint for statistics and routing, never as an authentication factor.
- Why does the device field say "generic" on desktop?
- Desktop browsers do not report a device model at all, so the parser can only say the class. Detailed device names appear mostly for mobile UAs.
- How do I recognise a bot?
- Bots usually announce themselves (Googlebot, bingbot) and often lack a full engine/version structure. Parse the string and check whether browser and engine fields look coherent — missing pieces are a strong bot signal.
Next steps
Open the User-agent parser tool
- HTTP status codes
- HTTP status checker
- HTTP headers & request methods
- Device information
- MIME types
- Basic auth generator
Spotted something wrong on this page? Tell us via Contact Us