User-Agent Parser
Parse a User-Agent string into browser, OS, and device details.
Runs locally in your browser. Your input is not uploaded or stored. You can verify this in your browser’s network panel.
What does this tool solve?
Paste a User-Agent string to break it into structured Browser, Engine, OS, Device, and CPU fields — or click “Use my browser” to inspect your own.
What examples should you start with?
Chrome on Windows
Input
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 … Chrome/126.0.0.0 Safari/537.36
Output
Chrome 126.0 · Blink · Windows 10/11 · Desktop
Googlebot
Input
Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Output
Bot / crawler — with a spoofing warning
How does it work?
Parsing is heuristic: ordered rules match product tokens, engine markers, platform hints, device fields, and CPU architecture.
Everything happens locally; your User-Agent is never sent anywhere by this page.
What are the edge cases and limits?
- User-Agent strings are free text and trivially spoofed — never use them for security decisions.
- Client hints and UA reduction mean modern browsers increasingly report frozen or generic values.
- Unusual clients (bots, libraries, embedded webviews) may resolve to Unknown with a note.
Technical reference
Related tools
- URL Encoder / DecoderEncode and decode URL components and query strings safely.
- HTML Entity Encoder / DecoderEncode and decode HTML entities for safe markup display.