What Is My User Agent
See your browser user-agent string plus local browser, platform, language, and screen details.
- Free, no account
- No watermark
- No usage limit
About the What Is My User Agent
Your user agent is a line of text your browser announces itself with on every request, and on its own it reads like alphabet soup. Most "what is my user agent" pages just print that soup and stop, but this one reads it for you. It shows the raw string, then parses it into the parts you actually want, the browser and version, the rendering engine, the operating system, and the device type, so you're not squinting at tokens trying to remember which slash means what.
Then it goes a step the string alone can't. Modern browsers have been quietly freezing the old user agent so it leaks less about you, which also means it now hides your real OS version and CPU. So this tool also reads User-Agent Client Hints, the structured data your browser hands over when a page asks, and that's where the accurate values are now, including your true OS version and CPU. All of it runs in your browser. Nothing about your setup is uploaded, logged, or sent to a server, which is more than the popular parser sites can manage, since they read your string on their end.
And you're not stuck with your own browser. Paste any user agent, out of a log file or a bug report or an API client, and the same parser decodes it. That turns this into a proper user agent parser you can share, decoded link and all.
How to use
- Open the page. It reads your own browser the moment it loads and fills in the breakdown. You'll see a quick "Detecting..." flash first.
- Read the parsed breakdown. Browser and version, engine, operating system, and device type, all pulled out of the string so you don't decode it by eye.
- Check the Client Hints panel. If your browser exposes them (Chrome, Edge, and other Chromium browsers do, Firefox and Safari don't yet), you get the accurate platform version, full browser version, and CPU architecture. That's the section to trust when the parsed OS looks stale.
- Copy what you need. "Copy string" grabs the raw user agent for a bug report. "Copy full report" grabs the whole decoded summary, breakdown and Client Hints together.
- Decode someone else's UA. Paste any user agent into the box and the breakdown switches to it. Clear the box to snap back to your own browser.
- Share the result. Share copies a link that reopens the exact user agent you decoded, with that string held after the
#, which is the one part of a web address a browser never sends to a server. Embed drops the live tool onto your own page, and it deliberately leaves the pasted string behind, since an embed becomes published HTML that every visitor to that page can read.
What the breakdown is actually telling you
A user agent packs four different facts into one line, and they answer different questions. The browser and version is the obvious one, and it's about the only token in the whole string you can mostly trust. The rendering engine, Blink or WebKit or Gecko, is the part that decides how a page actually draws, and for anything CSS related it matters more than the brand. Chrome, Edge, Opera, Brave, they're all Blink, so a bug in one usually turns up in the rest.
The operating system and the device type round it out. A modern Chrome string still claims to be "Mozilla," "AppleWebKit," and "Safari" all at once, and the tool sorts that out for you. Those are leftover compatibility words browsers copied off each other since the 90s so old servers wouldn't hand them a broken page. Only the "Chrome/131" style token names the real thing, and the parser shows you that one. Which is why seeing "Safari" in a Chrome user's string is normal and nothing to worry about.
Where the honest answer moved: Client Hints
For years the user agent quietly grew longer and leakier, and it became a fingerprinting signal that helps narrow a browser toward one person. So Chrome and the other Chromium browsers started reducing it, freezing the OS version and trimming the precise numbers. The side effect is that the string now reports some values inaccurately on purpose. Your Mac reports "Mac OS X 10_15_7" no matter which macOS you're really running. Windows 10 and Windows 11 both send the identical "Windows NT 10.0," so the string genuinely cannot separate them.
User-Agent Client Hints are the replacement, and this tool reads them. Instead of one crowded line, your browser keeps the precise pieces (real platform version, CPU architecture, full browser version, device model) as clean, labeled values. The sensitive ones only go out when a site actually asks, so nothing leaks by default. When your browser supports Client Hints, that panel is the part to believe. It reads the real macOS version behind the frozen 10_15_7, and it's the only reliable way to tell Windows 11 from Windows 10 inside a browser. Firefox and Safari don't expose the detailed pieces yet, so on those the parsed string stays your best read.
Decoding a user agent that isn't yours
The box near the bottom takes any user agent, not just your own. Paste one out of a server log, a crash report, or whatever an API client is sending, and it runs through the same parser. This is what makes it a real user agent parser rather than a mirror, and it helps when a customer says "it's broken" and the only clue you have is the string from their session.
One honest limit, since it always comes up. A pasted string is just text, so the device guess is only as good as the string itself. The classic trap is the iPad, which since iPadOS 13 reports itself as desktop macOS and drops the "Mobile" word, so a real iPad can read as a Mac. Your own browser can catch that with touch support. A bare string can't, not here and not on the big parser sites. Treat the device type as a strong hint rather than a certainty.
Frequently asked questions
Why does my browser and version look right but the OS version is wrong?
Because the operating-system part of the string is deliberately frozen. Chrome on an Apple Silicon Mac still says "Intel Mac OS X 10_15_7," and every Windows 10 and 11 machine sends the same "Windows NT 10.0." The browser token was never frozen, so it stays current while the OS token is stuck on purpose. The Client Hints panel shows the real platform version whenever your browser supports it.
Is anything I paste or check sent to a server?
No. The whole thing runs in your browser, and nothing you check or paste is uploaded or logged. That's a real difference from many parser sites, which receive your string on their servers to decode it. Here the decode happens locally, so a paste from a private log never leaves your computer. Pressing Share is the only thing that moves the string anywhere, and even then only into the link you just copied, where it rides after the # and stays invisible to every server on the way. Whoever you hand that link to can read it, which matters because a user agent names your OS build, your browser build, and anything your employer bolted onto it. The Embed code leaves it out completely.
What is a rendering engine, and why care about it more than the browser name?
The engine turns code into what you see, and it decides how CSS and JavaScript behave. Blink powers Chrome, Edge, Opera, and most Chromium browsers. WebKit powers Safari and every browser on iPhone and iPad. Gecko powers Firefox. It's more useful to test by engine than by brand name, since browsers on the same engine behave almost identically.
Why do Chrome and Firefox on my iPhone show WebKit instead of their own engine?
Apple requires every browser on iOS and iPadOS to use its WebKit engine underneath, so Chrome, Firefox, and Edge on an iPhone are really WebKit wearing a different label. The tool detects this and reports WebKit for iOS browsers, which is the accurate answer even though the brand token says Chrome or Firefox. On Android and desktop those same browsers use their own engines.
Can I change or fake my user agent?
Yes. Browser developer tools let you override it, extensions can swap it with a click, and many phone browsers have a "Request Desktop Site" toggle that does the same. If you've turned any of that on, the tool shows the spoofed value, because it reports whatever your browser presents. Spoofing is handy for testing and for getting past sites that wrongly block a browser, but it won't hide you from fingerprinting, and faking it while logging into a bank can trip fraud checks.
How do I read my user agent straight from the browser console?
Open developer tools (F12, or Ctrl+Shift+I, or Cmd+Option+I on a Mac), go to the Console, type navigator.userAgent, and press Enter. For the structured Client Hints, type navigator.userAgentData in a Chromium browser. This page does both for you, but the console is handy when you're already in devtools.
Does a user agent identify me personally?
Not by itself. Millions of people send the identical "Chrome on Windows" string, so on its own it's closer to knowing the model of a car than knowing the driver. It becomes a fingerprint only when stacked with other signals like your address on the network, screen size, installed fonts, and language. Trimming the string and moving detail into Client Hints, which only go out on request, is meant to shrink exactly that risk.