Solution 1 :

One option would be using navigator.userAgentData along with the .getHighEntropyValues() method. Then we can utilize the User-Agent Client Hints API and get high entropy values from userAgentData by requesting a number of hints. Providing a means to detect OS from User-Agent information since navigator.platform is no longer.

Or instead just access navigator.userAgent which has full support and provides a user-agent string for the current browser where the OS could be extracted from.

function checkOS(n) {
  if (n.userAgentData) {
    const hints = ["architecture", "model", "platform", "platformVersion", "uaFullVersion"];
      .then(ua => {
  } else {
    return "navigator.userAgentData is not supported!";


This is about the only documentation I’ve found in the DevTools “issues” tab aside from information on update on user agent string reduction.

A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. In a future version of Chrome, the amount of information available in the User Agent string will be reduced. – To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.

I tried logging navigator.userAgentData to the console on a Windows and macOS machine using Chrome to see what kind of data it contained, and the object does have some useful information like the getHighEntropyValues() method in particular.

// NavigatorUAData {brands: Array(3), mobile: true}
  "brands": [
      "brand": "Chromium",
      "version": "92"
      "brand": " Not A;Brand",
      "version": "99"
      "brand": "Google Chrome",
      "version": "92"
  "mobile": false,
  "getHighEntropyValues": function getHighEntropyValues() { [native code] }

The browser support for navigator.userAgentData is not great (only supported in Chrome, Edge, Opera), but this could be a step in the right direction for detecting OS from userAgentData since navigator.platform is no longer. CodePen demo

Solution 2 :

It turns out that the only realistic option for now is to look at the User Agent string and make decisions based on that (either by handrolling code, or using a user agent parsing library that does that for you).

This is not ideal, but as the goal is OS detection, and explicitly not browser detection, it’s also not too hacky or liable to break in the future.

Problem :

While previously we were able to use navigator.platform in order to check which OS a browser was running in (which is still necessary for things like key event translation, e.g. Home vs. metaKey+ArrowLeft, or placing virtual modal “close” icons in a way that follows OS conventions) that option no longer exists. (That is to say, right now it technically still does but it’s no longer a solution that is guaranteed to work by the time you deploy your code).

I can’t seem to find any official documentation on what the replacement is supposed to be if OS knowledge is required: what is the new and improved way to determine which OS/platform a web page is running on?

(The currently most popular SO question around this, “Best way to detect Mac OS X or Windows computers with JavaScript or jQuery”, does not have any answers that have been edited since the decision to deprecate navigator.platform was made, so unfortunately is not useful at the moment)


Comment posted by Mike ‘Pomax’ Kamermans

Yeah, this appears to be yet another one of those Chrome-only solutions instead of a true, agreed upon replacement =(

Comment posted by Tanner Dolby

Yeah, agreed =(