User-Agent String Parser
Private by design — runs entirely in your browser
Parse any User-Agent string and see the browser, version, operating system, and device family in plain form. Toova works on every common UA pattern from desktop browsers to mobile apps to bots — all in your browser, with no upload.
Why parse User-Agents at all
User-Agent strings are a mess. They started as a short hint about which browser was making a request, but decades of compatibility hacks left them as long compound strings that include misleading names. Toova decodes the structure into a clean breakdown — browser name and version, OS name and version, device family, rendering engine — so you can debug feature detection, write analytics rules, or troubleshoot client compatibility.
Bots and unusual clients
Toova recognizes the major web crawlers (Googlebot, Bingbot, AhrefsBot, GPTBot, CCBot), common monitoring services, headless browser tools, and a long tail of API clients that announce themselves through the UA. That makes the tool useful when looking at log entries and trying to figure out whether a request came from a real user, a search engine, or an automated tool.
Local-only
All parsing happens in your browser. The UA strings you paste — which might be from your own logs and could reveal your service architecture — never leave the page. The Network tab will stay empty during parsing, and the page works offline after first load.
Frequently Asked Questions
- Why is the User-Agent string so long?
- Historical compatibility. Every browser added the names of older browsers to its UA so legacy sniffing scripts would not exclude them. The result is a chain of names that is technically a lie — Chrome announces itself as Mozilla, Safari, and KHTML in the same string.
- Can I trust the UA in production?
- Not entirely. The UA can be set to any value by the client, so it is fine for analytics and feature hints but unreliable for security decisions. Modern Chrome is also phasing parts of it out via the User-Agent Client Hints API.
- How does it identify bots?
- Toova maintains a list of known crawler and bot signatures (Googlebot, Bingbot, GPTBot, and many others). When the UA matches, the tool labels the entry and surfaces the official documentation link for that bot.
- What about mobile apps?
- Mobile apps usually include a custom UA segment with the app name and version, plus the platform OS. Toova parses common patterns and reports the app name when recognized; otherwise it falls back to OS-only detection.
- Is my data sent anywhere?
- No. Parsing happens entirely in your browser.