User Agent Parser
Decode user agent strings into browser, OS, device, engine, and bot details.
User Agent Parser
Parse a browser or bot user agent string into browser, operating system, rendering engine, architecture, and device type details.
Common uses
- Debug browser-specific reports
- Inspect server logs and analytics exports
- Identify mobile, desktop, tablet, and bot traffic
How to use User Agent Parser
The user agent parser reads browser, operating system, device, engine, and bot details from a user agent string. It is useful for logs and support tickets.
Developers often use this page when they need user agent parser, user agent checker, parse user agent, and browser user agent parser.
Privacy and data handling
This tool is designed to run in your browser for normal use, so your input does not need to be sent to a server.
- Input and output stay on the page while you work.
- Copy buttons use your browser clipboard permission when available.
- Avoid pasting private production data on shared or untrusted devices.
Examples
Read a browser user agent
Input
Mozilla/5.0 Chrome/120.0 Safari/537.36Output
Browser: Chrome
Engine: Blink/WebKit-like
Device: desktop-likeUser agents are clues, not proof. They can be spoofed or reduced for privacy.
Steps
- 1Paste a user agent string.
- 2Review the detected browser, OS, and device.
- 3Use the result as a clue, not as a perfect identity.
Common use cases
- Debug browser-specific reports.
- Inspect user agents from server logs.
- Check whether a request may be from a bot.
Practical tips
- User agent strings can be spoofed.
- Modern browsers may reduce detail for privacy.
- Use feature detection in apps when possible.
FAQ
Can user agent strings be trusted?
Not completely. They are useful clues, but clients can change or fake them.
What is a bot user agent?
It is a user agent string used by a crawler or automated client. Some identify themselves clearly, and some do not.