When you visit a website, the server first receives information from your network request: your IP address, the User‑Agent header that reveals your browser and operating system, and Accept‑Language that shows your preferred language. Then the site executes JavaScript in your browser, which can measure a range of device characteristics without asking for permission. Scripts can query the GPU’s vendor and model via WebGL, read the CPU’s thread count and memory size through the navigator object, obtain screen resolution and pixel ratio, capture audio processing details with an OfflineAudioContext, and even enumerate installed fonts and browser extensions. By combining these signals, a fingerprinting script creates a hash that is highly stable over time and uniquely identifies a browser among millions of others.
The effectiveness of fingerprinting has led to its adoption as a replacement for third‑party cookies, especially after regulatory pressure limited cookie‑based tracking. Privacy‑focused browsers counteract fingerprinting in two main ways. Brave adds random noise—a technique called farbling—to hardware and software readings, making the fingerprint change frequently. Tor and the Mullvad Browser take the opposite approach: they deliberately make all users appear identical by reporting the same values for screen size, GPU, and other measurable traits, so no individual stands out. In contrast, Safari and Firefox provide only partial resistance; they still expose enough stable data for advanced trackers to single out users. Extensions that attempt to block fingerprinting, such as JShelter or Firefox’s Resist Fingerprinting feature, often break websites and, paradoxically, can make a user more unique because few people install them, giving trackers another signal to exploit. The source notes that no extension can match engine‑level protection built into the browser itself.
The consequences of widespread fingerprinting extend beyond advertising. Trackers can use the persistent identifier to build profiles of your interests, sell data to data brokers, or even offer the information to government agencies. Because the fingerprint works across devices and survives cookie clearing, VPN use, or private‑browsing modes, traditional privacy habits no longer prevent identification. Users who wish to assess how uniquely identifiable their browser is can visit coveryourtracks.eff.org, which reports the entropy contributed by each measured trait and shows whether a fingerprint would be distinguishable in a typical crowdsample. Ultimately, the source argues that avoiding tracking requires committing to a browser that implements fingerprinting resistance at the engine level, rather than relying on add‑ons or superficial settings.