Brave has released version 1.93 protections to thwart GPU fingerprinting by de-identifying WebGL vendor and renderer strings and randomizing WebGL extensions, while clearing WebGPU adapter descriptors to hinder trackers without harming graphics rendering.

These protections are enabled by default on desktop and Android, with per-site adjustments available if compatibility issues arise, and users can disable the protections or Brave Shields entirely.

Brave emphasizes a privacy-first stance and contrasts with competitors, presenting a data-backed rationale for prioritizing strong out-of-the-box privacy protections.

Future work includes extending randomization to WebGPU’s supported extensions, with ongoing testing across Nightly and Beta channels and user control over these features.

The approach injects randomization into the WebGL extension list so values seen by fingerprinting scripts vary by session, site, and storage area, preventing stable identifiers.

The updates stress a balance between privacy and minimal impact on site functionality, with mechanisms to adapt protections on a per-site basis if needed.

Brave positions itself as a leading privacy-focused browser with default-enabled protections, contrasting with opt-in or flag-based privacy features, and notes broader protections against state-based tracking and malicious scripts.

GPU fingerprinting relies on graphics APIs like WebGL and WebGPU to extract hardware data such as GPU model, driver version, and supported extensions, forming a persistent user identifier across sites.