User Agent Detection
This is the exact user agent string your browser sent to load this page, with the browser, operating system and device it reveals.
Your user agent is shown in the box below, read directly from your browser via navigator.userAgent — the same string sent in the User-Agent header of every request you make. Underneath it, we break it down into the browser, operating system and device type that websites infer from it.
The full string is what every website you visit receives. The parsed rows are our interpretation of it: browser name and major version, operating system, and whether the string marks itself as mobile, tablet or desktop.
Windows 10 and Windows 11 both send "Windows NT 10.0" in the user agent, and macOS has reported "Mac OS X 10_15_7" for years regardless of the real version. Chromium browsers also freeze the minor version to .0.0.0. A frozen or generic value in your result is normal — it is your browser reducing what it shares, not a detection error.
If your result shows a different browser or OS than you expect, a user-agent override is usually the cause: DevTools device emulation, "Request desktop site" on a phone, or a privacy extension.
Support teams often ask for it when a site misbehaves in one browser, because it pins down the exact browser version and platform in one line. Use the copy button and paste the string into your ticket.
Developers use it to confirm what a test device or emulator is actually reporting, and to check whether an override in DevTools took effect.
Detection happens locally in your browser. The string is not stored or sent anywhere by this page beyond the normal request your browser already made to load it.
Microsoft never changed the version token for Windows 11, so both Windows 10 and 11 report "Windows NT 10.0". The user agent alone cannot tell them apart. Chromium-based browsers can reveal the difference through User-Agent Client Hints, which our OS check uses when available.
Yes, most browsers allow you to modify your user agent through developer tools or extensions. This is often used for testing how websites appear on different browsers or devices, or for privacy purposes.
For historical reasons, browsers often include other browser names in their user agent strings for compatibility. For example, Chrome includes 'Safari' and 'Mozilla' because early websites used these strings to detect browser capabilities.