View all services
Talk to QA Advisor
Free tool · Browser and device

What is my user agent?

The exact user agent string your browser sends to every website, ready to copy, with the browser, operating system and device it describes. Where the string is deliberately vague, the real values from User-Agent Client Hints are shown alongside.

What is my user agent

Reading your browser’s details…

Ready
How to use

How to use the What is my user agent

  1. 1Open this page in the browser you want to check. The user agent string shows at the top.
  2. 2Copy it with the button, for a bug report, a test configuration or a server log search.
  3. 3Read the browser, operating system and device it identifies, and the note for anything the string gets wrong.
  4. 4Export the full environment if the bug report needs more than the user agent.

What a user agent string says

A user agent is a line of text the browser sends with every request, naming itself, its version, its rendering engine and the operating system. A typical one for Chrome on Windows reads Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36. Only "Chrome/141" and "Windows NT 10.0" carry real information; the rest is kept for compatibility with sites that check for older browsers.

Because of that history, almost every browser claims to be several others. Edge adds "Edg/", Opera adds "OPR/", and both still say Chrome and Safari. Parsers have to check for the most specific name first, which is a common source of bugs in analytics and browser detection code.

What the user agent now hides

Browsers have reduced the user agent to limit fingerprinting. Chromium browsers report the version as 141.0.0.0 rather than the full build. Every browser on Windows 11 reports Windows NT 10.0. Every browser on a Mac reports macOS 10.15.7, whatever the real version. Chrome on Android reports Android 10 and a device model of "K" for every phone.

Chrome, Edge, Opera and Samsung Internet expose the real values through User-Agent Client Hints, which a site has to ask for. This page asks, and shows the result. Firefox and Safari do not support client hints, so for those browsers the user agent is all there is.

Testing with user agents

Changing the user agent, in browser developer tools or a test framework, tests code that reads the string: server-side redirects to a mobile site, download pages that pick an installer, analytics, and feature blocks for old browsers. It does not make one browser behave like another, because the engine underneath is unchanged.

For device and browser bugs, test on the real browser or a cloud device rather than a spoofed user agent. Code that still parses the user agent for decisions is worth a test of its own, because the reduced strings above already break naive version checks.

QAble service

Compatibility testing

QAble tests browser detection, redirects and feature support on real browsers and devices, including the reduced user agents that break older parsing code.

Explore the service
FAQ

Frequently asked questions

What is my user agent?

It is shown at the top of this page, exactly as your browser sends it. Use the copy button to copy it without mistakes.

Why does my user agent say Mozilla?

For compatibility. Early websites sent better pages to browsers that said Mozilla, the code name of Netscape Navigator, so other browsers copied it. Every major browser still starts with Mozilla/5.0.

Why does Edge say Chrome in its user agent?

Edge is built on Chromium and includes "Chrome" so that sites written for Chrome treat it the same way. It adds "Edg/" with its own version, which is how it can be told apart.

What are User-Agent Client Hints?

A newer way for sites to ask for browser details. The browser sends a few basic values by default and more only when a site asks, such as the full version, the platform version and the device model. Chromium browsers support them; Firefox and Safari do not.

Can I change my user agent?

Yes. Chrome and Edge developer tools have a network conditions panel with a user agent override, Firefox has a setting in about:config, and test frameworks such as Playwright and Selenium set it per session. It changes what sites read, not how the browser behaves.

Need the edge cases found for you?

QAble testers work through the inputs, payment paths and data that break products in production, before your users find them.

Talk to QA Advisor