__ __ _ ____ _ \ \ / /_ _ ___| |_ / ___|__ _ _ __ _ | | \ \ /\ / / _` |/ __| __| \___ / _` | '_ \ _| || | \ V V / (_| | (__| |_ ___) | (_| | | | ||_ _| \_/\_/ \__,_|\___|\__| |____/ \__,_|_| |_| |_| _ _ _ _ | | ___ __ _ _ __ _ __ | | / \ _ __ ___ _| |_ | | / _ \/ _` | '__| '_ \| | / _ \ | '_ \/ _ \|_ _| | |__| __/ (_| | | | | | |_|/ ___ \| |_) | (_) | |_| |_____\___|\__,_|_| |_| |_(_)_/ \_\ .__/ \___/ (_) |_| W H A T C A N I L E A R N ?

Browser Fingerprint

The scary part. Cookies can be cleared. Fingerprints cannot — they are re-derived from your hardware and software every time. The ID below identifies this browser on this machine with no cookies at all. We compute it here and immediately throw it away. Trackers do not.

Hashing your canvas, audio, WebGL, fonts, and hardware

How does fingerprinting actually work?

Canvas: the page draws hidden text and shapes, then reads back the pixels. Your exact GPU, driver, and font rendering produce a subtly unique image — the same every time.

Audio: an offline audio graph processes a tone. Floating-point differences between devices leave a stable numeric signature. No sound plays.

WebGL: the 3D API reports your GPU vendor/renderer and dozens of capability limits — often enough to identify your graphics card outright.

Fonts: by measuring the width of text, a page can tell which fonts you have installed — a surprisingly personal fingerprint of your software.

Combine these with your screen, timezone, language, and hardware, hash the lot, and you get a durable identifier. That is exactly what happens below.