🌐

User Agent Parser

Parse any user agent string into browser, operating system, device type and engine details. Shows your current UA automatically. Free, browser-based.

💻 Developer Tools Free Browser-based
Tool

What is a User Agent String?

Every browser sends a User-Agent HTTP header with each request, identifying the browser name and version, rendering engine, operating system and device type. Web servers and analytics tools use this string to tailor responses, track browser usage and diagnose compatibility issues.

Common User Agent Examples

BrowserUA Prefix
Chrome (Windows)Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36…
Safari (macOS)Mozilla/5.0 (Macintosh; Intel Mac OS X…) AppleWebKit/605…
FirefoxMozilla/5.0 (Windows NT 10.0; Win64; x64; rv:…) Gecko/…
Chrome (Android)Mozilla/5.0 (Linux; Android 14; Pixel 8) AppleWebKit…
GooglebotMozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

Tips

User agent strings are not tamper-proof — any user or bot can send an arbitrary UA. Do not rely on UA detection for security decisions. Use it for progressive enhancement, analytics and debugging only.

'This is a legacy compatibility token dating back to the Netscape era. Browsers kept it to avoid being blocked by servers that checked for the "Mozilla" prefix.'], ['q' => 'Is my data uploaded to a server?', 'a' => 'No. Everything runs locally in your browser using JavaScript. Your data never leaves your device.'], ['q' => 'Why is the UA detection sometimes wrong?', 'a' => 'User agent strings do not follow a strict standard. Browsers may mimic each other (e.g. Edge reports as Chrome), and bots may spoof UA strings to avoid detection.'], ['q' => 'Where can I find a request\'s user agent string?', 'a' => 'Open browser DevTools → Network tab → select any request → look for the User-Agent request header. Server-side, it is available as the HTTP_USER_AGENT environment variable.'], ]" />