What is being compared

After development of Camoufox moved to CloverLabs in 2026, its public repository grew past 750 forks. Most are mirror bots with no commits of their own. This page compares stock Camoufox against the three forks that actually change anti-detect behavior, and records which one to run against a real target. The comparison is grounded in our 2026-06 testing against Datadome on leboncoin.fr, not on the forks’ stated goals.

Comparison table

Official Camoufoxcamoufox-reverseLeooNic/camoufoxJWriter20/camoufox
Base Firefox135 stable, 146 (v146-hardware)135149146
Headline changebaseline fingerprint DB + Jugglerengine-level PropertyTracercontent-aware canvas noise, humanized mouse, RDPBrowserWebRTC-leak fix, system-ui font, pytest suite
Runs under standard Playwright stackyesyes (raw Playwright + CAMOU_CONFIG)no, RDP onlyyes
Canvas noiseoff by defaultn/a (tracer)content-aware in source, not activatable in published buildinherits stock behavior
WebRTC under HTTP proxyleaks real WAN IP (srflx)n/anot tested at runtimeno candidates, no leak
Datadome on leboncoin ad pages~0 to 5% blockedn/anot runnable100% blocked
What it is good fordefault scrapinganalyzing detectorsreading the canvas technique in sourceclosing a WebRTC leak with SOCKS

Key differences

The counterintuitive result is the one that matters. JWriter20 is the fork built to be stealthier, and it was blocked on every leboncoin ad page while stock Camoufox passed almost all of them. The block reproduced in both run orders and with the spoofed OS pinned, and the JS, TLS/JA3-JA4, and HTTP/2 fingerprints were identical between the two builds. So the signal Datadome reacts to is structural to the JWriter20 build, in its request or connection behavior, not in any static fingerprint. A more-patched fork is not automatically a safer one. See webrtc-ip-leak for the leak JWriter20 does fix.

LeooNic is the most ambitious on paper. Its content-aware canvas noise is a genuine answer to the WWW’25 Pixel-Recovery attack (see canvas fingerprinting), but the published Firefox 149 build does not launch under the standard Playwright stack and only runs through the author’s own RDP tooling, and we could not activate the canvas seed externally. The innovation lives in the source, not yet in a usable artifact.

camoufox-reverse is not a contender at all. It is a measurement instrument: an engine-level PropertyTracer that shows which DOM getters a detector reads. We used it to watch Datadome on leboncoin, not to scrape.

When to use which

For scraping a Datadome or Cloudflare target today, run stock official Camoufox on a clean residential IP, navigating from the homepage rather than deep-linking. It outperformed every fork in our testing. Reach for camoufox-reverse when you want to understand what a detector reads, not to run production traffic. Consider JWriter20 only when a WebRTC leak under a proxy is your specific problem and you are on SOCKS5, and even then weigh it against its much higher Datadome block rate. Treat LeooNic as a source to read rather than a build to deploy until its Firefox 149 port stabilizes.

Sources


The Web Scraping Wiki is compiled from the tests and research published on The Web Scraping Club, the newsletter for web scraping professionals. Subscribe to get the next article in your inbox.