What Is My User Agent
Instantly check your user agent string and decode it into plain English — browser name and version, operating system, device type, and rendering engine. Read locally in your browser, never stored, with one-click copy. Note that UA strings can be spoofed and are increasingly reduced for privacy.
Read Locally
Nothing leaves your browser
Your user agent is read directly from your browser on this page and never stored or sent to a server. Note that UA strings can be spoofed, and modern browsers increasingly freeze or reduce them for privacy — so the breakdown below is a best-effort guess, not proof of identity.
How to use this tool
Open the Page
Your user agent is read automatically the moment the page loads — no input needed. A 'detecting' state shows briefly before it appears.
Read the Breakdown
See the full raw string up top, then a parsed grid showing your browser, version, operating system, device type, and rendering engine.
Copy if Needed
Tap the copy button to grab the exact string for a bug report, support ticket, or compatibility test.
Remember UA strings can be spoofed by extensions and are increasingly frozen or reduced for privacy — treat the breakdown as a best-effort guess, not proof of identity.
What This Tells Sites
Every request your browser makes sends this string. Sites use it to serve the right layout, detect old browsers, and gather analytics — but it is one of many signals, not a reliable fingerprint.
Why It May Be Wrong
UA strings can be edited, faked by extensions, or frozen to a generic value. Chrome's reduced UA and Safari's frozen string mean the version you see may not be your exact build.
What Is My User Agent?
Every time your browser loads a page, it quietly introduces itself with a line of text called the user agent string. This tool reads that string the instant the page opens, displays it in full, and decodes it into a friendly breakdown: your browser and version, operating system, device type, and rendering engine. You can copy the raw string with one click — handy for bug reports, support tickets, or testing how a site behaves for a specific browser.
What Each Part of the Breakdown Means
A raw UA string looks intimidating, but it packs four useful facts:
- Browser & version — which program is making the request (Chrome, Firefox, Safari, Edge, Opera, Samsung Internet) and its version number. Support teams often ask for this first.
- Operating system — Windows, macOS, Linux, Android, iOS or ChromeOS, sometimes with a version. It tells a site what platform conventions to expect.
- Device type — desktop, tablet or mobile, inferred from tokens like
MobileandiPad. This drives responsive layouts and app-store prompts. - Rendering engine — the part that actually draws the page: Blink (Chrome, Edge, Opera), WebKit (Safari), or Gecko (Firefox). Engine quirks explain why a site can look slightly different across browsers.
Why You Would Check It
Developers check the user agent constantly: to reproduce a bug a user reported, to confirm which engine is rendering a layout, or to test that feature-detection and analytics are working. Non-developers find it useful too — when a website tells you to "update your browser" or an app shows a strange layout, copying your exact UA string into a support message saves a long back-and-forth. It is also a quick sanity check after installing a UA-switching extension to confirm the override actually took effect.
Why the Result Can Be Misleading
Here is the important caveat: the user agent is not trustworthy. It can be edited by extensions, overridden in developer tools, or set to anything by automated tools and scrapers. Browsers also include legacy tokens — almost every UA still claims to be "Mozilla" and "like Gecko" for ancient compatibility reasons — so the raw text mentions browsers you do not use. Treat the breakdown as a well-informed guess, never as proof of identity.
Reduction, Freezing and the Future
To curb fingerprinting, browsers are deliberately making UA strings less specific. Chrome's User-Agent Reduction trims the minor version and exact OS build down to rounded values, and Safari froze its string years ago. The long-term replacement is User-Agent Client Hints, a structured API that sites must explicitly request rather than receiving everything by default. That is why the version this tool shows may be rounded — your browser is intentionally telling sites less than it used to.
Privacy: Read Locally, Nothing Stored
This checker runs entirely in your browser. The UA string is read from navigator.userAgent on page load and parsed on your device — it is never uploaded, logged, or stored. You can use it on a private or work machine without anything leaving your computer.
For more on the technical side of your setup, pair this with the JSON formatter when you are debugging API responses that vary by client. Knowing your exact browser and engine makes it far easier to explain — and reproduce — the issues you run into.