JavaScript Navigator userAgent Property

What You’ll Learn

navigator.userAgent returns the browser’s User-Agent string. Learn how to read it, why sniffing browsers with it is unreliable, how UA reduction affects the string, five examples, and why feature detection is safer.

Introduction

Every browser has a long identification string called the User-Agent (UA) string. It usually starts with something like Mozilla/5.0 and then lists OS, engine, and browser tokens.

navigator.userAgent gives you that string in JavaScript. The browser also sends a similar value in the User-Agent HTTP header when it requests pages.

Modern Chromium browsers also reduce the UA string (frozen or simplified tokens) for privacy, so parsing brand and version from it gets even harder over time.

Understanding the userAgent Property

Think of navigator.userAgent as a name-tag string the browser already carries — useful for logging and learning, risky as the only way to decide which APIs to use.

• Value — a single string (the UA string).
• Shape — formal tokens (Mozilla/5.0, platform, AppleWebKit, Chrome, Firefox, Safari, …).
• Related APIs — parts overlap with appVersion, platform, and Client Hints.
• Reduction — many browsers freeze or shorten version / OS details.
• Best practice — detect features, not brands.

📝 Syntax

General form of the property:

navigator.userAgent

Value

• A string containing the current browser’s User-Agent.

Common patterns

console.log(navigator.userAgent);
// Chrome (reduced) example shape:
// "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36
//  (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"

// Firefox example shape:
// "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0"

// Prefer feature detection over sniffing:
if ("serviceWorker" in navigator) {
  // safe to use service workers
}

Examples Gallery

Examples follow MDN navigator.userAgent patterns. Prefer Try It Yourself — your live UA string will differ by browser and may be reduced.

console.log(navigator.userAgent);

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36
(your string will differ — and may be reduced)

const ua = navigator.userAgent;
const lines = [
  "typeof: " + typeof ua,
  "length: " + ua.length,
  "starts with Mozilla/5.0?: " + ua.startsWith("Mozilla/5.0")
];
console.log(lines.join("\n"));

typeof: string
length: 117
starts with Mozilla/5.0?: true
(length varies by browser)

const ua = navigator.userAgent;
const lines = [
  "includes(\"Mozilla\"): " + ua.includes("Mozilla"),
  "includes(\"Gecko\"): " + ua.includes("Gecko"),
  "includes(\"Chrome\"): " + ua.includes("Chrome"),
  "includes(\"Safari\"): " + ua.includes("Safari")
];
console.log(lines.join("\n"));
console.log("Many browsers share these tokens — do not gate features on them.");

includes("Mozilla"): true
includes("Gecko"): true
includes("Chrome"): true
includes("Safari"): true
Many browsers share these tokens — do not gate features on them.
(exact true/false values depend on your browser)

const lines = [
  "userAgent: " + navigator.userAgent,
  "appVersion: " + navigator.appVersion,
  "platform: " + navigator.platform
];
console.log(lines.join("\n"));
console.log("Still prefer feature detection for real app logic.");

userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...
appVersion: 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...
platform: Win32
Still prefer feature detection for real app logic.
(values vary)

const lines = [];
lines.push(
  "userAgent length: " + navigator.userAgent.length + " — OK for logs"
);
lines.push(
  "serviceWorker: " +
    ("serviceWorker" in navigator ? "available" : "missing") +
    " — use this for features"
);
lines.push(
  "geolocation: " +
    ("geolocation" in navigator ? "available" : "missing")
);
console.log(lines.join("\n"));

userAgent length: 117 — OK for logs
serviceWorker: available — use this for features
geolocation: available

🚀 Common Use Cases

• Debugging / support logs — include the UA string when reporting bugs.
• Learning HTTP — connect the JS property to the User-Agent request header.
• Legacy code review — spot brittle includes("Safari") sniffing.
• Not for feature gates — do not enable APIs based on brand tokens alone.
• Analytics caution — reduced UAs make fine-grained OS / version stats less accurate.

📝 Notes

• Baseline Widely available (MDN, since July 2015).
• Not Deprecated, Experimental, or Non-standard — no status banner required.
• Read-only string on Navigator.
• UA sniffing is unreliable; UA reduction makes it worse for version detection.
• Related: userAgentData, appVersion, platform, product.

💡 Best Practices