User Agent Parser
Paste a user agent string to see the browser, rendering engine, operating system, device, and versions behind it. Or load your own current UA with one click. It runs in your browser.
This user agent parser reads a UA string and tells you the browser, rendering engine, operating system, and device behind it. Paste any string to parse a user agent string straight from your logs, or press one button to look up your own current user agent. The detection is a hand-written regex table that runs in your browser, so nothing about your request is sent anywhere. Use it as a quick user agent lookup while debugging analytics, feature support, or a bug that only shows up on one browser.
How it works
- 1
Paste a UA string
Drop in any user agent string, or click the button to load your own current one.
- 2
Read the breakdown
The browser, engine, OS, device type, and version are pulled out and listed as you type.
- 3
Copy what you need
Each field has its own copy button, so you can grab just the browser or OS version.
Instant & 100% private — nothing is uploaded
Everything runs locally in your browser. Your code, text and files are processed on your own device and are never sent to a server — so there are no upload waits, no size limits from us, and nothing is ever stored or logged.
Frequently asked questions
- What is a user agent string?
- It’s the line a browser sends with every request to identify itself. It packs the browser name, version, rendering engine, and operating system into one string, which this user agent parser splits back apart.
- How do I find my own user agent?
- Click “Use my current user agent” and the tool fills in the string your browser is sending right now, then shows the parsed result. That’s the fastest user agent lookup for the device you’re on.
- Is the parsing done online or on my device?
- On your device. It’s a UA parser online in the sense that the page loads from the web, but the matching runs in your browser with JavaScript. No user agent string is uploaded.
- Why does my browser say it’s both Safari and Chrome?
- For historical compatibility, most user agent strings still carry tokens like “Safari” and “Mozilla” even on Chrome. The parser weighs the more specific tokens first so it reports the real browser.
- Can it detect bots and crawlers?
- Yes. Strings from Googlebot, Bingbot, and similar crawlers are flagged as a bot device type rather than a desktop or mobile browser.
- Can I trust the device model?
- Treat it as a best guess. Android strings often embed a model name this tool extracts, but many browsers hide or fake it, so the model can be blank.
More tools
More from the Hivly network
Free sister tools on our other sites.
