JavaScript Navigator oscpu Property

What You’ll Learn

navigator.oscpu returns a string that identifies the current operating system when the browser exposes it. Learn MDN’s example, typical OS string shapes, feature detection, preference overrides, why sniffing is brittle, five examples, and try-it labs.

Introduction

The name oscpu comes from older browser APIs that tried to answer: “what operating system / CPU platform is this?” On supporting browsers it returns a human-readable OS string.

Today that answer is incomplete across the web. Chromium and Safari typically do not expose a useful oscpu, and even in Firefox the string can be overridden for privacy or testing.

Understanding the oscpu Property

When available, reading navigator.oscpu gives a string describing the OS. MDN documents common formats such as Windows NT x.y; Win64; x64 or Linux uname-style output.

• Read-only — you inspect; you do not assign.
• Non-standard — limited, engine-specific support.
• May be missing — treat absence as normal on many browsers.
• May be overridden — Firefox general.oscpu.override can replace the true value for non-privileged pages.

📝 Syntax

General form of the property:

navigator.oscpu

Value

• A string identifying the operating system when supported.
• Often undefined / absent outside Gecko.

Common patterns

// Always feature-detect first
if ("oscpu" in navigator && navigator.oscpu) {
  console.log(navigator.oscpu);
} else {
  console.log("oscpu not available");
}

// MDN-style helper:
function osInfo() {
  return navigator.oscpu;
}

Examples Gallery

Examples follow MDN navigator.oscpu patterns with safe detection. Prefer Try It Yourself in Firefox to see a real string; Chromium often shows “missing.”

const supported = "oscpu" in navigator && !!navigator.oscpu;
console.log(supported ? "oscpu available" : "oscpu missing");

oscpu missing
(or "available" in Firefox / Gecko)

function osInfo() {
  if (!("oscpu" in navigator) || !navigator.oscpu) {
    console.log("oscpu not supported");
    return;
  }
  console.log(navigator.oscpu);
}

osInfo();
// Example on some Firefox builds: "Windows NT 10.0; Win64; x64"

oscpu not supported
(or a string like "Windows NT 10.0; Win64; x64")

function describeOscpu() {
  if (!navigator.oscpu) return "missing";
  const s = String(navigator.oscpu);
  const hints = [];
  if (/Windows NT/i.test(s)) hints.push("windows-nt");
  if (/Win64|x64/i.test(s)) hints.push("64-bit-tokens");
  if (/WOW64/i.test(s)) hints.push("wow64");
  if (/Linux|Mac OS|macOS/i.test(s)) hints.push("unix-like-tokens");
  return "value=" + s + "; hints=" + (hints.join(",") || "none");
}

console.log(describeOscpu());

missing
(or value=Windows NT 10.0; Win64; x64; hints=windows-nt,64-bit-tokens)

function oscpuTrustNote() {
  if (!navigator.oscpu) {
    return "No oscpu — cannot trust or distrust a missing value.";
  }
  return (
    "Got: " +
    navigator.oscpu +
    " — treat as untrusted (prefs / privacy may override)."
  );
}

console.log(oscpuTrustNote());

No oscpu — cannot trust or distrust a missing value.
(or "Got: … — treat as untrusted…")

const lines = [];
lines.push(
  "oscpu: " +
    (navigator.oscpu ? navigator.oscpu : "(absent)") +
    " — ignore for sniffing"
);
lines.push(
  "serviceWorker: " +
    ("serviceWorker" in navigator ? "available" : "missing")
);
lines.push(
  "onLine: " + String(navigator.onLine)
);
console.log(lines.join("\n"));

oscpu: (absent) — ignore for sniffing
serviceWorker: available
onLine: true
(exact lines depend on your browser)

🚀 Common Use Cases

• Learning Navigator — see a classic non-standard OS string API.
• Legacy Firefox debugging — understand old OS-report reads.
• Privacy / override education — show why OS sniffing is untrusted.
• Not for production branching — prefer feature detection.
• Not for fingerprinting — avoid collecting brittle identity signals.

📝 Notes

• Non-standard — primarily a Gecko/Firefox-oriented Navigator property (MDN).
• Not Baseline; many engines omit it.
• Read-only string when present.
• May reflect general.oscpu.override instead of the true platform.
• Do not use for production OS sniffing or fingerprinting.
• Related: onLine, buildID, appVersion, Window.

💡 Best Practices