You open a normal webpage. No pop-up asks for microphone or location access. You haven't even closed the cookie banner yet. Behind the scenes, your browser has already played an inaudible sound in memory, drawn a hidden triangle, read your GPU model, and hashed it all into a short string.
Developer Marcin Śleszyński demonstrated this trick in his interactive article Fingerprints are the new cookies. Visit the page, and it immediately assigns you a nickname like "Giddy Beaver" and a SHA-256 hash. Refresh the tab, clear your cookies, switch on a VPN. Nothing changes—you're still "Giddy Beaver."
How Google Helped Cookies Fade Into the Background
Browser fingerprinting (identifying a user from their unique combination of hardware and browser settings without storing files on disk) grew out of a three-act third-party cookie saga.
Safari and Firefox blocked third-party cookies back in 2019–2020, and Google promised to "kill cookies" too. Five years later, its Privacy Sandbox replacement proved too clunky and ran into antitrust scrutiny. Google changed course, and its ad products began allowing device fingerprinting. As the author jokes, when even the EU moves faster on rules than Big Tech, Big Tech was clearly stalling. Fingerprints beat cookies for trackers: they aren't stored on disk, survive history wipes, and bypass standard consent banners.
Five Chatty APIs and the Akinator Effect
A script only needs five standard Web APIs—all available without user permission. OfflineAudioContext renders an inaudible 1 kHz triangle wave in memory through a compressor (new OfflineAudioContext(1, 5000, 44100)) and sums samples 4500..5000; tiny floating-point rounding differences expose your audio stack and CPU. WebGL reveals your GPU model via WEBGL_debug_renderer_info (such as "apple m4"), supported extensions, and rendered pixels of a tiny triangle (gl.readPixels).
Next, canvas draws 'Sphinx of black quartz 🦊' over a gradient and reads the pixels via ctx.getImageData(0, 0, 240, 60).data—anti-aliasing and font rendering vary by OS and GPU. Intl grabs your time zone, locale, and number formatting. That's where a VPN gives you away: your IP changes, but your time zone stays home. Finally, navigator adds CPU threads (hardwareConcurrency), memory (deviceMemory in Chrome), and language. Everything gets joined and hashed with SubtleCrypto.digest():
async function getFingerprint() {
// Time zone and locale — a VPN won't spoof these
const dt = Intl.DateTimeFormat().resolvedOptions();
const intlSig = [
dt.timeZone, dt.locale, dt.calendar,
(1234567.891).toLocaleString(),
].join('/');
// Basic hardware and browser language signals
const navSig = [
navigator.hardwareConcurrency,
navigator.deviceMemory,
navigator.language,
].join('/');
// GPU model from the WebGL debug extension
const gl = document.createElement('canvas').getContext('webgl');
const dbg = gl?.getExtension('WEBGL_debug_renderer_info');
const gpu = dbg
? gl.getParameter(dbg.UNMASKED_RENDERER_WEBGL)
: '';
// Combine all signals into a single SHA-256 hash
const raw = [intlSig, navSig, gpu].join('|');
const bytes = new TextEncoder().encode(raw);
const hash = await crypto.subtle.digest('SHA-256', bytes);
return [...new Uint8Array(hash)]
.map((b) => b.toString(16).padStart(2, '0'))
.join('');
}
Śleszyński's demo uses a strict hash: change one signal, and the hash changes. Commercial trackers are smarter—they match attributes probabilistically and recognize you even after a browser update.
It works just like the game Akinator, except your browser answers the questions. Millions of people use Chrome, millions use a Mac M4, millions use a French locale—but only a handful sit at the intersection. Information theory calls this signal entropy: each bit cuts the pool in half, and roughly 20 bits are enough to isolate one person out of a million.
Why Extensions Don't Save You—and What Actually Works
The first instinct is to install an extension like JShelter to spoof Canvas and Audio. In practice, that often makes your browser more unusual and easier to spot, while smart trackers simply drop the noisy API and use the rest. Disabling JS silences those five APIs, yet network traces remain: your IP, HTTP headers, and TLS fingerprint.
Real defense lives in the browser engine. Chrome and Edge offer almost no fingerprinting protection—in Chrome, as the author puts it, you "walk around with a passport taped to your forehead." Safari (iOS/macOS 26+) and Firefox provide partial defenses, though Firefox's strict Resist Fingerprinting mode breaks some sites. Two approaches actually work: farbling in Brave (adding tiny per-session noise to Canvas, Audio, and WebGL) and full standardization in Tor Browser and Mullvad Browser, where every user looks identical. You can test your own browser on EFF's Cover Your Tracks.

