What Is My User Agent
Instantly see the full user agent string your browser is sending right now, and decode it into a clean table — browser, operating system, engine, and device type. It runs entirely in your browser, so nothing leaves your device.
What is the What Is My User Agent tool?
Every time your browser opens a web page, it quietly sends a line of text called a user agent that introduces itself to the server. The what is my user agent tool reads that exact line straight from your browser and then decodes it into a clean human-readable breakdown of your browser, operating system, rendering engine and device type. Instead of squinting at a cryptic string full of slashes and version numbers, you get a tidy table that tells you what you are actually running — plus a one-click button to copy the raw string when you need it.
How to use it
- Open the page. The tool reads your user agent automatically, on the spot — there is nothing to type and no button to start.
- Read the raw user agent string at the top, then scan the decoded table below it: browser name and version, OS and version, engine, device type, and whether you are on mobile or desktop with touch support.
- Click Copy raw string to put the raw string on your clipboard, ready to paste into a bug report, a support ticket, or a compatibility test.
That is the whole flow — get your answer in a second and move on.
The method behind it
A user agent string has a loose, historical structure. It almost always
begins with Mozilla/5.0, followed by platform details in
parentheses, then a list of engine and browser tokens such as
AppleWebKit, Gecko, Chrome,
Safari, Firefox, or Edg. These tokens
were copied between browsers over decades so that older servers would not
wrongly block a "new" browser — which is why the string looks messy and
lists names that seem contradictory.
This tool parses that string locally. It looks for known browser and engine
tokens and their version numbers, matches platform keywords like
Windows NT, Mac OS X, Android,
iPhone or Linux to an operating system, and infers
device type. When your browser supports the modern
navigator.userAgentData interface (User-Agent Client Hints,
which deliberately sends less detail by default), the tool uses that richer,
structured data too. All of this runs in your browser using
navigator.userAgent and related APIs — nothing is uploaded.
Examples
- A Windows laptop in Chrome might show a raw string like
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0 Safari/537.36, which decodes to Chrome 120 · Windows 10 · Blink engine · Desktop · no touch. - An iPhone in Safari might decode to Safari 17 · iOS 17 · WebKit engine · Mobile · touch enabled, even though the raw string still contains the word
Mozilla.
Common use cases
- Compatibility troubleshooting — confirm which browser and version you are testing in before filing a "works on my machine" report.
- Bug reports and support tickets — paste an accurate user agent so developers can reproduce the issue on the right platform.
- Confirming your device or browser — quickly verify whether you are on mobile or desktop, or which OS version you are running.
- Crawler and scraper debugging — check what UA your automation or headless browser is presenting to servers.
Why use this one
Most "user agent" pages just dump the raw string and stop there. This one decodes it into the details that actually matter, runs entirely in your browser so nothing leaves your device, requires no sign-up, and stays mobile-first and clutter-free. It sits alongside a couple of related network checks: What Is My IP for your public address and What Is My Screen Resolution for your display details.
Frequently asked questions
What is a user agent?
A user agent is a line of text your browser sends with every request to identify itself to web servers. It typically names the browser, its version, the operating system, and the rendering engine, so sites can serve the right content and layout for your setup.
Where does this tool get my user agent from?
It reads the navigator.userAgent property (and the newer navigator.userAgentData when your browser supports it) directly in your browser. Nothing is sent to a server, so the result is exactly the string your browser would send to any website.
Why does my user agent mention Chrome, Safari and Mozilla all at once?
For historical compatibility reasons, browsers copied tokens from each other so old servers would not block them. That is why almost every UA string starts with Mozilla/5.0 and may list multiple engine names. Our decoder reads past the noise and shows the browser you are actually using.
Can I change or fake my user agent?
Yes. Browser dev tools and extensions let you override it for testing, and some privacy tools spoof it. The new User-Agent Client Hints mechanism also lets browsers send less detail by default. This tool always reports whatever your browser is currently presenting.
Is the result private?
Yes. Detection happens entirely on your device using browser APIs. We do not log, store, or transmit your user agent. Refresh the page and the data is gone.