# Brave improves protections against GPU fingerprinting

**URL:** https://discuss.privacyguides.net/t/brave-improves-protections-against-gpu-fingerprinting/39889
**Category:** General
**Tags:** article
**Created:** 2026-08-14T05:52:41Z
**Posts:** 5

## Post 1 by @user1 — 2026-08-14T05:52:41Z

> **[Brave improves protections against GPU fingerprinting | Brave](https://brave.com/privacy-updates/38-webgl-webgpu-fingerprinting-protections/)**
>
> Starting in version 1.93, Brave is rolling out new protections against GPU and graphics-driver fingerprinting, de-identifying WebGL vendor and renderer strings and adding noise to the list of supported extensions.

---

## Post 2 by @fernweh — 2026-08-14T08:17:58Z

I am not sure this is going to work as intended because gpu and drivers can be detected due to differences in rendering behavior. Returning wrong js strings would make fingerprints more unique.

---

## Post 3 by @user1 — 2026-08-14T09:15:50Z

Returning a generic string put you in a brave bucket with all the other users, it’s the same concept that tor uses.

---

## Post 4 by @not-wittingly — 2026-08-14T09:29:37Z

Nice, the team there is doing good work

---

## Post 5 by @any1 — 2026-08-14T16:56:38Z

If the only goal is protecting the naive approach of hashing `getSupportedExtensions`, then this could have been done in a much better way.