Windows 11 Browser Fingerprint
On desktop systems, Windows 11 creates one of the most distinctive browser fingerprints. The combination of Windows-specific system fonts, ANGLE-based WebGL rendering, and DPI scaling options available only on Windows produces a fingerprint profile that is structurally different from macOS, Linux, or mobile fingerprints.1 Windows 11 ships with Segoe UI Variable, Calibri, Cambria, Consolas, and other Microsoft-exclusive typefaces that do not exist on macOS or Linux default installations.
The WebGL renderer string on Chrome includes ANGLE and a Direct3D version identifier that is absent from macOS Metal-based renderers.2 Display scaling at 125%, 150%, or 175%, Windows-specific options, produces non-integer devicePixelRatio values of 1.25, 1.5, or 1.75 that are uncommon in the global browser population.3 Consequently, a browser on Windows 11 with non-standard DPI scaling exposes a combination of signals that definitively identifies the OS and narrows the hardware further than any single signal alone.
Windows 11 signal sources
- Exclusive fonts Segoe UI, Segoe UI Variable, Calibri, Cambria, Consolas, Candara, Constantia, Corbel
- WebGL renderer prefix ANGLE, present only on Windows Chrome
- Non-integer DPI scaling 125%, 150%, 175% produce devicePixelRatio 1.25, 1.5, 1.75
Opens the Browser Fingerprint Inspector with this section's checklist shown at the top of the tool.
Open in the tool →Windows-specific font set as a fingerprinting signal
Font fingerprinting scripts probe for the presence of specific fonts by rendering text and measuring pixel widths using CanvasRenderingContext2D.measureText().4 Windows 11 installs a defined set of Microsoft-exclusive fonts that do not exist on default macOS or Linux installations: Segoe UI, Segoe UI Variable, Calibri, Cambria, Consolas, Candara, Constantia, and Corbel are all Windows-only in default configurations.1 Detecting the presence of Segoe UI alone is sufficient to confirm a Windows OS.
Why Windows 11 creates a recognizable browser profile
Beyond the OS-default set, installed software adds recognizable fonts that fingerprint the installed application portfolio: Adobe Creative Cloud installs several Adobe-exclusive typefaces, gaming peripherals software installs brand-specific fonts, and Microsoft 365 adds additional Office-exclusive fonts. Consequently, the full font set on a Windows 11 installation reflects both the OS and the installed application ecosystem, creating a compound identifier that is more distinctive than either the OS or the software list alone.
The scale of this effect becomes clear when you consider how many applications leave a font trail. A typical Windows 11 machine with creative, productivity, and gaming software installed exposes dozens of application-specific typefaces that together describe the user's software choices. You can measure your own profile with the fingerprint inspector, which lists every font a script can detect and shows how the total set narrows your position in the Windows population.
Why font probes are hard to hide
Building on this, font fingerprinting operates through canvas measurement without requiring any canvas image exports, which means canvas image blocking does not prevent font probe detection. The measureText() API returns a numeric width value rather than pixel data, so even extensions that intercept toDataURL() or toBlob() calls have no effect on font enumeration. This makes font probing one of the most resilient fingerprinting techniques, since it bypasses the most common canvas-level blocking strategies while still relying on the same rendering engine that produces the canvas hash.
ANGLE rendering on Windows and the WebGL renderer string
Chrome on Windows routes all WebGL calls through ANGLE (Almost Native Graphics Layer Engine), which translates OpenGL ES calls to Direct3D.2 The WEBGL_debug_renderer_info UNMASKED_RENDERER_WEBGL string on Windows Chrome takes the form "ANGLE (NVIDIA GeForce RTX 4070 Direct3D11 vs_5_0 ps_5_0)". This string format is unique to Windows and contains three distinct identifiers: the ANGLE prefix confirming Windows Chrome, the GPU model name identifying the specific card, and the Direct3D version identifying the Windows version and driver generation.
How to reduce Windows fingerprint exposure
Consequently, the WebGL renderer string on Windows is simultaneously a Windows indicator, an OS version indicator, and a GPU model identifier. macOS Chrome uses Metal and reports a different format; Linux Chrome reports Mesa-based strings. Building on this, the Direct3D version in the renderer string, Direct3D11 or Direct3D12, narrows the Windows version and GPU driver generation, since Direct3D12 requires Windows 10 or later and a compatible GPU driver series.5
DPI scaling as an entropy amplifier
Windows allows non-integer display scaling in Settings > Display > Scale: 100%, 125%, 150%, 175%, and 200%. Each scaling percentage produces a specific window.devicePixelRatio value: 1.0, 1.25, 1.5, 1.75, or 2.0. The non-integer values, 1.25, 1.5, and 1.75, are uncommon in the global browser population.3 Most macOS displays report exactly 2.0 (Retina) or 1.0, and mobile browsers cluster around 2.0, 3.0, or 4.0.
Consequently, a Windows user at 125% scaling (devicePixelRatio 1.25) is in a small subpopulation, and combining that with a specific screen resolution and the ANGLE renderer string narrows the candidate pool significantly. Furthermore, users who set scaling to 150% for accessibility reasons are in a different subpopulation from those who use it for HiDPI optimization, which correlates with different software portfolios and device usage patterns. Measuring how DPI scaling and ANGLE combine on your specific display shows which Windows 11 signals contribute most to your overall fingerprint uniqueness.
When to use this
Use this guide when analyzing why a Windows 11 browser produces a higher entropy score than macOS or Linux, or when evaluating which Windows-specific signals contribute most to fingerprint uniqueness.
Examples
Windows 11 font detection vs. macOS baseline
macOS Safari or Chrome: probing for Segoe UI returns width matches fallback font (absent), OS confirmed as non-Windows
Windows 11 Chrome: probing for Segoe UI returns a different width (present), immediately confirms Windows OS without any other signal
A single font probe for Segoe UI is sufficient to distinguish Windows from macOS and Linux. Advanced scripts probe 100+ fonts to build a detailed application portfolio signature.
ANGLE renderer string vs. macOS Metal renderer
macOS Chrome: `UNMASKED_RENDERER_WEBGL` → "Apple M2" or "AMD Radeon Pro 5500M OpenGL Engine"
Windows 11 Chrome: `UNMASKED_RENDERER_WEBGL` → "ANGLE (NVIDIA GeForce RTX 4070 Direct3D11 vs_5_0 ps_5_0)"
The ANGLE prefix uniquely identifies Windows Chrome. The Direct3D version in the string further identifies the Windows version and GPU driver generation.
- 1.
Microsoft, "Font List Windows 11," learn.microsoft.com, accessed July 2026. https://learn.microsoft.com/en-us/typography/fonts/windows_11_font_list
- 2.
ANGLE, "Almost Native Graphics Layer Engine," chromium.googlesource.com, accessed July 2026. https://chromium.googlesource.com/angle/angle/+/HEAD/README.md
- 3.
Microsoft, "Scale and Layout for Windows," learn.microsoft.com, accessed July 2026. https://learn.microsoft.com/en-us/windows/apps/design/layout/screen-sizes-and-breakpoints-for-responsive-design
- 4.
Mozilla Developer Network, "CanvasRenderingContext2D: measureText() method," developer.mozilla.org, accessed July 2026. https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/measureText
- 5.
"Direct3D," Wikipedia, accessed July 2026. https://en.wikipedia.org/wiki/Direct3D
Browser Fingerprinting on a Windows PC (Chrome)
Google's Privacy Sandbox initiative was discontinued in April 2025 without ever shipping a fingerprinting-specific mitigation.1 That leaves Chrome on this Windows PC with no engine-level equivalent to Safari's Advanced Fingerprinting Protection or Firefox's resistFingerprinting mode, just a menu of individually configured privacy settings. CapyToolkit's own Windows 11 guide already documents the exclusive font set, the ANGLE-prefixed WebGL renderer string, and the DPI scaling ratio this configuration exposes; what that guide doesn't cover is that nothing in Chrome, by default, stands between those signals and a script reading them.
Run this check yourself in the Browser Fingerprint Inspector.
Open in the tool →Specifications
| Rendering engine | Chrome / Blink; ANGLE translates WebGL calls to Direct3D |
|---|---|
| Built-in fingerprinting resistance | None by default; Privacy Sandbox discontinued April 2025 |
| Client Hints model | Opt-in; a site must request reduced or high-entropy values itself |
| Canvas / WebGL / font signals | Return the identical value on every run, no default noise |
| Already-documented signals | Exclusive Windows fonts, ANGLE renderer string, non-integer DPI scaling |
Why nothing here suppresses the signals the Windows 11 guide already documents
CapyToolkit's own Windows 11 guide walks through the exclusive font set, the ANGLE-prefixed WebGL renderer string, and the non-integer DPI scaling values this kind of configuration exposes in detail. What that guide doesn't need to cover separately is the reason those signals reach a script unmodified in the first place: Chrome on this PC has no built-in mechanism that suppresses or randomizes any of them by default, unlike the browsers this same tool profiles on Apple hardware.
Google's Privacy Sandbox ended without a fingerprinting fix
Privacy Sandbox was discontinued in April 2025 without shipping a single fingerprinting-specific mitigation, leaving Chrome without one central anti-fingerprinting switch of the kind Firefox or Safari offer.1 In its place, Chrome offers a scattered menu of individually configured settings, cookie controls, and Client Hints options, none of which suppress canvas, WebGL, or font enumeration output the way an engine-level protection would.
Client Hints exist, but a site has to opt in to receiving less
User-Agent Client Hints were designed so the default request header stays generic while a site actively requests more detail through an Accept-CH response header if it wants it.2 Nothing about that design forces a site toward the reduced path; a site that wants the fuller picture simply asks for it. That stands opposite to Advanced Fingerprinting Protection, which this tool's iPhone and MacBook guides describe as applying automatically at the engine level regardless of what any individual site requests.
Why this combination reads as the least anonymous of the four devices in this set
Stacking the pieces together explains why a Windows Chrome scan tends to land at the higher end of the entropy scale among the devices this tool profiles. iPhone and MacBook Safari both apply engine-level fingerprinting protections that touch canvas, WebGL, and audio output; Samsung's Galaxy Chrome at least ships behind a somewhat-reduced default User-Agent header even though the underlying hardware APIs still expose real values. This Windows PC has neither an engine-level protection nor a meaningfully reduced default header standing between the fonts, GPU renderer string, and DPI ratio already documented in the Windows 11 guide and a script reading them.
No default noise means canvas, WebGL, and font rows repeat the same value every run
Run this scan on this PC twice in a row and the canvas hash, the WebGL renderer string, and the detected font list will read identically both times, because nothing in stock Chrome injects session noise the way Safari's Advanced Fingerprinting Protection or Firefox's resistFingerprinting mode does.2 That exact repeatability, the same value on the tenth visit as on the first, is precisely the property that makes a signal useful for cross-session tracking in the first place, which is why the entropy score tends to sit higher here than on the Safari-based devices in this set.
Switching to Brave with Shields enabled, or to Firefox with resistFingerprinting turned on, would change that picture measurably on this same physical machine, since both apply engine-level randomization Chrome does not ship by default.34 Running this scan before and after making that switch is the most direct way to see the difference on your own PC rather than taking the comparison on faith; the unchanged canvas hash, ANGLE renderer string, and font list it reports are exactly the stable hardware signals a tracking script keys a cross-session identity on.5
- 1.
The Register, "Google Chrome lacks browser fingerprinting defenses," theregister.com, April 2026. https://www.theregister.com/security/2026/04/16/google-chrome-lacks-browser-fingerprinting-defenses/5229136
- 2.
Google Chrome, "Improving user privacy and developer experience with User-Agent Client Hints," developer.chrome.com, accessed August 2026. https://developer.chrome.com/docs/privacy-security/user-agent-client-hints
- 3.
Brave, "Fingerprint Randomization," brave.com, 2020. https://brave.com/privacy-updates/3-fingerprint-randomization/
- 4.
Wikipedia, "Device fingerprint," en.wikipedia.org, accessed August 2026. https://en.wikipedia.org/wiki/Device_fingerprint
- 5.
Mozilla Developer Network, "Privacy on the web," developer.mozilla.org, accessed August 2026. https://developer.mozilla.org/en-US/docs/Web/Privacy
Safari on both Apple devices applies engine-level Advanced Fingerprinting Protection that adds noise to canvas, WebGL, and audio output. Chrome on this Windows PC has no equivalent by default, so the exclusive fonts, ANGLE renderer string, and DPI scaling ratio already documented in this tool's Windows 11 guide reach a script unmodified.
Privacy Sandbox, Google's initiative covering this area, was discontinued in April 2025 without shipping a fingerprinting-specific mitigation. Chrome instead offers a set of individually configured privacy settings and Client Hints controls rather than one built-in switch.
A site has to actively request additional User-Agent detail through an Accept-CH response header to receive it; the reduced string is only the default when a site doesn't ask for more. That's a different model from Advanced Fingerprinting Protection, which applies automatically regardless of what a site requests.
No, not without changing something about the machine or the browser itself. Stock Chrome applies no session noise to canvas or WebGL readouts, so the same hardware and driver combination produces the identical value on every run, which is exactly the repeatability that makes a signal useful for tracking.
Switching to Brave with Shields enabled or Firefox with resistFingerprinting turned on would apply engine-level randomization Chrome doesn't ship by default. CapyToolkit's inspector lets you run the same scan before and after making that switch on your own PC to see the measurable difference rather than taking the comparison on faith.
Install from Microsoft Store