70 bits? That's a ton. I'm at: 17.62 Chrome 75.0.x normal (non-incognito) 16.62 Chrome 75.0.x incognito 15.62 FF 68.0.1 (Private doesn't seem to make a

70 bits? That's a ton. I'm at: 17.62 Chrome 75.0.x normal (non-incognito) 16.62 Chrome 75.0.x incognito 15.62 FF 68.0.1 (Private doesn't seem to make a diff, I get the same score) Seems like in Chrome, at least, the most offending (most unique) "characteristic" is HTTP_ACCEPT Headers, which looks something like text/html, */*; q=0.01 gzip, deflate, br en-US,en;q=0.9,fr-FR;q=0.8,f... If there is a good way to control this (FF does a much better job -- could be tied to plugins and such tho), one could further reduce the number of identifying bits. Chrome seems to do better (less unique) in both Hash of canvas fingerprint and Hash of WebGL fingerprint. I've summarized the main differences I see below, seems like combining the best of Chrome w/ the best of FF would result in even better privacy: https://i.imgur.com/QQQ6R85.png https://i.imgur.com/QQQ6R85.png Edit: I think Chrome's HTTP_ACCEPT Headers is like that because I've installed/enabled many languages in it for l10n testing. I'm removing them now, which should make Chrome get a better score than FF.