Browserleaks tests failed?

Can anyone tell why brave for iOS generates (more or less) unique hashes / fingerprints in multiple sections of the site browserleaks.com ? Among them in canvas, and fonts, and html5.

This has been tested and confirmed multiple times, and with different settings in the brave shields (in particular tracking, fingerprinting, etc).

Isn’t it true that brave is supposed to do the opposite, protect the user from all tracking and fingerprinting ?

iOS limitation. I had to verify, iOS’s app store still requires all 3rd party browsers to essentially use WebKit. For example, Firefox isn’t using Gecko, it too on iOS is using WebKit. Thus, Brave isn’t using Blink like it would on other platforms, instead it’s using WebKit as well.

Unfortunately do to this, there is only so much you can do. As an ex employee of Apple, I wish I could tell you they’d budge on this, but they weren’t willing when I worked there (Mac OS Mavericks era), and apparently, still aren’t. There’s some exclusions with Europe and Japan, but I’ve yet to see anything come of it yet (though being Japan’s deadline was December of 2025, and it’s January of 2026, maybe we’ll see some traction finally).

This all comes down to this basically, Brave can only do so much on the iOS platform, because iOS is a walled garden. (One of which Android used to not be, but is slowly becoming itself).

A simple version of this is, Brave can request these protections from WebKit, but WebKit will do what it thinks it should per Apple’s own policies.

Thanks a lot for that insight!

I haven’t tested brave for Android as much, but a few simple runs this morning seem to show, that here too brave does generate some unique fingerprints. Would you say this is due to

  • limitations (bugs ?) in brave (v 1.85.177)
  • or again sth on OS level, similar to what happens under iOS …

Happy New Year !

The serious problem I see is that the whole appstore description AND the brave user interface (UI) is designed to give the user the impression that brave “takes care of all privacy needs” which a user may ever need. And … it doesn’t.

A simple example: settings > security > fingerprinting …

you switch it on, and it makes you believe, all fingerprinting is blocked. But it isn’t. If the brave designers had nothing but the user needs on their minds …. this button would be replaced by a gentle warning: brave (at least on ios and Android) CANNOT protect you from fingerprinting. Be aware that more than 50% of all sites worldwide (source: Bruce Sneier) employ techniques to generate unique fingerprints of users, their devices, etc.

It has been partly answered, at least for the iOS, but the result for users is nevertheless disappointing.