What it is
The operating system is not one value but a story the browser tells in many places: the UA string, the Client Hints, navigator.platform, and then indirectly through fonts, GPU renderer strings, speech voices, touch support and screen shapes. The claim is cheap to make; the corroboration is not.
How websites read it
navigator.platform // "Win32" · "MacIntel" · "iPhone" · "Linux armv8l"
navigator.userAgentData?.platform // "Windows" · "macOS" · "Android"
navigator.oscpu // Firefox only: "Windows NT 10.0; Win64; x64"navigator.platform is the oldest witness and still reports the family — Win32, MacIntel, iPhone, Linux armv8l. Client Hints add the version. Everything else is inference.
Why it identifies you
The OS decides which fonts exist, which GPU drivers render the canvas, which text-to-speech voices are installed and how windows are sized. Those consequences are far harder to fake than the label, so they are what identifies the machine.
How risk-control systems use it
Risk engines treat the OS as the axis everything must line up on. A Windows UA with Helvetica Neue, Menlo and Geneva installed, an Apple GPU or Apple voices reads as a Mac wearing a Windows badge. Mobile claims are checked against touch points; desktop claims against screen size and window metrics.
Common mistakes
Changing only the UA and platform; running a Windows profile on a Mac host without a matching font and GPU set; a macOS profile that reports Microsoft voices; a phone UA on a machine with no touch support.
Mango is accepting waitlist registrations. These capabilities describe its first release; client access opens with invitations.
How Mango Browser handles it
CustomMango configures the operating-system identity for Windows and macOS profiles across its Chrome / Chromium and Firefox engines. Fonts, GPU and platform settings follow the selected profile, with Client Hints aligned where the engine supports them.
Check yours
Jump to this signal in your scan results.