Skip to Content
Platform.Ontology

Chrome and Edge: no default fingerprint defense

Chrome and Edge do not randomize or block fingerprinting APIs by default.

Used to track youGraphics and fingerprintingCountermeasuresWeb browsersWhen the page loads

In one line

Can't stop sites from using device traits to spot you in Chrome or Edge

Chrome and Edge do not randomize or block fingerprinting APIs by default.

Chrome only reduced passive signals (User-Agent Reduction, Client Hints, partitioned storage). Privacy Budget never shipped, so canvas, WebGL, audio and fonts stay fully readable. Chrome has the largest fingerprinting surface.

What it can and can't do

What the user does: Nothing. It is how Chrome and Edge are set up by default

It can

  • Let sites check canvas, graphics, audio and fonts as usual
  • Let sites see a trimmed down browser and system label
  • Keep cookies separate per site, which blocks some tracking

It cannot

  • Add random noise to those checks
  • Block sites from fingerprinting by default
  • Hide your graphics card, fonts and sound setup

How it differs between platforms: Safari, Firefox and Brave add protections that Chrome and Edge do not.

Browser support

BrowserStatusFirst versionNote
ChromeNot supportedNot available:No default defense
EdgeNot supportedNot available:No default defense
FirefoxNot supportedNot available:Edge adds Strict tracking prevention but not fingerprint noise
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot available:No default defense
Samsung InternetNot supportedNot available:No default defense

How a site asks for it

APIChrome settings (no toggle); Incognito changes nothing for fingerprints
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Site reads canvas, WebGL, fonts as usual
  2. Chrome only coarsens UA string and some high entropy hints
  3. Enterprise and extensions like CanvasBlocker can add noise

Data you get

What comes back: No noise, no budget
Shape: none

FieldTypeUnitRangePrecision
noisebooleanNonenonen/a

Technical limits

  • Incognito mode does not change fingerprints
  • Edge Strict mode blocks some trackers, not fingerprinting

The story

What it is

Chrome and Edge do not block or randomize most fingerprinting signals by default.

For you

Most people use Chrome or Edge and leave the default settings on. That means canvas, audio and graphics details are available to most sites, with no warning to you.

For makers

Fraud teams and ad tech rely on the open signals, because they work for the largest share of web users. Chrome has trimmed some data, like the version string, but still leaves most others readable.

Where you see it

TypeExampleApps
adsAn ad network builds a device ID on Chrome visitors using canvas, fonts and graphics, because nothing stops it.None named
securityA bank trusts that Chrome reports honest values, and builds its device recognition on that.None named
gamesA browser game reads graphics card names to pick the best quality setting for each player.None named
analyticsA visitor counting tool gets stable IDs from Chrome users and uses them for unique counts.FingerprintJS
shoppingA big retailer detects bots by checking that Chrome's values look like a real laptop.None named
videoA streaming site reads device and codec details to choose video quality.Netflix, YouTube
developerA developer uses the same signals to fix bugs that only appear on certain graphics cards.None named

Risks

  • Default setting leaves signals open
  • Few people change defaults

What the platform says

Good uses and abuse

Legitimate uses

  • n/a

Known abuse

  • Highest fingerprint fidelity of any browser

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2022-05, Chrome 101: User-Agent Reduction starts
  • 2023-02, Chrome 110: Reduced user agent string rolled out to all desktop and Android
  • 2025-10, Chrome: Privacy Sandbox APIs largely wound down

Sources

How well checked: Based on official documentation.

On this page