What Is My User Agent — View Your UA String

Your browser's User-Agent string

Share X / Twitter Facebook LinkedIn WhatsApp

How to use What Is My User Agent

Open the page — your user agent string appears automatically.
Copy the full string.
Use it for development, testing or support — the exact UA pinpoints your browser/OS combination.
For a friendly summary instead, use the What Is My Browser tool.

What is What Is My User Agent?

This tool shows your user agent string — the exact text your browser sends to identify itself to every website. It's a dense line like Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 that encodes your browser, version, operating system and rendering engine.

The user agent is what sites read to know who's visiting — and it's useful to developers, testers and support who need the exact raw string rather than a friendly summary. This displays yours precisely, ready to copy.

About the What Is My User Agent

Open the page and see your full user agent string, ready to copy.

Who needs the raw string: web developers — testing user-agent detection, debugging why a site serves different content to different browsers, and checking what their code will receive; QA and testing — verifying the exact UA in different browsers and devices, and confirming user-agent-based logic works; support and bug reports — the precise UA string pinpoints the exact browser/OS/version combination when reproducing issues; and curiosity — seeing the (frankly bizarre) string every browser sends.

Why user agents look so strange: the "Mozilla/5.0" at the start of nearly every modern browser's UA is historical baggage — browsers have impersonated each other for compatibility for decades, so the string is a fossil record of browser politics rather than clean identification. This is why user-agent detection is fragile (browsers lie in the UA), and why the web is slowly moving toward better mechanisms (Client Hints). For a friendly interpretation of your browser rather than the raw string, see our What Is My Browser tool; for the broader picture of what sites detect, What Is My Screen Resolution and What Is My IP Address. The privacy note: your UA is one component of browser fingerprinting — sites combine it with other signals to identify visitors.

Frequently Asked Questions

The text your browser sends to every website to identify itself — encoding the browser, version, operating system and rendering engine. Sites read it to know who's visiting and potentially serve different content accordingly.

Historical baggage — browsers have impersonated each other for compatibility since the 1990s, so nearly all modern browsers claim "Mozilla" regardless of what they actually are. The UA string is a fossil of browser politics, not clean identification.

For testing UA-detection code, debugging browser-specific content serving, and precise bug reports (the exact UA pinpoints the browser/OS/version). Developers need the actual string, not a summary, to test what their code receives.

Yes — browsers offer UA switching, dev tools can override it, and privacy tools spoof it. This is why user-agent detection is unreliable (browsers "lie") and the web is moving toward Client Hints as a better mechanism.

Not alone — but combined with other signals (screen size, fonts, timezone) it contributes to browser "fingerprinting" that can identify and track visitors without cookies. It's one piece of the identifying picture sites can build.