How Canvas 2D, WebGL & AudioContext Fingerprinting Work
Hardware Browser Fingerprinting characterizes a client environment by measuring deterministic subpixel differences in GPU shader precision, OS font hinting, and floating-point audio DSP buffers — operating completely independently of HTTP cookies.
While HTTP cookies store arbitrary state labels inside a local profile folder, graphics and localization APIs query the underlying host platform directly. You can inspect your live hardware digest using our Browser Fingerprint.
1. Canvas 2D Subpixel Anti-Aliasing
When a browser executes ctx.fillText() across serif fonts, mathematical glyphs, and alpha-blended arcs, rasterization passes through DirectWrite (Windows), CoreText (macOS), or FreeType (Linux) and hardware GPU shaders. Edge pixels differ by 1–2 RGB levels across GPU families, producing a deterministic FNV-1a or SHA digest.
2. WebGL Renderer & Shader Precision
Through WEBGL_debug_renderer_info, web applications inspect the graphics driver string (such as Apple Metal, NVIDIA Direct3D11, or Mesa Vulkan), maximum texture dimensions, and extension capabilities — essential for diagnosing cross-platform rendering issues.
3. OfflineAudioContext DSP Profiling
Rendering a silent 44.1 kHz triangle oscillator through a dynamics compressor reveals subtle floating-point rounding differences across CPU architectures (x86_64 vs ARM64) and browser engines.