User-Agent Parser
Parse a User-Agent string to identify the browser, operating system, rendering engine, and device type.
Recommended Settings
Pro Tips
- •This uses pattern matching against common User-Agent conventions - it covers the vast majority of real-world browsers and devices, but obscure or heavily customized UA strings may not parse perfectly
- •Many browsers deliberately include misleading tokens for legacy compatibility (Chrome's UA contains 'Safari', for example), so detection order matters and is handled here
- •Modern browsers are increasingly reducing and 'freezing' User-Agent details for privacy, so parsed results may become less granular over time
- •Loaded by default with your own browser's UA string - paste in any UA string from a server log to analyze a different visitor
Most Popular
Most developers paste a User-Agent string from their server access logs to quickly identify what browser and OS a visitor was using
When to Use This Tool
Parse a raw User-Agent string from an access log to see what browser and OS a visitor used.
Confirm exactly which browser and version a bug report's User-Agent string corresponds to.
See how your own browser and device are identified from your current User-Agent.
Learn how browser, OS, and engine details are encoded within a User-Agent string.
How It Works
Check the User-Agent string against known browser signature patterns in the order that correctly distinguishes overlapping tokens
Extract the operating system and its version from known OS signature patterns
Determine device type (mobile, tablet, or desktop) from device-specific keywords in the string
100% Private
Files never leave your device. All processing happens locally in your browser.
Lightning Fast
Powered by Client-side regex-based User-Agent parsing for optimal performance on modern browsers.
Open Source
Built with verified, open-source libraries. Fully transparent.
Frequently Asked Questions
Why does Chrome's User-Agent contain 'Safari'?
For historical compatibility reasons, most browsers include tokens from earlier browsers in their User-Agent string. This tool checks for more specific, distinguishing tokens first to correctly identify the actual browser.
Can a User-Agent string be spoofed?
Yes, easily - browsers allow developer tools and extensions to override the reported User-Agent, so it should never be treated as a reliable security signal.
Why is the OS version missing for Linux?
Linux User-Agent strings generally don't include a specific distribution or kernel version, unlike Windows, macOS, iOS, and Android.
Is my User-Agent string sent anywhere?
No. All parsing happens locally in your browser.