Realistic Firefox binary to pair with browser_type='firefox'

[feder-cr]

browser_type='firefox' here already works well. I maintain invisible_playwright, a Playwright wrapper around a Firefox build patched at the source level for a realistic fingerprint (no injected JS), which pairs directly with this option via executable_path. Could be a useful mention for crawls that hit bot detection on Chromium. Happy to write a short example if there's interest.

[Pijukatel]

Hello, in avoid blocking we have examples of using Camoufox and CloakBrowser

There are other similar projects available, but we have just those two examples; by no means an exhaustive list.

I haven't had the opportunity to compare invisible_playwright against these two. Did you do any such comparison? Do you think there are specific challenges where invisible_playwright is more suitable?

[feder-cr]

Honestly I haven't run a head-to-head benchmark against Camoufox or CloakBrowser, so I won't claim it wins. Architecturally invisible_playwright is a patched Firefox where the fingerprint (GPU, canvas, fonts, audio, WebRTC, and a few hundred other fields) is derived from a seed at the C++ source level and delivered through prefs, and it keeps the standard Playwright Browser/Context/Page objects so it drops into existing code. Camoufox is in the same patched-Firefox space; the main practical difference here is the seed-stable persona (same seed gives the same identity across runs) and a pure-config core with no Playwright dependency. It fits best when you need many reproducible identities from a seed with a normal Playwright API. If it helps I'm happy to put together a like-for-like comparison on a shared test set.

[Pijukatel]

I am trying to find the right place for this, as it could be relevant for many Crawlee users. What do you think about writing one article at https://crawlee.dev/blog ? (Example of the last one: apify/crawlee#3734)

I think that an article that compares different state-of-the-art existing "stealthy" automation browsing methods would be really interesting to crawlee users; it would give you and the readers a good idea of how your tool performs compared to existing tools, and when demonstrated on specific sites where other tools fail, it would give you a nice way to promote it.

@souravjain540 , could an article like this qualify for a reward under "Write for Apify program" ?