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

GPU data, combined with signals like screen resolution and fonts, can create a unique fingerprint across sessions without cookies.

This update fits a broader industry shift away from cookies toward fingerprinting-based tracking, with Brave historically prioritizing aggressive fingerprinting protections.

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

WebGL and WebGPU power rich visuals and games but also reveal hardware details such as GPU model and driver behavior to sites by default.

Brave emphasizes privacy with minimal site impact and includes mechanisms to adapt protections on a per-site basis if compatibility issues arise.

Brave positions itself as a leading privacy-focused browser, citing default-enabled protections and broader safeguards against state-based tracking and malicious scripts.

Brave is introducing stronger anti-fingerprinting protections that target WebGL and WebGPU to curb device fingerprinting via graphics APIs.

In version 1.93, Brave de-identifies WebGL vendor and renderer strings, randomizes WebGL extensions, and empties WebGPU adapter descriptors to hinder trackers while preserving graphics rendering.

Brave has not announced an exact rollout date for the update, but promises automatic improvements once it ships, with APIs still in use for browser games and data reporting kept under control.

The protections are enabled by default on desktop and Android, with per-site tuning possible; users can disable protections or Brave Shields altogether.

Brave frames this as part of a privacy-centric stance, highlighting a data-backed rationale and a concise comparison with competitors to justify out-of-the-box protections.