JavaScript Navigator appVersion Property

What You’ll Learn

navigator.appVersion is a read-only Navigator string that claims to describe browser version info. The text varies by browser, is unreliable for sniffing, and should not drive feature logic. Learn how to read it, compare it with userAgent, and prefer feature detection.

Introduction

appVersion sounds like a clean “browser version number.” In reality it is a free-form compatibility string. Chrome-family browsers often return something close to userAgent with the Mozilla/ prefix removed. Firefox often returns a short hint such as 5.0 (Macintosh).

That inconsistency is exactly why MDN recommends against using it to work around bugs or missing features. User-Agent reduction also makes these strings less detailed over time.

Still learn the property so legacy code and DevTools experiments make sense — then choose safer patterns for real apps.

Understanding the appVersion Property

Reading navigator.appVersion returns a string the browser exposes as “version information.” There is no single guaranteed format across engines.

• It is read-only.
• Content varies significantly by browser (long vs short strings).
• Often related to, but not identical to, navigator.userAgent.
• Unreliable for browser detection or version gating.

📝 Syntax

General form of the property:

navigator.appVersion

Value

• A string representing version-like information about the browser.

Common patterns

console.log(navigator.appVersion);

// Inspect safely — do not branch product logic on parse results
const v = navigator.appVersion;
console.log(typeof v, v.length);

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

Examples Gallery

Examples follow MDN Navigator.appVersion patterns. Outputs differ by browser — that is the lesson. Use View Output or Try It Yourself for each case.

console.log(navigator.appVersion);
// Chrome-like: long string starting with "5.0 (…"
// Firefox-like: often short, e.g. "5.0 (Windows)"

(browser-dependent string — open Try It to see yours)

const v = navigator.appVersion;
console.log(typeof v);
console.log("length: " + v.length);
console.log("preview: " + v.slice(0, 40) + (v.length > 40 ? "…" : ""));

string
length: (varies)
preview: 5.0 (…

const v = navigator.appVersion;
console.log(v.startsWith("5.0"));
console.log(v.slice(0, 12));
// true (common)
// 5.0 (Windows  or similar

true
5.0 (Windows
(exact preview depends on OS / browser)

const av = navigator.appVersion;
const ua = navigator.userAgent;
const lines = [
  "appVersion length: " + av.length,
  "userAgent length: " + ua.length,
  "UA includes appVersion? " + ua.includes(av)
];
console.log(lines.join("\n"));

appVersion length: (varies)
userAgent length: (varies)
UA includes appVersion? true or false
(depends on browser relationship)

const lines = [];
lines.push("appVersion preview: " + navigator.appVersion.slice(0, 24) + "…");
lines.push(
  "geolocation: " +
    ("geolocation" in navigator ? "available" : "missing")
);
lines.push(
  "serviceWorker: " +
    ("serviceWorker" in navigator ? "available" : "missing")
);
console.log(lines.join("\n"));

appVersion preview: 5.0 (…
geolocation: available
serviceWorker: available
(exact lines depend on your browser)

🚀 Common Use Cases

• Learning Navigator — see a browser-dependent string property.
• Debugging legacy sniffers — understand what old code was reading.
• Teaching anti-patterns — show why version parsing fails across engines.
• Quick diagnostics — log once in DevTools (not for production branching).
• Not for feature gating — use feature detection or support tables instead.

📝 Notes

• Returns a string — format is not standardized across browsers.
• Unreliable for detecting browser brand or exact version.
• Related to, but not a replacement for, userAgent.
• Baseline Widely available — support ≠ usefulness for sniffing.
• Related: appName, appCodeName, Window.

💡 Best Practices