Canvas, WebGL, and Audio Fingerprints: Your Invisible Hardware Signature

Among browser fingerprints, three signals are especially powerful because they reflect your hardware and drivers directly: Canvas, WebGL, and Audio fingerprints. They require no permissions; a page runs them quietly in the background.

Canvas fingerprint

The page asks the browser to draw text and shapes on an invisible canvas, then reads the pixel data and hashes it. The same code produces tiny but stable pixel differences across GPUs, drivers, operating systems, and font-rendering settings — and that difference becomes your "canvas signature."

WebGL fingerprint

WebGL handles 3D rendering and can further expose your GPU vendor and model (e.g. "NVIDIA GeForce RTX...") plus subtle differences when rendering a complex frame. The GPU model alone is highly distinctive; combined with a render hash, uniqueness is high.

Audio fingerprint

The audio fingerprint plays no sound. It uses OfflineAudioContext to synthesize a waveform in memory, processes it through an oscillator and compressor, and reads the output values. Audio-stack implementations differ slightly by device, so the values act as another stable trait.

Why it is hard to defeat

These reflect real hardware that ordinary users cannot easily change; yet deliberately randomizing them can make you stand out instead. This is why "change the UA and clear cookies" does little against fingerprint tracking.

What you can do

• Use a browser with anti-fingerprinting protection (it adds noise to Canvas/WebGL or returns uniform values).
• Avoid installing many rare fonts or extensions that add distinctiveness.
• Check your Canvas/WebGL/Audio hashes on our home page to see your exposure.