What's the Latest Version of macOS User Agents

What's the Latest Version of macOS User Agents?

The macOS user agent is a string identifying macOS devices to websites, providing crucial details like the operating system version, hardware architecture, and the browser being used. This helps websites ensure compatibility and provide optimized experiences for macOS users.

macOS User Agent Format

A macOS user agent string packs the operating system, CPU architecture, rendering engine, and browser version into a single line. On Mac, the OS portion is frozen at Intel Mac OS X 10_15_7 for every modern Safari release, which is explained in the next section.

Example: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0 Safari/605.1.15

Breakdown:

• Mozilla/5.0

A legacy identifier used for compatibility across browsers.

• (Macintosh; Intel Mac OS X 10_15_7)

Macintosh: Indicates the device is a Mac.

Intel: Historically the CPU architecture. Apple silicon (M-series) Macs also report "Intel" here for compatibility, so it is not a reliable hardware signal.

Mac OS X 10_15_7: The reported macOS version. Safari deliberately freezes this at 10_15_7 (macOS Catalina) on every newer release to reduce fingerprinting, so it does not reflect the Mac's real macOS version.

• AppleWebKit/605.1.15 (KHTML, like Gecko)

Indicates the WebKit rendering engine (used by Safari and some other browsers like Chrome).

• Version/26.0 Safari/605.1.15

Version/26.0: The version of Safari.

Safari/605.1.15: Identifies the specific version of Safari’s WebKit.

Why Apple Freezes the macOS Version at 10_15_7

Look closely at a modern Safari user agent on any Mac and the operating system is always reported as Intel Mac OS X 10_15_7, even on Apple silicon Macs running macOS Sequoia, Tahoe, or later. This is intentional. Since Safari 15, Apple freezes the OS token at 10_15_7 (the version number of macOS Catalina) to shrink the browser's fingerprinting surface, so websites can no longer read your exact macOS version from the user agent string.

The freeze also fixed a real compatibility problem. When macOS 11 Big Sur first reported "Mac OS X 11_0_0", sites and games that compared the version string naively broke, because 11 sorted lower than 10.15. Capping the value at 10_15_7 kept that older content working. Google Chrome, Microsoft Edge, and Mozilla Firefox adopted the same behaviour: Chromium-based browsers also cap macOS at 10_15_7, while Firefox caps it at 10.15.

Latest macOS User Agent Strings (Copy & Paste)

Below are current macOS user agent strings for Safari and the other major browsers on Mac. Every string keeps the frozen 10_15_7 (or 10.15 for Firefox) OS token described above, so only the browser and engine versions change over time. For the exact, always-current build numbers, use the live user agent table at the top of this page.

Version numbers shown here are indicative of mid-2026 releases and change as browsers update. The frozen 10_15_7 / 10.15 OS token stays the same across newer macOS releases.

How to Modify macOS’s User Agent

• Enable the Develop menu first:

Safari does not expose user agent switching until the Develop menu is turned on. Go to Safari > Settings > Advanced and enable "Show features for web developers" (on older macOS versions this option is labelled "Show Develop menu in menu bar"). Then open the Develop menu in the menu bar, choose "User Agent", and pick a preset browser string or select "Other..." to enter a custom one. Press Command + Option + I to open Web Inspector, where you can confirm the active user agent.

• Extensions:

Use a browser extension such as "User-Agent Switcher" for persistent, per-site user agent changes.

How to Check macOS’s User Agent

• Via Browser:

Open Safari or Chrome, go to about:version or chrome://version → Find "User Agent" under browser details.

• Using JavaScript:

Open DevTools (Command + Option + I), go to the Console tab, and type: navigator.userAgent; Press Enter to display the full user agent string.

How to Fix the "403 disallowed_useragent" Error

The 403 disallowed_useragent error appears when you try to complete a Google sign-in or OAuth authorization from inside an embedded web view - for example an in-app browser such as Android WebView or iOS WKWebView - or from a browser that sends an unrecognized or spoofed user agent string. Since April 2017, Google has blocked OAuth (Google Authorization) requests coming from embedded browsers because they are easier to compromise and can expose user credentials.

How to resolve it:

• Use a system browser: Complete the Google sign-in in a full browser such as Safari, Chrome, or Edge instead of an embedded web view.
• Update the OAuth flow (developers): Launch the default system browser through SFSafariViewController on iOS or Custom Tabs on Android, rather than a raw WebView.
• Do not spoof the user agent: Avoid overriding the browser with a custom or outdated user agent string during authorization, as Google validates it against known secure browsers.
• End users: If the app forces an embedded login, report the issue to the app developer, since the fix has to be made in the app authorization code.

What is my User Agent?