Deleting a cookie removes a stored identifier.
It does not necessarily make the browser indistinguishable from every other browser on Earth.
That is where fingerprinting enters the story.
A website can observe characteristics exposed during an ordinary visit: browser version, operating system, language, time zone, screen dimensions, graphics capabilities, supported features, font behavior, and other details.
Any one property may be common.
The combination can be much less common.
The identifier can be calculated instead of stored
A cookie works by writing a value and reading it later.
Fingerprinting can work differently.
The site asks the browser a collection of questions, combines the answers, and computes a signature. On a later visit, it asks similar questions again and compares the new signature with previous ones.
Nothing requires a file named tracker_id=12345 to sit in the cookie jar.
Mozilla describes fingerprinting as an attempt to identify users through a set of characteristics of their browser or device. Firefox now includes Fingerprinting Protection, while its stricter Resist Fingerprinting feature deliberately reduces or standardizes exposed differences. See Mozilla’s current fingerprinting guidance.
The reason those defenses exist is straightforward: uniqueness itself can become an identifier.
A fingerprint is not a magic serial number
This is where explanations often become too dramatic.
Browser fingerprints are generally probabilistic and context-dependent.
Devices update. Fonts change. Window sizes change. Browsers reduce exposed information. Privacy tools deliberately make many users look alike. Two machines can share enough characteristics to collide, while one machine can change enough to look new.
So a fingerprint can be a strong recognition signal without being equivalent to a hardware serial number.
A tracking company may also combine fingerprinting with other evidence such as account logins, IP-derived information, cookies, advertising IDs, or link identifiers.
The confidence comes from the bundle.
Cookie blocking changes the economics, not the desire to recognize
Firefox’s privacy documentation says the browser protects against known third-party trackers and fingerprinting technologies. Safari’s Tracking Prevention Policy likewise defines tracking broadly enough to include methods beyond cookies. See Firefox’s privacy notice and WebKit’s Tracking Prevention Policy.
That broader framing matters.
If privacy protection focused only on cookies, the incentive would be obvious: replace the blocked identifier with something computed from the browser itself.
Modern defenses increasingly treat recognition across contexts as the underlying problem rather than one specific storage mechanism.
That is the Surveillance Economy’s recurring lesson.
The cookie was never the goal.
The goal was remembering which browser came back.