User-Agent Parser
Parse user-agent strings to identify browser, OS, device type, and rendering engine instantly in your browser
Paste any user-agent string to parse its components
What is a User-Agent String?
A user-agent string is an HTTP header sent by browsers and applications to identify themselves to web servers. It contains information about the browser, operating system, device type, and rendering engine. Web developers use this information for browser compatibility checks, analytics, and debugging.
How to Use
- Paste a user-agent string into the input field, or click "Use My Browser's UA" to auto-fill
- The parsed components appear instantly in the labeled fields below
- Copy any individual field using the "Copy" button next to it
Examples
Chrome on Windows:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36Parsed: Browser = Chrome 120.0.0.0, OS = Windows 10/11, Device = Desktop, Engine = Blink
Safari on iPhone:
Mozilla/5.0 (iPhone; CPU iPhone OS 17_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.1 Mobile/15E148 Safari/604.1Parsed: Browser = Safari 17.1, OS = iOS 17.1, Device = Mobile, Engine = WebKit
Googlebot:
Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)Parsed: Browser = Googlebot 2.1, Device = Bot
Understanding User-Agent Structure
A typical user-agent string follows this pattern:
Mozilla/5.0 (platform; details) engine/version browser/version- Mozilla/5.0: A legacy compatibility token present in virtually all modern browsers
- Platform: Operating system and hardware info (e.g., "Windows NT 10.0; Win64; x64")
- Engine: The rendering engine (AppleWebKit, Gecko, Trident)
- Browser: The actual browser name and version
Browser Detection Order
Because browsers include each other's tokens for compatibility, detection order matters. This parser checks: Edge → Opera → Chrome → Firefox → Safari. Edge and Opera both include "Chrome" in their UA strings, so they must be matched first to avoid false identification.
Privacy and User-Agent Reduction
User-agent strings contribute to browser fingerprinting. Modern browsers are reducing the information in UA strings through initiatives like User-Agent Client Hints (UA-CH). Chrome has been progressively freezing parts of the user-agent since 2022, replacing detailed platform info with generic values to improve user privacy while still allowing servers to request specific details when needed.
Frequently Asked Questions
What information can be extracted from a user-agent string?
A user-agent string typically contains the browser name and version, operating system and version, device type (desktop, mobile, tablet, or bot), and the rendering engine (Blink, Gecko, WebKit, or Trident). This tool extracts all of these components.
Why do some browsers report multiple browser names in the user-agent?
Modern browsers include legacy tokens for compatibility. For example, Chrome includes "Safari" and "AppleWebKit" in its UA string because early websites checked for these tokens. Edge includes "Chrome" because it uses the same engine. The parser handles this by checking browsers in specificity order: Edge → Opera → Chrome → Firefox → Safari.
Is my user-agent string sent to any server?
No, all parsing happens entirely in your browser using client-side JavaScript. Your user-agent string never leaves your device, ensuring complete privacy.
How does the parser detect bots and crawlers?
The parser checks for known bot signatures like Googlebot, Bingbot, YandexBot, DuckDuckBot, and others before attempting browser detection. Bot user-agents typically include the bot name followed by a version number.
What are the privacy implications of user-agent strings?
User-agent strings can contribute to browser fingerprinting, allowing websites to track users without cookies. This is why browsers are gradually reducing the information in UA strings through initiatives like User-Agent Client Hints (UA-CH). Chrome has been freezing parts of the UA string since 2022.