What Is My User Agent
See the exact user agent string your browser sends with every request, decoded into the browser, rendering engine, operating system and device it identifies.
Your browser's user agent
This string is read directly from your browser on this page - it is not logged or sent to our servers by this tool.
Reading user agent…
About What Is My User Agent
Every request your browser makes carries a User-Agent header: a single line of text that identifies the browser and version, the layout engine that renders pages, and the underlying operating system. Servers read it for content negotiation, analytics and compatibility decisions. This tool reads that exact string from your browser's navigator.userAgent property and shows it to you verbatim, character for character.
Below the raw string, the tool decodes four facets. The browser (Chrome, Firefox, Safari, Microsoft Edge, Opera, Samsung Internet or Internet Explorer), the rendering engine (Blink, Gecko, WebKit or Trident), the operating system (Windows, macOS, iOS, iPadOS, Android, ChromeOS or Linux) and the device class (desktop or laptop, mobile, or tablet). The classic user agent string is deliberately messy for historical reasons, which is why the near-universal Mozilla/5.0 prefix tells you almost nothing on its own.
The whole process happens locally in your browser. The string is read and parsed on this page and is not logged or transmitted to our servers by the tool. That matters because the user agent is one of the signals used in browser fingerprinting. For the same reason, modern browsers now freeze or reduce parts of the string and move precise details into User-Agent Client Hints, so the version numbers shown here may be approximate rather than exact.
Knowing your user agent is useful whenever a problem depends on the browser and OS combination. It gives you the precise text to paste into a bug report, confirms which rendering engine is behind a CSS or JavaScript quirk, and lets you verify that a device-emulation override in developer tools is actually taking effect.
How to use it
- 1Open the tool. Your browser's user agent string appears automatically, read directly from navigator.userAgent.
- 2Read the full string in the monospace box and copy it into a bug report or support ticket if needed.
- 3Review the decoded panel to see the detected browser, rendering engine, operating system and device type.
- 4Switch browser or device and reload the page to compare how different clients identify themselves.
Common use cases
- -Filing a bug report that requires the exact browser and OS combination
- -Confirming which rendering engine (Blink, WebKit or Gecko) a browser uses when debugging CSS or JavaScript quirks
- -Checking whether a device reports itself as mobile, tablet or desktop during responsive testing
- -Verifying that a user agent override or developer-tools device emulation is actually being applied
- -Learning how a real-world user agent string is structured
Frequently asked questions
- What is a user agent string?
- A user agent string is a line of text your browser sends in the User-Agent HTTP header on every request. It names the browser and version, the rendering engine and the operating system so servers can tailor their responses.
- How do I find my user agent?
- Open this page and your user agent appears automatically, read from your browser's navigator.userAgent property. No extension or installation is required.
- What is the difference between the browser and the rendering engine?
- The browser is the application you use, such as Chrome, Firefox or Safari, while the rendering engine is the component that turns HTML and CSS into pixels, such as Blink, Gecko or WebKit. Different browsers can share one engine: Chrome, Edge and Opera all use Blink.
- Why does my browser version look generic or slightly wrong?
- Chrome, Edge and Safari now freeze or reduce parts of the user agent for privacy, moving precise details into User-Agent Client Hints. As a result the version shown here can be approximate.
- Is my user agent unique to me?
- Not by itself, since many people share the same string. Combined with other signals, however, it can contribute to browser fingerprinting, which is why modern browsers deliberately reduce the detail they expose.
- Does this tool send my user agent anywhere?
- No. The string is read and decoded entirely in your browser on this page and is not logged or transmitted to our servers by the tool.