macOS user agent tokens
Browsers on macOS include a Macintosh; Intel Mac OS X platform token. The macOS version embedded in it is frozen or capped by modern browsers, so it confirms macOS but not the precise release, and it still says Intel even on Apple Silicon for compatibility. Use Client Hints for finer detail.
What this means
On macOS, browsers report a Macintosh; Intel Mac OS X platform token with a version. Modern browsers freeze or cap this version to reduce fingerprinting and avoid breaking version-sniffing sites, so the number plateaus and stops tracking new macOS releases accurately.
Notably, the token continues to say Intel even on Apple Silicon Macs. This is intentional compatibility behaviour; it does not mean the machine has an Intel processor.
What you cannot infer
You cannot read the exact macOS release from the frozen version, and you cannot determine Intel versus Apple Silicon from the legacy string, since it reports Intel universally. Attempts to do either yield misleading data.
Where platform architecture or version genuinely matters, request high-entropy Client Hints (such as Sec-CH-UA-Arch and Sec-CH-UA-Platform-Version) and accept that the browser may not return them.
- Token confirms macOS, not the exact release
- Architecture reads Intel even on Apple Silicon
- Use high-entropy Client Hints for finer detail, if granted
Practical handling
Group macOS visits by the broad family for analytics and avoid presenting a precise version or chip split derived from the user agent. Such breakdowns are unreliable given the freeze and the universal Intel token.
As always, do not base access control on the platform token alone; it is coarse context and is client-supplied.
How it appears in analytics and logs
A Macintosh / Mac OS X token indicates a macOS desktop browser. The version is frozen or capped, and the architecture still reads Intel even on Apple Silicon Macs, so neither the OS version nor the chip can be read reliably from the user agent.
Diagnostic use case
Interpret the macOS platform token for desktop analytics, and understand why it cannot tell you the exact macOS version or whether the Mac uses Apple Silicon.
What WebmasterID can help detect
WebmasterID treats the macOS token as coarse OS context for human-traffic breakdowns, avoiding any claim about exact macOS version or chip architecture that the user agent cannot support.
Common mistakes
- Reading the exact macOS version from the frozen token.
- Inferring Apple Silicon vs Intel from a string that always says Intel.
- Using the macOS token as a device fingerprint.
Privacy and accuracy notes
The macOS token is coarse OS context, not an identity or a location. WebmasterID records the broad platform family only and does not combine tokens into a fingerprint.
Related pages
- Windows user agent tokens
Browsers on Windows include a Windows NT platform token in the legacy user-agent string. The NT version number has been effectively frozen, so it identifies the Windows family but not the marketing version — Windows 10 and Windows 11 share the same NT 10.0 token. Use Client Hints for finer platform detail.
- Safari user agent on iOS and macOS
Safari's user agent is built around WebKit and a Version token, and differs between macOS and iOS. A notable quirk is that iPadOS can present a desktop-class Safari user agent, which can make an iPad look like a Mac in logs. This page covers the pattern and the platform-specific behaviour.
- User-Agent Client Hints
User-Agent Client Hints are HTTP headers (the Sec-CH-UA family) that let a site request specific browser, platform, and version detail rather than reading it all from one passive string. They underpin UA reduction: the raw user agent is shrinking, and finer detail moves to opt-in hints. This page explains the model.
- WebmasterID docs
Coarse platform context recorded without device fingerprinting.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.