Browser Fingerprinting: Profile uniqueness, leakage & injecting external fingerprints

[morpheus9393]

Hi Pydoll team & community,

the developer asked me to move this topic into a discussion, so here we go — this is a follow-up to issue #411.

I’ve been reading the docs regarding browser fingerprinting and have a few points I’d love to get clarity on.

1. Authentic fingerprints & profile uniqueness

The docs state:

“Authentic browser fingerprints. Canvas, WebGL, and AudioContext fingerprints come from real GPU and audio hardware. Navigator properties, plugins (the standard 5 PDF plugins), and MIME types reflect genuine browser state. There is nothing to configure here.”

Questions:

• Does this imply that every pydoll profile shares the exact same fingerprint, because they all tap the same underlying host hardware (GPU, audio stack)?
• If so, does this leak the real GPU and AudioContext fingerprints of the host machine to visited sites?
• Would that make it trivial for anti-bot systems to link/correlate multiple profiles back to the same physical machine?

2. Canvas fingerprint uniqueness

• Are canvas fingerprints 100% unique per profile, or do they mirror the real GPU rendering output (and thus are identical across profiles on the same machine)?
• What setup or configuration is required to get fingerprints that are not 100% unique, but still differ per profile (as is the case with a normal Chrome install)?

3. Injecting custom fingerprints

• Is there any supported or recommended way to inject custom fingerprints into pydoll profiles — either real-world fingerprints collected via JS from my own site, or auto-generated ones (e.g. using Apify Fingerprint Suite)?
• Specifically, can fingerprints from external tools like the Apify Browser Fingerprint Suite be used? If yes, what would the integration approach look like — CDP overrides, navigator patching, canvas noise injection, etc.?

4. Anti-detection / fingerprint spoofing

• Does pydoll currently support any form of fingerprint randomization or spoofing (e.g. subtle noise in canvas output, overriding WebGL renderer strings, faking AudioContext hashes)?
• If not, is this on the roadmap?

Environment (for reference):

• pydoll version: 2.22.1
• Python version: 3.14.2
• OS: Windows 10 Enterprise, 64-bit

Thanks a lot for any insights — looking forward to the discussion!