Fingerprint management for the Afina antidetect browser

A combination of browser-readable properties (UA, platform, WebGL renderer, Canvas hash, AudioContext, fonts, screen size, language, time zone, hardware concurrency, deviceMemory, etc.) that uniquely identifies your browser. Anti-detect browsers manage these properties per profile so accounts don't share an identity.

Pulled from real devices. We maintain an upstream catalogue of actual macOS / Windows fingerprints; each new profile gets a consistent set drawn from it. Internal consistency is what most checkers actually test for — generated noise fails immediately.

Yes. Through the API or partial fingerprint payload you can override individual fields (WebGL vendor, languages, screen size, deviceMemory etc.) and Afina merges your overrides over the generated base. Some fields are server-managed for consistency (UA, BrandFullVersion) — see docs/API for the full list.

Optional. Each profile carries four noise toggles (isNoiseCanvasEnabled/Audio/Rects/GL). When on, Afina injects per-profile deterministic perturbations that look like real hardware variation. When off, the profile reads pixel-identical to the source device.

Catalogue and noise logic update with each desktop release. New fingerprint surfaces (new APIs in Chrome) are added as soon as upstream catalogues cover them. You don't have to do anything — install the latest Afina.

Yes. The fields we generate (and don't allow you to override unless you know what you're doing) are pulled from a real machine of that OS/chip combo, so cross-property checks (WebGL renderer ↔ deviceMemory ↔ AudioContext signature) line up the way they would on actual hardware.