b2KIT

Canvas Fingerprint Defender

Test and demonstrate canvas fingerprinting techniques. Generate noise-injected canvas to show how defenders work.

Tested tool guide Tested browser tools Checked August 16, 2026

What Canvas Fingerprint Defender does and how it behaves

Canvas Fingerprint Defender creates a canvas sample and a noise-injected version so you can observe how small pixel changes affect material used for canvas fingerprinting. The comparison demonstrates one anti-tracking tactic, not whether the browser is anonymous. A result can look unchanged to the eye while its pixel data differs. Seeing a changed result also does not prove that a privacy extension or browser setting caused it, because the tool itself can generate the defended variant. Rendering and comparison stay in the browser.

How the result is produced

1

Canvas readback

Canvas fingerprinting depends on obtaining a representation of rendered pixels. This tool supplies controlled canvas content for that experiment. The same drawing can be rasterized differently across browser, operating-system, font, display-scale, and graphics configurations. An unmodified result may therefore be reproducible within one setup without serving as a universal identifier.

2

Noise injection

The defender demonstration intentionally perturbs canvas pixel values and produces a noise-injected canvas. Even tiny changes can alter an exact byte comparison or any digest made from those bytes while remaining difficult to see. The useful question is whether repeated canvas results remain stable or are deliberately varied, not whether the picture looks visibly distorted.

Good uses

  • Explaining during a privacy review why visually similar canvases can produce different readback data after noise is introduced.
  • Comparing repeated runs before and after enabling a browser's canvas-protection setting while keeping the rest of the environment unchanged.
  • Demonstrating the narrow scope of canvas noise alongside a broader assessment of browser fingerprinting signals.

Limits and checks

  • A noisy canvas generated by this page is not evidence that the browser modifies canvas reads on other sites.
  • One changed result is ambiguous because browser, font, display scale, graphics, or operating-system changes can also affect rendering.
  • Canvas protection does not cover WebGL, audio, fonts, screen properties, network identifiers, or other fingerprinting inputs.

Common questions

Does a changed noise-injected result mean canvas fingerprinting is defeated?

No. It shows that modifying canvas pixels can stop an exact result from matching the unmodified result. A tracker may repeat measurements, identify a consistent modification, or combine canvas with other signals. Use this tool to inspect canvas perturbation, not to assign an anonymity score or certify a browser configuration.

Why can the canvases look the same if their fingerprint material differs?

Canvas readback represents pixel values, not a person's visual judgment. A small change to one or more color-channel values may be imperceptible at normal zoom yet still make the byte sequence unequal. If a digest is computed from that sequence, changed bytes can produce a different digest without making the displayed image look meaningfully different.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools