UA Parser

Parse User-Agent strings online to identify browser, OS, and device information

User-Agent
Characters: 0

Parsed Results

Paste a User-Agent string here...

What is User-Agent?

User-Agent is an HTTP request header string that identifies the browser, operating system, and device information of the client making the request. Web servers analyze UA strings to determine the visitor's device type and provide appropriately formatted content. UA strings typically contain browser name and version, rendering engine, operating system, and other details.

How to Use

Basic Operations

  1. Paste the User-Agent string you want to parse in the input box
  2. Or click "Parse My UA" to auto-detect your current browser's UA
  3. Parsed results will display below with browser, system, and device details
  4. Click "Copy UA" to copy the original UA string

Features

Browser DetectionIdentify Chrome, Firefox, Safari, Edge and other major browsers with versions
OS DetectionDetect Windows, macOS, Linux, iOS, Android and other operating systems
Device DetectionIdentify desktop, mobile, tablet devices with vendor and model info
Bot DetectionRecognize Googlebot, Bingbot and other search engine crawlers

Common UA Examples

Chrome Browser

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 Chrome/120.0.0.0 Safari/537.36

iPhone Safari

Mozilla/5.0 (iPhone; CPU iPhone OS 17_0 like Mac OS X) AppleWebKit/605.1.15 Version/17.0 Mobile/15E148 Safari/604.1

Google Bot

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

Frequently Asked Questions

Q: Why are UA strings so long?

A: UA strings contain multiple layers of information: browser compatibility identifiers (like Mozilla/5.0), system information, browser engine and version. This is due to the historical evolution of browser compatibility in web development.

Q: Can UA strings be faked?

A: Yes, UA strings can be easily modified or spoofed. Most browsers allow users to modify their UA, and there are browser extensions specifically for switching UAs. Therefore, UA should not be used as the sole basis for identity verification.

Q: Why do some browsers have similar UAs?

A: Many browsers use the same rendering engines (e.g., Chrome and Edge both use Blink, Safari and Chrome both list WebKit), and include other browser identifiers for compatibility, resulting in similar UA strings.