[{"data":1,"prerenderedAt":85},["ShallowReactive",2],{"$fENm9fmefYNf2nbninwU98jEXJfFU7qGpN-RdSBFujgc":3},{"title":4,"date":5,"dateModified":6,"datePublished":7,"dateModifiedISO":7,"image":8,"content":9,"faq":10,"metaTitle":33,"metaDescription":34,"author":35,"authorBio":6,"authorLinkedin":6,"authorTitle":6,"authorPhoto":36,"lastReviewed":6,"researchBasis":6,"category":37,"readingTime":38,"related":39,"prev":57,"next":6,"toc":58,"takeaways":84},"Camoufox vs Patchright: Firefox Fork or Patched Chromium? (2026)","24 Sep 2026",null,"2026-09-24","/img/news/camoufox-vs-patchright-2026.png","\u003Cp>\u003Cstrong>Short answer:\u003C/strong> start with \u003Cstrong>Patchright\u003C/strong>. It costs one import line and adds no overhead over standard Chromium. Move to \u003Cstrong>Camoufox\u003C/strong> only when Patchright is passing fingerprint checks and still getting blocked, and the target is worth \u003Cstrong>42.49 seconds a page\u003C/strong>.\u003C/p>\n\u003Cp>That number is the entire comparison. Camoufox has the better detection record — 0% headless detection on standard tests, which no other open-source option matches. It pays for that with an average bypass time that makes a daily catalogue crawl arithmetically impossible. Patchright is faster because it is doing less, and doing less is correct until it isn't.\u003C/p>\n\u003Ch2 id=\"choose-before-you-read\">Choose Before You Read\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Your situation\u003C/th>\n\u003Cth>Use\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Node.js stack, Cloudflare blocking you\u003C/td>\n\u003Ctd>\u003Cstrong>Patchright\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Patchright passing fingerprint tests, still blocked\u003C/td>\n\u003Ctd>\u003Cstrong>Camoufox\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Tens of thousands of pages a day\u003C/td>\n\u003Ctd>\u003Cstrong>Patchright\u003C/strong> — Camoufox does not scale to this\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>A handful of high-value pages on a hard target\u003C/td>\n\u003Ctd>\u003Cstrong>Camoufox\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Target behaves differently in Firefox\u003C/td>\n\u003Ctd>\u003Cstrong>Patchright\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Blocked by behavioural scoring, not fingerprinting\u003C/td>\n\u003Ctd>\u003Ca href=\"#neither-one-fixes-behaviour\">Neither fixes this\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>You want the data, not a stealth stack\u003C/td>\n\u003Ctd>\u003Ca href=\"#the-cost-neither-one-removes\">See the last section\u003C/a>\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Ch2 id=\"two-different-patch-layers\">Two Different Patch Layers\u003C/h2>\n\u003Cp>Both tools solve the same problem by patching a browser rather than injecting JavaScript into a page. They patch different browsers, at different depths, with different bills.\u003C/p>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https://github.com/Kaliiiiiiiiii-Vinyzu/patchright\">Patchright\u003C/a>\u003C/strong> patches the Chromium binary at build time and keeps Playwright's API. It removes the \u003Ccode>HeadlessChrome\u003C/code> user-agent string compiled into the build, the WebDriver capability exposure, and the \u003Ccode>Runtime.enable\u003C/code> CDP call that Cloudflare's current detection watches for. Three targeted removals, applied before the browser process starts.\u003C/p>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https://camoufox.com\">Camoufox\u003C/a>\u003C/strong> forks Firefox's source and patches at the C++ level. Not three signals — the whole surface: canvas fingerprinting, WebGL renderer strings, AudioContext behaviour, font metrics, network timing. Every value an anti-bot script can read is controlled in the binary rather than corrected afterwards in the page.\u003C/p>\n\u003Cp>The difference in ambition explains the difference in cost. Patchright removes the tells that say \u003Cem>automation\u003C/em>. Camoufox constructs a complete, internally consistent identity for a browser that does not exist.\u003C/p>\n\u003Ch2 id=\"camoufox-vs-patchright-side-by-side\">Camoufox vs Patchright: Side by Side\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>\u003C/th>\n\u003Cth>Patchright\u003C/th>\n\u003Cth>Camoufox\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Browser\u003C/td>\n\u003Ctd>Chromium\u003C/td>\n\u003Ctd>Firefox fork\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>API\u003C/td>\n\u003Ctd>Playwright, drop-in\u003C/td>\n\u003Ctd>Playwright-compatible, Firefox\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Patch depth\u003C/td>\n\u003Ctd>Three signals, build time\u003C/td>\n\u003Ctd>Full fingerprint surface, C++\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Headless detection rate\u003C/td>\n\u003Ctd>Passes standard tests\u003C/td>\n\u003Ctd>\u003Cstrong>0%\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Average Cloudflare bypass\u003C/td>\n\u003Ctd>No added overhead\u003C/td>\n\u003Ctd>\u003Cstrong>42.49 seconds\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Memory per instance\u003C/td>\n\u003Ctd>~200MB\u003C/td>\n\u003Ctd>200MB+ per context\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Cloudflare BotFight\u003C/td>\n\u003Ctd>Passes\u003C/td>\n\u003Ctd>Passes\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Cloudflare Enterprise / Turnstile\u003C/td>\n\u003Ctd>Variable by target\u003C/td>\n\u003Ctd>Passes\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Akamai Bot Manager v4\u003C/td>\n\u003Ctd>Variable by target\u003C/td>\n\u003Ctd>Passes\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>PerimeterX / HUMAN\u003C/td>\n\u003Ctd>Variable by target\u003C/td>\n\u003Ctd>Passes\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>DataDome\u003C/td>\n\u003Ctd>Variable by target\u003C/td>\n\u003Ctd>Passes\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Behavioural scoring\u003C/td>\n\u003Ctd>Not addressed\u003C/td>\n\u003Ctd>Not addressed\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Maintenance\u003C/td>\n\u003Ctd>Small independent team\u003C/td>\n\u003Ctd>Small team, tracks Firefox releases\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Best fit\u003C/td>\n\u003Ctd>Volume on mid-tier targets\u003C/td>\n\u003Ctd>Low volume on hard targets\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Caside class=\"article__inline-cta\">\u003Cp class=\"article__inline-cta-text\">Try ScrapeWise on your own URL — \u003Cstrong>extract in 24s\u003C/strong>, no credit card.\u003C/p>\u003Ca class=\"article__inline-cta-btn\" href=\"https://portal.scrapewise.ai/login\" target=\"_blank\" rel=\"noopener\">Start Free →\u003C/a>\u003C/aside>\u003Ch2 id=\"the-42-seconds-is-the-whole-decision\">The 42 Seconds Is the Whole Decision\u003C/h2>\n\u003Cp>Run the arithmetic before choosing, because it decides for you.\u003C/p>\n\u003Cp>At 42.49 seconds per solved challenge, one Camoufox worker clears roughly \u003Cstrong>85 pages an hour\u003C/strong>, or about 2,000 a day at full utilisation. A 50,000-SKU daily crawl therefore needs on the order of 25 workers running flat out with no failures, no retries and no headroom — at 200MB+ per context each. That is a real server bill and a real orchestration problem, for data that is worth what it is worth regardless of how you collected it.\u003C/p>\n\u003Cp>Patchright at no added overhead does the same crawl on a fraction of that, and gets blocked on some of it. Which is the trade: Camoufox buys completeness at a price per page, Patchright buys throughput at a price in coverage.\u003C/p>\n\u003Cp>So the question is not "which is more stealthy". It is \u003Cstrong>how many pages, how often, and what is a miss worth\u003C/strong>. A weekly pull of 300 competitor prices from a Cloudflare Enterprise retailer is a Camoufox job. A nightly refresh of 50,000 SKUs is not, at any configuration.\u003C/p>\n\u003Ch2 id=\"firefox-is-not-a-free-swap\">Firefox Is Not a Free Swap\u003C/h2>\n\u003Cp>Camoufox is a Firefox fork, and that carries consequences beyond the stealth question.\u003C/p>\n\u003Cp>Target sites behave differently across engines. Layout, JavaScript quirks and rendering differences mean selectors validated in Chromium are not guaranteed in Firefox, and a site that quietly serves a different code path to Firefox can need separate extraction logic. If you already have a working Chromium scraper, adopting Camoufox is a rewrite of the parts that touch the DOM, not a swap of the launcher.\u003C/p>\n\u003Cp>There is a maintenance dimension too. Camoufox is maintained by a small team keeping pace with Firefox's own security releases. That creates a potential lag between a newly-discovered detection vector and a patched build — the same class of risk Patchright carries, on a larger codebase.\u003C/p>\n\u003Ch2 id=\"neither-one-fixes-behaviour\">Neither One Fixes Behaviour\u003C/h2>\n\u003Cp>Both tools address \u003Cem>technical\u003C/em> fingerprinting. Every modern WAF also scores \u003Cstrong>behaviour\u003C/strong>, and neither one touches it.\u003C/p>\n\u003Cp>Mouse-movement paths, scroll velocity, dwell time before the first interaction, keystroke cadence, the timing distribution of requests across a session — a perfectly fingerprinted browser that loads a page, reads the DOM and leaves still looks like what it is. Camoufox's 0% figure is a headless-detection result, not a promise about behavioural scoring, and on the highest-security configurations behaviour is what catches both tools.\u003C/p>\n\u003Cp>Neither gives you proxies either. A flawless fingerprint arriving from a datacentre IP that has already been flagged is refused at the edge before any of the patching matters.\u003C/p>\n\u003Cp>The full five-way matrix, including playwright-extra, the Python \u003Ccode>playwright-stealth\u003C/code> line and noDriver, is in our \u003Ca href=\"/blogs/playwright-stealth-2026\">Playwright stealth benchmark\u003C/a>. If you are choosing between vanilla Playwright and a patched build in the first place, start with \u003Ca href=\"/blogs/patchright-vs-playwright-2026\">Patchright vs Playwright\u003C/a>.\u003C/p>\n\u003Ch2 id=\"the-cost-neither-one-removes\">The Cost Neither One Removes\u003C/h2>\n\u003Cp>Both are libraries, and libraries decay. Each anti-bot vendor ships detection updates, each update needs a corresponding patch, and the gap between the two is downtime on whichever data source you were depending on. That weekly cycle is the recurring cost, and it does not appear in any install command or benchmark table.\u003C/p>\n\u003Cp>If what you need is \u003Cstrong>competitor prices, stock levels and product data arriving in your systems\u003C/strong> rather than a stealth stack to keep alive, this comparison is the wrong one to be having. \u003Ca href=\"/\">ScrapeWise\u003C/a> runs the browsers, the proxy rotation and the challenge handling and delivers structured, validated rows. It is a feed, not a toolkit: no plan and no compute units, just a balance you top up and a charge per delivered page from EUR 0.15 per 1,000, with 5 free requests on every new account.\u003C/p>\n\u003Cp>You can also call \u003Ca href=\"/scrapers\">36 ready-made scraping API endpoints\u003C/a> directly, or see how this feeds \u003Ca href=\"/use-cases/competitor-price-tracking\">competitor price tracking\u003C/a> and \u003Ca href=\"/use-cases/brand-protection\">brand protection\u003C/a>.\u003C/p>\n\u003Ch2 id=\"so-which-should-you-pick\">So Which Should You Pick?\u003C/h2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Patchright\u003C/strong> — default. One import line, no overhead, clears Cloudflare BotFight and a good share of Enterprise. Start here and find out whether you need more.\u003C/li>\n\u003Cli>\u003Cstrong>Camoufox\u003C/strong> — Patchright is passing fingerprint checks and still getting blocked, the target runs Enterprise-grade protection, and the volume is low enough that 42 seconds a page is affordable.\u003C/li>\n\u003Cli>\u003Cstrong>Both\u003C/strong> — Patchright for the bulk of the catalogue, Camoufox reserved for the handful of targets that refuse it. Common, and cheaper than running Camoufox across everything.\u003C/li>\n\u003Cli>\u003Cstrong>Neither\u003C/strong> — you want delivered rows on a schedule and would rather not maintain a stealth stack at all.\u003C/li>\n\u003C/ul>\n\u003Cp>\u003Ca href=\"/pricing\">Book a call\u003C/a>.\u003C/p>\n",{"title":11,"description":12,"badge":13,"benefits":14},"Frequently asked questions","Camoufox vs Patchright in 2026 — detection rates against bypass time, whether Firefox is a free swap, what neither one fixes, and which fits your volume","FAQ",[15,18,21,24,27,30],{"title":16,"description":17},"Is Camoufox better than Patchright?","Camoufox has the better detection record and the worse economics. It forks Firefox and patches the full fingerprint surface at the C++ level, achieving a 0% headless detection rate on standard tests that no other open-source option matches. It pays for that with an average 42.49 seconds to clear a Cloudflare challenge. Patchright patches three signals in the Chromium binary with no added overhead over standard Chromium. Start with Patchright and move to Camoufox only when it is passing fingerprint checks and still getting blocked.",{"title":19,"description":20},"How many pages a day can Camoufox actually do?","At 42.49 seconds per solved challenge, one worker clears roughly 85 pages an hour, or about 2,000 a day at full utilisation with no failures or retries. A 50,000-SKU daily crawl therefore needs on the order of 25 workers running flat out at 200MB+ per context each. That is why Camoufox suits low-volume, high-value targets and does not suit a nightly catalogue refresh at any configuration.",{"title":22,"description":23},"Can you swap a Chromium scraper straight over to Camoufox?","Not cleanly. Camoufox is a Firefox fork, and target sites behave differently across engines — layout, JavaScript quirks and rendering differences mean selectors validated in Chromium are not guaranteed in Firefox, and a site that serves a different code path to Firefox can need separate extraction logic. Adopting Camoufox on an existing Chromium scraper is a rewrite of the parts that touch the DOM, not a swap of the launcher.",{"title":25,"description":26},"Why do Camoufox and Patchright still get blocked on some sites?","Both address technical fingerprinting; neither addresses behaviour. Modern WAFs score mouse-movement paths, scroll velocity, dwell time before the first interaction, keystroke cadence and the timing distribution of requests. A perfectly fingerprinted browser that loads a page, reads the DOM and leaves still looks like what it is. Camoufox's 0% figure is a headless-detection result, not a promise about behavioural scoring. Neither tool gives you proxies either, and a flagged datacentre IP is refused at the edge before any patching is evaluated.",{"title":28,"description":29},"Can you run Patchright and Camoufox together?","Yes, and it is usually cheaper than running Camoufox across everything. Patchright handles the bulk of the catalogue at no overhead, and Camoufox is reserved for the handful of targets that refuse it — typically Cloudflare Enterprise, Akamai Bot Manager v4 or PerimeterX-protected sites where a block means losing a data source rather than losing a page.",{"title":31,"description":32},"What are the alternatives to running a stealth stack at all?","Both tools are libraries, and libraries decay — each anti-bot vendor ships detection updates, each update needs a corresponding patch, and the gap between the two is downtime on whichever source you depend on. If what you need is competitor prices, stock levels and product data arriving in your systems rather than a stealth stack to keep alive, a managed feed removes the question. ScrapeWise runs the browsers, proxy rotation and challenge handling and delivers structured, validated rows from EUR 0.15 per 1,000 delivered pages, with 5 free requests on every new account.","Camoufox vs Patchright 2026: 0% Detection at 42s a Page","Camoufox vs Patchright in 2026: 0% headless detection at 42.49s a page against patched Chromium at no overhead. Which one your volume can actually afford.","Siim Brazier","/img/team/siim.jpg","Alternatives",6,[40,45,51],{"slug":41,"title":42,"image":43,"date":5,"category":37,"excerpt":44},"patchright-vs-playwright-2026","Patchright vs Playwright: What Patchright Actually Patches (2026)","/img/news/patchright-vs-playwright-2026.png","Patchright vs Playwright in 2026. The three signals Patchright removes, the drop-in migration, what still gets you blocked, and when to stop patching.",{"slug":46,"title":47,"image":48,"date":49,"category":37,"excerpt":50},"oxylabs-vs-apify-web-scraping-2026","Oxylabs vs Apify: Which Web Scraping Platform Should You Choose in 2026?","/img/news/oxylabs-vs-apify-web-scraping-2026.png","23 Sep 2026","Oxylabs vs Apify compared for 2026: proxy access vs Actor marketplace, how each prices, e-commerce and AI coverage, and which one your bottleneck actually calls for.",{"slug":52,"title":53,"image":54,"date":55,"category":37,"excerpt":56},"decodo-smartproxy-alternative-web-scraping-2026","Decodo (Smartproxy) Alternative for Web Scraping: 4 Options Compared [2026]","/img/news/decodo-smartproxy-alternative-web-scraping-2026.png","22 July 2026","Decodo (formerly Smartproxy) is a proxy-first scraping platform. Compare 4 Decodo alternatives on proxy quality, scraping APIs, cost and upkeep.",{"slug":41,"title":42},[59,63,66,69,72,75,78,81],{"level":60,"text":61,"id":62},2,"Choose Before You Read","choose-before-you-read",{"level":60,"text":64,"id":65},"Two Different Patch Layers","two-different-patch-layers",{"level":60,"text":67,"id":68},"Camoufox vs Patchright: Side by Side","camoufox-vs-patchright-side-by-side",{"level":60,"text":70,"id":71},"The 42 Seconds Is the Whole Decision","the-42-seconds-is-the-whole-decision",{"level":60,"text":73,"id":74},"Firefox Is Not a Free Swap","firefox-is-not-a-free-swap",{"level":60,"text":76,"id":77},"Neither One Fixes Behaviour","neither-one-fixes-behaviour",{"level":60,"text":79,"id":80},"The Cost Neither One Removes","the-cost-neither-one-removes",{"level":60,"text":82,"id":83},"So Which Should You Pick?","so-which-should-you-pick",[],1790238196327]