Camoufox is an open-source, Firefox-based anti-detect browser built for browser agents and other automated work. It has a Python interface designed to work with existing Playwright code.
What Camoufox changes
Camoufox modifies browser behavior below the usual page-script layer. The official feature reference says fingerprint values are intercepted in the C++ implementation rather than overwritten with injected JavaScript. Supported changes include navigator properties, screen and viewport values, WebGL, fonts, locale, timezone, WebRTC data, and related request headers.
The project also isolates Playwright's internal page-agent code and uses BrowserForge to generate device characteristics. Its aim is consistency: a reported operating system, graphics device, screen, fonts, locale, and network identity should make sense together.
This is different from a small stealth script, such as Playwright Stealth, that rewrites a few JavaScript properties after launch. It is also more operationally involved because the browser fork and its fingerprint data have to keep pace with Firefox and with new detection checks.
Where it gets used
Camoufox is intended for AI agents and browser automation that need Playwright compatibility while presenting varied Firefox identities. Its documentation includes fingerprint rotation, proxy-aware geolocation and locale settings, remote hosting, and human-like cursor movement.
Those features can support legitimate automated testing and agents. They can also be used for scraping or other activity a site has not approved. The browser name does not settle that question; the requested resource and observed behavior do.
What Camoufox's documentation says about detection
The project's 2026 status note is unusually direct. After a maintenance gap, the maintainers reported that an older Firefox base and newly found fingerprint inconsistencies had reduced performance, and that active development had resumed.
Camoufox also documents two remaining detection paths. A generated fingerprint can contain values that do not agree with one another, and interaction analysis may expose scripted mouse movement or timing. Moving spoofing into C++ removes some JavaScript-patching artifacts, but it does not remove the need for consistent browser, network, and behavioral evidence. The guide on how sites detect automated browsers covers those layers.
Centinel benchmark result
Centinel detected Camoufox in our September 2026 benchmark.
Camoufox belongs in a regression suite precisely because its implementation differs from stock Playwright and JavaScript stealth plugins. Testing only one automation family leaves a detector with an easy blind spot.
See what gets through your bot protection
Browser-like scraping can be hard to distinguish from ordinary visits. Request a free site audit to see which scraping tools reach your site. We run real scraping tools against your site, review the results, and email you the report.
Build a useful Camoufox test
Do not block a visitor merely because one Firefox value looks unusual. Compare the browser's claims with the connection and request, then assess what the session does. A public page, an account flow, and a protected data endpoint carry different risks.
Use the evidence to choose a policy: observe uncertain traffic, rate-limit expensive repetition, challenge when more confidence is needed, and block activity that violates the site's rules. Maintain an explicit allow path for approved agents and automation. Centinel bot management, the product tested in that benchmark, applies each of these responses per route. Test it against your own traffic.
When Camoufox is part of a regression suite, keep the browser build and test inputs with the result. Retest after either Camoufox or the protected application changes. The value of the exercise is not a permanent signature; it is proof that the detection path still works against a browser that was designed to alter the obvious signals.