What Is My User Agent?

See your browser's user agent string and what it reveals about your browser, operating system, and device. This page now also parses your user agent into browser, version, OS, device type, rendering engine and CPU architecture - and lets you decode any user agent string you paste.

Your User Agent

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])

Parsed Breakdown

Browser
JavaScript required
Operating system
JavaScript required
Device type
JavaScript required
Rendering engine
JavaScript required
CPU architecture
JavaScript required

Parsed in your browser from the user agent above. The server only sees the raw string.

Parse a Custom User-Agent String

Decoded locally in your browser - the pasted string is never sent to our servers.

What is a user agent string?

A user agent string is a line of text your browser sends in the User-Agent HTTP header with every request. It identifies the browser and its version, the rendering engine, the operating system, and often the device type and CPU architecture, so servers can deliver compatible content and developers can troubleshoot.

How do I find my user agent?

The fastest way is to open this page - your user agent is shown above and parsed automatically. You can also check it manually in five steps:

  1. Open your browser's developer tools (press F12 or Ctrl/Cmd + Shift + I).
  2. Go to the Console tab.
  3. Type navigator.userAgent and press Enter.
  4. Read the string that is printed back.
  5. Alternatively, inspect the User-Agent request header in the Network tab.

What does a user agent reveal?

A user agent typically exposes the following details, which together help websites adapt content and help trackers fingerprint your browser:

  • Browser & version - e.g. Chrome 120, Firefox 121, Safari 17.
  • Rendering engine - Blink, WebKit, Gecko or Trident.
  • Operating system & version - Windows 10/11, macOS, Android, iOS, Linux.
  • Device type - desktop, mobile, tablet, or bot/crawler.
  • CPU architecture - 64-bit (x86_64), ARM, or 32-bit, when disclosed.

Why do user agents look so messy?

For historical compatibility, almost every browser still begins its user agent with Mozilla/5.0 and includes tokens like AppleWebKit, KHTML, like Gecko, and Safari even when it is not Safari. This "user agent string history" exists so old server-side sniffing code keeps serving modern features. Modern browsers are also reducing (freezing) user-agent detail in favour of the structured User-Agent Client Hints API.

Can I change my user agent?

Yes. You can override it from your browser's developer tools (Network conditions), with a browser extension, or in code via request headers. Spoofing the user agent can help test responsive layouts, but it does not hide your real browser from advanced fingerprinting, which combines many other signals.

The User-Agent header is defined in RFC 9110 (HTTP Semantics). The structured replacement, User-Agent Client Hints, is specified by the W3C.

Frequently Asked Questions

A user agent string identifies the browser, version, operating system, and device type making a web request. Every HTTP request includes a user agent header.

Sites use user agents for analytics, responsive design decisions, browser-specific features, bot detection, and serving mobile vs desktop content.

Yes, browser extensions and developer tools allow changing user agents. This is useful for testing how sites render on different browsers/devices without switching hardware.

Mobile user agents include keywords like 'Mobile', 'Android', or 'iPhone' and often specify device models. Desktop agents typically show the OS (Windows, Mac, Linux) and browser version.

User agents evolved to maintain backward compatibility. Modern strings include legacy tokens so older websites don't break. This 'browser history' makes them lengthy and redundant.

Yes, websites can block or restrict access based on user agents. This is commonly used to block bad bots, outdated browsers with security issues, or scrapers.

Frequently Asked Questions

What is a user agent string?
A user agent string identifies the browser, version, operating system, and device type making a web request. Every HTTP request includes a user agent header.
Why do websites check user agents?
Sites use user agents for analytics, responsive design decisions, browser-specific features, bot detection, and serving mobile vs desktop content.
Can I change my user agent?
Yes, browser extensions and developer tools allow changing user agents. This is useful for testing how sites render on different browsers/devices without switching hardware.
What's the difference between desktop and mobile user agents?
Mobile user agents include keywords like 'Mobile', 'Android', or 'iPhone' and often specify device models. Desktop agents typically show the OS (Windows, Mac, Linux) and browser version.
Why are user agent strings so long and complex?
User agents evolved to maintain backward compatibility. Modern strings include legacy tokens so older websites don't break. This 'browser history' makes them lengthy and redundant.
Can websites block certain user agents?
Yes, websites can block or restrict access based on user agents. This is commonly used to block bad bots, outdated browsers with security issues, or scrapers.
Last reviewed: Reviewed by the

How this tool works: This tool runs in your browser and on our server in real time. Depending on the tool, results are computed directly from the input you provide or retrieved from live, authoritative data sources at the moment you run a lookup. We do not sell your data, and your lookups are kept private — any history shown here is stored only on your device.