User-Agent parser
ClientPaste a full User-Agent header to see structured browser, engine, OS, and device fields—no network request.
User-Agent
?
Parsed locally—paste a UA from server logs or DevTools. Redact internal build tokens if you share screenshots.
- Browser
- Chrome (120.0.0.0)
- Engine
- Blink (120.0.0.0)
- OS
- macOS (10.15.7)
- Device
- Macintosh · Apple
- CPU
- —
Common use cases
- Decode User-Agent strings from server logs to see browser family, OS, and device class.
- Compare what your app thinks the client is versus what DevTools reports.
- Sanity-check bot or crawler signatures when filtering traffic.
Common mistakes to avoid
Trusting User-Agent for security decisions alone
Clients can spoof the header. Use it for analytics and hints, not for authentication.
Expecting stable strings forever
Browsers freeze or reduce detail over time. Log raw strings but avoid brittle substring checks.
Confusing engine and browser brands
Many browsers share an engine. Read both engine and product fields when diagnosing issues.
FAQ
Is the User-Agent sent to Toolcore?
No. Parsing happens locally after you paste.
Why does my browser show a simplified UA?
Modern browsers may send a reduced string for privacy. Your logs may differ from older documentation.
Can I get geolocation from the UA?
Not reliably—use explicit location APIs or server-side geo where appropriate.
More tools
Related utilities you can open in another tab—mostly client-side.
HTTP status codes
ClientHTTP response status reference: search 1xx–5xx, short meanings, copy status lines—client-side.
HTTP methods
ClientGET, POST, PUT, PATCH, DELETE—safe, idempotent, body usage—quick reference for APIs, client-side.
MIME types & file extensions
ClientLook up common MIME types from extensions (and vice versa)—filterable table, copy Content-Type—client-side.
JWT decode
ClientInspect JWT header and payload as JSON in browser; signature not verified.