What Is My User Agent?

The User-Agent string your browser sends with every request, read from navigator.userAgent and split into browser, engine, operating system, device type and CPU architecture.

Analyzing your user agent...

Runs in your browser: your files and text are not uploaded. Free, no account needed.

Last updated: · Reviewed by the QuickTooly Team

Reading the string

Anatomy of a User-Agent String

Chrome on Windows sends a string like this: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36

  • Mozilla/5.0: a historical token that almost every browser sends. It tells you nothing.
  • (Windows NT 10.0; Win64; x64): the platform. Windows 10 and 11 both send NT 10.0.
  • AppleWebKit/537.36 (KHTML, like Gecko): compatibility tokens. Chromium browsers still send them although their engine is Blink.
  • Chrome/142.0.0.0: the browser and its version.
  • Safari/537.36: another compatibility token. It does not mean the browser is Safari.

How This Page Parses It

The parser runs simple text checks in a fixed order, and the order explains most odd results:

  • Browser: Edge (Edg/) and Opera (OPR/) are checked first, then Chrome and Firefox on iOS (CriOS/, FxiOS/), then Chrome, Firefox and Safari. Brave, Vivaldi and Samsung Internet send a Chrome string and show as Chrome.
  • Engine: any string with "Chrome/" that is not from an iPhone or iPad shows as Blink with the Chrome major version, because Chromium browsers render with Blink while still sending AppleWebKit/537.36. Every browser on iOS shows as WebKit. Firefox shows as Gecko with its rv: version.
  • Operating system: checked in the order Windows, Android, iPhone, iPad, Mac OS X, Linux. Android strings also contain "Linux" and iPhone strings contain "like Mac OS X", so the more specific names are checked first. The macOS version is read with dots or underscores.
  • CPU: x64 from x86_64, Win64 or WOW64, and ARM from "ARM". Macs send "Intel" even on Apple silicon, so a Mac shows Unknown.

User-Agent Reduction and Client Hints

Chrome and Edge send a reduced string. The version always ends in 0.0.0, macOS is always 10_15_7, and on Android the version and model are replaced by "Android 10; K". The full version, platform version and device model are only available through User-Agent Client Hints: the Sec-CH-UA request headers, or navigator.userAgentData in JavaScript. This page does not read Client Hints, so it shows only what the reduced string contains. Firefox and Safari do not support Client Hints.

Using the String Safely

  • Do not use it to decide which features to use. Test for the feature instead, as the Test Features button does for each API it lists.
  • Anyone can change it with DevTools device mode or an extension, so never rely on it for security decisions.
  • For logs and analytics, use a maintained parser; hand-written checks like the ones above fail in the ways listed.

User Agent Questions

Why does my Chrome version end in 0.0.0?

Chrome reduced its User-Agent string. Only the major version is real; the rest is always sent as 0.0.0. The full version is available through User-Agent Client Hints, which this page does not read.

Why does my Android string also say Linux?

Android runs on the Linux kernel, so its User-Agent string includes the word Linux. The parser checks for Android before Linux, so the phone shows as Android with device type Mobile.

Why does Chrome send AppleWebKit if it uses Blink?

Chromium browsers still send the AppleWebKit/537.36 token for compatibility. The parser reports Blink for any string with Chrome/ outside iOS, so Chrome, Edge and Opera show as Blink. On iPhone and iPad every browser uses WebKit.

Related Checks

  • What Is My Browser: a short summary of the browser and version found in this string.
  • IP Lookup: its View Headers button shows the User-Agent as a server receives it, next to your other request headers.
  • Screen Resolution: screen size and pixel ratio, which the User-Agent string does not include.