Browser fingerprinting identifies your device by combining dozens of small technical details, your screen size, installed fonts, GPU rendering quirks, into a signature that is often unique to you. Deleting cookies does nothing to it, and opening a private window does nothing to it either.
The technique does not store anything on your device at all, which is exactly why the usual defenses fail against it entirely.
A 2010 study by the Electronic Frontier Foundation tested nearly half a million browsers and found 83.6 percent produced a completely unique fingerprint, rising to 94.2 percent among browsers running Flash or Java. That research still anchors how privacy researchers measure trackability today.
What a Fingerprint Actually Collects
A fingerprinting script reads dozens of properties your browser exposes automatically: screen resolution, installed fonts, GPU model, operating system, browser version, timezone, and language settings. Individually, none of these single you out.
Combined, they narrow the crowd fast. Researchers measure this narrowing in bits of entropy, where each bit halves the pool of browsers that could match you. Eckersley's original study found an average of 18.1 bits of entropy, enough to make most browsers statistically unique among the sample tested.
Among browsers that also exposed Flash or Java plugin data, average entropy rose to 18.8 bits, since plugin lists and their installed fonts added even more distinguishing detail. Modern browsers have dropped both plugins, but newer signals like WebGL rendering and audio processing have largely replaced the entropy they used to provide.
How Canvas Fingerprinting Reads Your Hardware
The most powerful single signal comes from the HTML5 Canvas API, a feature every browser uses to draw graphics. A tracking script quietly instructs the canvas to render hidden text or shapes, then reads back the resulting pixel data.
That pixel data varies slightly based on your GPU, its driver version, your operating system's rendering stack, and your browser's anti-aliasing settings. The output becomes a near-unique hash, generated in milliseconds, without ever showing anything on screen.
Security researchers Keaton Mowery and Hovav Shacham first documented canvas fingerprinting in a 2012 paper, showing that font rendering and graphics card differences alone could reliably distinguish one machine from another across visits.
WebGL fingerprinting works on the same principle but targets 3D rendering instead of flat graphics, extracting details about your graphics card's shader processing. Audio fingerprinting takes a third approach, running a signal through your device's audio stack and measuring how the output waveform differs by hardware and driver.
None of these techniques require permission prompts the way camera or microphone access does. They run through standard web APIs that every modern browser exposes by default, which is part of why fingerprinting spread so widely before most users understood it existed.
Why Cookies and Incognito Mode Don't Stop It
Cookies work by writing a small file to your device that a website reads back later. Deleting the file breaks the link, which is why cookie clearing has worked as basic privacy hygiene for decades.
Fingerprinting skips storage entirely. It rebuilds the same identifying signature from your hardware and software configuration every time you load a page, whether or not you accepted cookies. Our look at incognito mode covers why private browsing hides your history locally but leaves this exact signal untouched.
Incognito mode blocks local history and clears cookies at the end of a session. It changes nothing about the GPU, fonts, or screen resolution your browser exposes mid-session, so a fingerprinting script sees the same machine either way.
Fingerprinting Is Growing Even as Cookies Survive
Google retired its Privacy Sandbox initiative in October 2025, ending a five year project meant to replace third-party cookies with more private alternatives. Chrome kept third-party cookies indefinitely, with the remaining Sandbox APIs fully removed by Chrome 150 in July 2026.
That reversal surprised many people who assumed cookies were disappearing. Fingerprinting grew anyway, because Safari and Firefox have blocked third-party cookies by default for years, and advertisers, fraud detection systems, and analytics platforms wanted a tracking method that works regardless of any single browser's cookie policy.
Google cited limited real world adoption of its Privacy Sandbox APIs as a major reason for retiring the project, alongside years of pressure from regulators including the UK Competition and Markets Authority. The ad industry never fully migrated to the cookie replacement Google built, and cross-browser fingerprinting filled part of that gap regardless.
Banks and ecommerce platforms use the same underlying signals defensively, flagging device fingerprints that suddenly appear on a new account to catch takeover attempts, a use case tied closely to how passkey based authentication verifies which device is making a request.
Fingerprinting Beyond the Browser
The same logic extends past desktop browsers. Mobile apps read device identifiers, installed sensor lists, and system settings to build comparable profiles, a practice our app data collection guide breaks down in more detail.
Payment networks apply a related principle for fraud prevention, where device signals sit alongside network tokenization systems to confirm a transaction is coming from a recognized device rather than a stolen card number alone.
Streaming services and gaming platforms use similar fingerprinting to detect shared or resold accounts, comparing the device signature attached to a login against the profile the account has used historically. A sudden change in fingerprint alongside a login from an unfamiliar location is treated as a fraud signal worth flagging.
What Actually Reduces Fingerprinting
No browser setting removes fingerprinting risk completely, but some approaches shrink it meaningfully. Tor Browser standardizes its fingerprint across every user, so canvas output, fonts, and screen size look identical regardless of the underlying hardware, an approach related to how onion routing anonymizes network traffic.
Firefox includes a resistFingerprinting setting that rounds off many identifying signals. Extensions that inject random noise into canvas output can help too, though trackers have learned to detect the noise pattern itself and flag it as suspicious on its own.
The most reliable defense is a consistent, common configuration rather than a heavily customized one, since standing out from the crowd of typical browsers is itself what makes a fingerprint identifiable in the first place.
Conclusion
Browser fingerprinting works precisely because it never needed cookies to begin with. It reconstructs an identifying signature from hardware and rendering details every time you load a page, which is why clearing cookies or opening a private window changes nothing about it.
As Chrome keeps third-party cookies while fingerprinting keeps expanding, the technique looks less like a workaround and more like the tracking method the rest of the industry was quietly building toward all along.
Frequently Asked Questions
Can incognito mode stop browser fingerprinting?
No. Incognito mode clears local history and cookies but does not change your GPU, fonts, or screen resolution, the signals fingerprinting actually reads.
Does clearing cookies remove my browser fingerprint?
No, because fingerprinting does not store anything on your device. Your browser rebuilds the same signature from hardware and software details on every visit.
How accurate is browser fingerprinting at identifying a device?
EFF research found 83.6 percent of tested browsers produced a completely unique fingerprint, rising above 94 percent among browsers with older plugins like Flash installed.
Can a VPN block browser fingerprinting?
No. A VPN changes your IP address and location, but fingerprinting relies on browser and device details that a VPN does not alter at all.
Is browser fingerprinting legal?
In most jurisdictions it falls under general data privacy law, and regions enforcing GDPR or similar rules increasingly require disclosure and consent for fingerprinting used to track individuals.
Why do trackers use fingerprinting instead of just cookies?
Cookies can be deleted or blocked by the user, while fingerprinting survives cookie clearing, private browsing, and even switching between some privacy tools entirely.