2026-06-23 · Avery Chen · 872 words
A macOS fingerprint on a Windows host
OS-family mismatch is a loud tell. This note covers a macOS story on a Windows host, and why most buyer guides never write that gap down. Authorized work only.
A macOS story on a Windows host is an OS-family mismatch. The user agent can say Macintosh. The box is still a PC. Fonts, raster, GPU paths, and the process list will argue. Most buyer guides never write that gap down. They list surfaces. They skip the host.
This is a coherence note for authorized profiles on the public Windows channel. It is not a "how to look like a Mac" guide. We will not write that guide.
The host is the constraint
The public download is Windows 10 and 11 x64. Installer target is NSIS for that arch. Build scripts exist for macOS and Linux. Those packs are not the public channel. I will not claim they are tested end to end.
Fingerprint presets can model desktop OS families, including macOS. That is a schema fact. It is not a promise that a Mac caption survives contact with a Windows process. Client Hints still mark mobile false. The product is desktop profiles, not a Mac hardware lab.
What browser fingerprinting actually measures is a bundle that is supposed to agree. An OS-family fork is the loudest disagreement in that bundle.
The Browser fingerprinting cluster already refused the phone version of this mistake in a mobile user agent on a desktop profile. This page is the Mac version.
| Host fact | What a Mac caption needs | What you actually have |
|---|---|---|
| Fonts | A macOS catalog and raster | DirectWrite, Windows faces |
| GPU | Metal / Apple family | --use-angle=d3d11 on win32 |
| Process list | A Mac process table | A Windows binary, aliasing only partial |
| TLS hello | A Mac Chromium hello | A Windows Chromium hello |
| Cookies | A session that could be Mac | Often a leftover Windows Chrome session |
Where the story breaks
Fonts. Windows catalogs are distinctive. The inject can allowlist faces and patch document.fonts.check plus measurement fallbacks. Measurement still happens on a Windows layout engine. DirectWrite raster is only partly in our hands, and only when the custom Chromium 131 core is present with a MASKWRIGHT_FONT_LIST. A Mac UA with a Windows font catalog is a cheap catch.
GPU. The renderer has to match the user agent. An ANGLE Direct3D string next to Macintosh is a fork. A claimed Apple GPU on a machine that still answers like D3D is a fork. Launch on win32 uses --use-angle=d3d11 for Chromium. That is a host fact.
Process. Task Manager still shows a Windows process. Process-name aliasing is partial: an optional hardlink or a compile-time patch. It is not a Mac process table.
TLS. The Client Hello belongs to the binary you launched. A Windows Chromium hello with a Macintosh UA is the same collage as a phone UA on that hello.
Cookies. A new fingerprint in the same folder can paint Macintosh and leave a Windows Chrome cookie store. The site then has a Mac caption on a PC session.
What we actually cover, and what we do not
The surfaces we actually cover include UA, Client Hints, platform, vendor, screen, WebGL, WebGPU, canvas, fonts, client rects, audio, and the rest of the inject schema. Those overrides can say macos in the schema. They cannot turn the host into Apple hardware.
Automation flags are unrelated. We set webdriver false. That does not mint a Mac.
After third-party cookies is unrelated. Topics and CHIPS do not fix an OS-family fork.
We have no published pass rates. I will not claim a macos preset on this host clears a named stack. I will not claim the custom core makes the host a Mac. When the core is missing, we fall back to system Chrome or Edge with JS and CDP spoof only.
How I want you to decide
If the authorized profile is a Windows person, tell a Windows story. Match GPU, fonts, screen, and UA to that family. Test the profile before work as a PC profile.
If the authorized profile is a Mac person, the honest tool is a Mac. The public channel is not that tool today. A schema field that can say macos is a convenience for desktop families. It is not a hardware swap. Operators who treat the dropdown as a swap will meet the host on the first font probe.
Buyer guides skip this gap because a feature grid looks cleaner without it. The grid can say "macOS fingerprints" and stop. The host still has DirectWrite, Task Manager, and a Windows hello. Write those three down before you trust the dropdown.
A caption is cheap. The host is not. Write the gap down before you buy a Macintosh string for a tower. If you already launched a macos preset on this PC, treat the first font and GPU mismatch as expected, not as a lab defect you can hunt away with a snippet.
FAQ
Does the schema support a macos preset? Yes, as a desktop family in the schema. That is not a hardware swap.
Are macOS installers the public channel? No. Public download is Windows 10 and 11 x64. Other packs exist as build scripts. End-to-end testing is unknown.
Will the custom Chromium core make the host a Mac? No. It can go deeper on some Windows tells. It does not mint Apple hardware.
Related notes
- What browser fingerprinting actually measuresBrowser fingerprinting
- Testing a fingerprint before workBrowser fingerprinting
- A mobile user agent on a desktop profileBrowser fingerprinting
- A new fingerprint in the same folderBrowser fingerprinting
- GPU renderer has to match the user agentBrowser fingerprinting
- Fingerprint surfaces we actually coverBrowser fingerprinting
- navigator.webdriver and automation flagsBrowser fingerprinting
- What replaces third-party cookies for trackingBrowser fingerprinting