What Is My User Agent
Your user agent
Detecting…
Read locally from your browser. Nothing is uploaded.
How to use
- Open the page — your full user agent string appears at the top right away.
- Click Copy to put the exact string on your clipboard for a bug report, header config, or test.
- Read the parsed breakdown below to see how browsers interpret your string into browser, engine, and OS.
FAQ
What is my user agent string?
Your user agent is the identifying text your browser attaches to every HTTP request. The full string is shown at the top of this page and can be copied with one click.
What does a user agent contain?
It typically lists a Mozilla compatibility token, the platform/OS, the rendering engine, and the browser with its version — for example the WebKit or Gecko engine and a Chrome, Safari, or Firefox version.
How is this different from the User Agent Parser tool?
This page shows your own browser's user agent automatically and parses it. The User Agent Parser is built for analyzing any string you paste in — for example UAs pulled from server logs or other users.
Why does my user agent look reduced or generic?
Chromium and other browsers now freeze or reduce user agent detail for privacy, replacing fine-grained version and platform data with rounded values. The string here reflects exactly what your browser sends.
Can I change my user agent?
Yes — browser dev tools and extensions can spoof it. If you have spoofing enabled, this page will show the spoofed value, because it reads whatever your browser currently reports.
Is anything sent to a server?
No. The string is read with navigator.userAgent in your browser and parsed locally. Nothing is uploaded or stored.
Introduction
What Is My User Agent shows the exact user agent string your browser is sending right now, front and center, with a one-click copy button. Below it, a parsed breakdown translates that dense string into the browser, engine, and operating system it represents.
The user agent is one of the most-requested pieces of information in support and QA: it travels with every request, and it is what servers use to tailor responses or log who visited. Reading yours should not require opening developer tools — this page surfaces it instantly.
What is a user agent?
A user agent string is a single line of text identifying the client software making a web request. A typical desktop Chrome UA looks like:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
The pieces, roughly, are:
| Segment | Meaning |
|---|---|
Mozilla/5.0 |
Legacy compatibility token present in nearly every UA. |
(Windows NT 10.0; …) |
Platform and OS details. |
AppleWebKit/537.36 (KHTML, like Gecko) |
Rendering engine lineage. |
Chrome/124.0.0.0 |
The actual browser and version. |
Safari/537.36 |
Another compatibility token for WebKit heritage. |
Common use cases
- Bug reports — paste your exact UA so developers reproduce the issue against the right client.
- Header configuration — copy a real UA when configuring tests, scrapers, or API clients responsibly.
- Verifying spoofing — confirm a dev-tools or extension UA override is actually taking effect.
- Analytics debugging — match what your analytics tool recorded against your real string.
Best practices
- Copy the full string rather than retyping it — UAs are long and a single wrong character changes how it parses.
- Remember the UA can be spoofed or reduced; treat it as a hint, not proof of identity.
- To analyze user agents that are not your own (from logs, for example), use the dedicated user agent parser.
- For a friendly, version-first view of just your browser, see what is my browser; for the full environment, open device info.