Browser automationBrowser engines

Chromium fingerprint defense

Understand the native patches, startup fingerprint file, and JS shims used by the Chromium path.

Chromium fingerprint defense — contract and behavior

  • Native patches cover canvas behavior, user-agent reduction, brand lists, ALPS, and related engine surfaces in the separate chromium-build repository.
  • Weles writes a generated fingerprint config and passes it with --weles-fingerprint for the patched browser to consume at startup.
  • addInitScript helpers fill gaps that are not cleanly enforceable in C++, including the HEVC codec and Sanitizer API shims.
  • Stock Chromium is not equivalent: it lacks the command-line contract and engine-level enforcement expected by WSession.

Stay in the loop. Never miss out.

Subscribe to our newsletter and unlock Wisent insights.

Contact Careers Privacy Policy Terms of Service