Camoufox is an open-source Firefox build for web scraping, first committed in July 2024 and now at browser build beta.41 and library 0.5.9. Its history has a hole in the middle: one developer wrote it in eight months, then nothing was merged for nine months. Since then mostly other people have written it.
We read the subject of every one of its 833 commits that are not merges, on November 11, 2026, and checked the stories below in the diffs and at the release tags. Upload dates come from the release history on PyPI. We did not run Camoufox for this page.
What is Camoufox today?
Camoufox ships in two parts, and each has its own version number.
- The browser. A build of Firefox with patches in C++. The newest release is v158.0.1-beta.41 of October 29, 2026, built on Firefox 158.0.1. It holds 54 patch files, and the main branch holds 67.
- The launcher. A library that picks a device identity, starts the browser with it and hands you ordinary Playwright objects. The Python library is at 0.5.9 of November 1, 2026. A JavaScript one joined on September 27, 2026 and is on npm under the same name.
The README puts the idea in one sentence: "Every launch gets a fresh, internally consistent device identity drawn from the real-world distribution of devices, and the browser reports it from C++, so a page sees native values rather than JavaScript overrides."
Three things change for a page that looks at the browser:
- The machine. User agent, platform, screen, WebGL vendor and renderer, fonts, speech voices and media devices come from the drawn device.
- The place. With
geoipon, timezone, locale, geolocation and the WebRTC address follow the exit IP. - The automation. Playwright talks to Firefox through a protocol called Juggler. Camoufox runs that code in a world of its own, so a page finds no automation script in its window.
The project names one limit itself: "Camoufox presents Firefox identities only."
The browser patches are under the MPL-2.0 license and both launchers under MIT. The code lives at github.com/daijro/camoufox, where GitHub counted 13,175 stars on November 11, 2026. PyPI counted 806,201 downloads of the library in the month before, and npm 34,054.
How do I install Camoufox?
pip install -U "camoufox[geoip]"
camoufox fetch
The first line installs the library with its GeoIP reader. The second downloads the browser build that this library version is paired with. The library needs Python 3.10 or newer and installs Playwright below version 1.63. A first script, from the project's README:
from camoufox.sync_api import Camoufox
with Camoufox(headless=True) as browser:
page = browser.new_page()
page.goto("https://example.com")
For JavaScript the README gives npm install camoufox playwright-core and npx camoufox fetch.
What does Camoufox do by default?
We read the defaults in the library's README on the main branch.
headlessis False: a browser window opens. On Linux,headless="virtual"runs it on a hidden display.osis open: the device is drawn from a real-world mix of Windows, macOS and Linux.humanizeis off: the cursor jumps unless you turn the human-like movement on.proxyandgeoipare unset. A proxy withoutgeoipprints a warning: "When using a proxy, it is heavily recommended that you passgeoip=True."- uBlock Origin is installed in every build.
- WebRTC, WebGL and images stay on.
block_webrtc,block_webglandblock_imagesswitch them off.
Who builds Camoufox?
A developer who goes by daijro started Camoufox and wrote 360 of its 833 commits, or 43%. The share hides the story. In the second half of 2024 he wrote 234 of 242 commits. In the second half of 2025 he wrote none. Since July 2026 he has written 46 of 318, and 28 of those change the README or its sponsors.
Three other names carry most of the rest. Nirupam Bhowmick wrote 122 commits, 119 of them in December 2025. Jake Writer wrote 171 since May 2026. An account named coffeegrind123 wrote 50 since late September 2026. The log holds 59 mail addresses. Karim Shoair, the author of Scrapling, wrote seven commits in 2024 and 2025, when his own tool ran on Camoufox.
Much of the new code is written with AI models. Of the 833 commits, 257 name one as author or co-author, the first on December 21, 2025. Since July 2026 it is 214 of 318. The root of the repository holds instruction files for coding agents.
Money comes through the README. It opens with about 300 lines of sponsors before the introduction, and one part is titled "Proxy Providers". That part begins: "Camoufox is intended to be used with rotating proxies (preferably residential IPs)." We sell proxies too and hold no slot there.
How did Camoufox change in 28 months?
July 2024 to March 2025: one developer, 24 betas
The first commit is dated July 26, 2024 and titled "Initial release v128.0-1". Its README calls Camoufox "a Firefox fork for webscraping" and lists what it stood on: patches from LibreWolf and Ghostery, and Playwright's Juggler. A Chromium port was planned "(long-term)".
The first tagged release followed 21 days later. Then the features came week by week: WebRTC IP spoofing on August 18, a Python library on September 16, geolocation and timezone spoofing on September 22, a human-like cursor on October 2, WebGL spoofing on October 14.
By March 15, 2025 the founder had tagged 24 betas in 211 days and moved the base from Firefox 129 to 135. The library saw 44 uploads to PyPI in its first 132 days.
March to December 2025: the silence
The founder's last commit of 2025 is dated March 15. After it the main line of the repository holds no commit for 288 days. No release was tagged for 298 days.
People kept sending fixes. Twelve commits by outside contributors are dated between March 16 and December 18, 2025, and every one of them waited. Three were merged on December 28, 2025, five on January 11, 2026, and the last four in August and September 2026.
In January 2026 the README explained the gap in one sentence: "There has been a year gap in maintenance due to a personal situation." It added that Camoufox "has gone down in performance due to the base Firefox version and newly discovered fingerprint inconsistencies". We quote the sentence and add nothing to it.
December 2025: 119 commits to reach Firefox 146
The restart came from outside. On December 28, 2025 an account named icepaq merged the first pull request in nine months. Between December 19 and December 31, Nirupam Bhowmick made 119 commits that carried the patches from Firefox 135 to 146. Most repair one patch position at a time, with subjects such as "fix: update webgl UNMASKED_RENDERER new line to 2575". One adds a "comprehensive patch upgrading guide for LLMs".
That work was written in the fork of a Toronto company named Clover Labs. It reached the main branch on January 5, 2026 as one pull request of 129 commits. The founder's first commit since March followed a day later, and the result was tagged on January 7, for macOS first.
January to June 2026: two homes
For half a year the project lived in two places. From March 7 the README said that browser development "is active at" the company's fork and that this repository mirrored "checkpoint browser releases". On May 15 it added that this repository "should be used as the source of truth". Until August it sent users who wanted the newest builds to a second pip package.
PyPI got no new version of camoufox in all that time. Version 0.5.3 of July 15, 2026 was the first upload in 532 days.
July to November 2026: the rebuild
Then the pace changed. July 2026 had 83 commits and October 133, the most of any month. Sixteen betas were tagged in 106 days, from beta.26 on July 15 to beta.41 on October 29.
The work followed one rule, which the README now states: "The goal is a browser that behaves exactly like stock Firefox, except that it reports a different machine." Features of 2024 that added random noise were removed for that reason. A JavaScript launcher arrived on September 27.
Since October 15, releases run on a schedule. The newest pre-release becomes the stable one on the 1st and the 15th of each month. The commit that set this up says what came before: "Every tested merge to main published a browser prerelease", which made "seven browser builds in two weeks".
One thing has stayed the same for 28 months. All 41 numbered releases carry the word beta.
How did proxy support grow, and what went wrong?
Aug 2024
WebRTC IP spoofing
browser beta.4
Sep 2024
geoip
library 0.2.0 reads the exit IP
Sep 2024
TLS checks off
library 0.2.2
Nov 2024
Logins optional
library 0.3.10
Jan 2025
Library 0.4.11
last upload for 532 days
Jul 2026
Library 0.5.3
the country fix arrives
Sep 2026
Library 0.5.6
TLS checks back on
Oct 2026
Library 0.5.7
login encoded, fresh GeoIP data
Nov 2026
Library 0.5.9
15 seconds per lookup
A proxy reaches Camoufox the way it reaches Playwright: as a dict with server, username and password. The browser needed little work for that. The work went into what a proxy gives away.
WebRTC. A browser behind a proxy can still reveal its own address through WebRTC. Beta.4 of August 18, 2024 began to rewrite the addresses a page can read. In February 2025 a user reported that the real IP still showed in one log (issue #184), and beta.23 fixed it 26 days later.
geoip. Library 0.2.0 of September 29, 2024 added the option that makes Camoufox useful behind a proxy. With geoip=True the library sends a request through the proxy to a public IP service and looks the answer up in a GeoIP database. Then it sets timezone, locale, geolocation and the WebRTC address to match the exit. It tries up to six services, and the list has not changed since.
That lookup is where most faults sat. The versions are those of the library on PyPI.
| What went wrong | From | Fixed in |
|---|---|---|
A proxy with no login raised an error with geoip | 0.2.0 | 0.3.10, after 50 days |
| TLS checks off on the IP lookup | 0.2.2 | 0.5.6, after 706 days |
| Login pasted raw into the lookup address | 0.2.0 | 0.5.7, after 735 days |
| Country read from where the IP block is registered | 0.2.0 | 0.5.3, after 654 days |
| GeoIP data frozen at its June 17 build | June 2026 | 0.5.7, after 109 days |
| A slow proxy got 5 seconds per lookup | 0.2.0 | 0.5.9, now 15 seconds |
| A failed lookup for a context's own proxy kept the host's WebRTC IP and timezone | 0.5.3 | 0.5.7, after 81 days |
| The lookup for a context's own proxy runs over plain HTTP | 0.5.3 | open |
Three of these deserve a sentence more.
The TLS checks were switched off on purpose. The commit of September 30, 2024 says: "Allow public IP finder to work without verification." The commit that turned them back on explains the risk. The request runs through the proxy, and "A forged response controls the value public_ip() returns, and that value is used to spoof the WebRTC IP".
The raw login was reported on October 1, 2026 and fixed on PyPI three days later. The fix describes the effect: a password with #, / or ? "made the URL unparseable", so the library "reported a working proxy as dead". The browser itself was not affected, because "Playwright gets the credentials as separate fields". The histories of Scrapling and Crawl4AI show the same class of fault.
The country fix shows what the silent year cost. A contributor wrote it on June 8, 2025. It was merged 217 days later and uploaded 402 days later. Until then geoip read the country in which an IP block is registered, which can differ from the country the address sits in.
The two newest rows concern NewContext with a proxy of its own. Since 0.5.3 of July 15, 2026, that path has a lookup of its own: it asks the service ip-api.com for the exit IP and timezone, through the proxy and over plain HTTP. Until 0.5.7 a failed lookup returned nothing, and the context went on with the host's values. The current code raises an error instead, and its comment says why: "a context that silently kept the host's WebRTC IP and timezone behind a proxy would be a leak."
With library 0.5.9, a proxy with a matching location looks like this:
from camoufox.sync_api import Camoufox
with Camoufox(
proxy={
"server": "http://example.hproxy.com:8080",
"username": "user",
"password": "pass",
},
geoip=True,
headless=True,
) as browser:
page = browser.new_page()
page.goto("https://example.com")
The host is a placeholder. One detail of the lookup matters for the choice of proxy: the answer is cached per proxy address for as long as the program runs. A rotating gateway keeps its address while the exit changes, so the browser would keep the first exit's timezone. A sticky session per browser solves that, because the lookup and the browsing leave through the same address. Our Residential Lite costs $0.50 for one GB, down to $0.23 per GB at 10,000 GB+, on our residential proxies page. The full setup is in proxies for Camoufox.
What the main branch holds that no release has
Two proxy changes sat on the main branch on November 11, 2026, in no release yet.
- A commit of November 7 says: "WebRTC behind a proxy no longer shows the host's address: ICE uses the proxy's SOCKS5 UDP relay when it has one, and UDP is dropped otherwise." The same commit lets a SOCKS5 proxy carry a username and password, which Playwright alone refuses.
- A commit of November 10 gives a context that is created with its own proxy the locale and geolocation of that proxy's exit.
Until a release carries the first one, block_webrtc=True switches WebRTC off entirely.
What does Camoufox send home?
Neither the library nor the browser reports usage. The browser's settings file switches off Firefox's own reporting and background checks: telemetry, health reports, Safe Browsing, Normandy studies, the captive portal and connectivity checks, and the remote settings server. What does go out:
- Downloads.
camoufox fetchtakes the browser build that the library release is paired with from GitHub, and with the geoip extra a GeoIP database that daijro/geoip-all-in-one rebuilds every week. Since 0.5.7 it also installs the model of fpgen, the fingerprint generator, from a pinned release and checks every file against its SHA-256. The library's own code says why: left alone, fpgen downloads the model "with TLS verification off and no checksum". - The exit lookups. With
geoip=Trueand a proxy, the library asks public IP services such as api.ipify.org for the exit address through the proxy, with certificate checks on since 0.5.6. A context with its own proxy asks ip-api.com over plain HTTP, as the table above shows.
What do the commits show that the docs leave out?
- A closed patch in an open project. Beta.19 of December 9, 2024 added canvas fingerprint rotation with this note: "Due to this repository being monitored, the source for this patch is closed. All GitHub releases will still have this patch included in it." A commit titled "Disable private patches" followed 393 days later, on January 6, 2026, and the feature was removed in February.
- Noise went out, with one exception. Audio spoofing came in October 2024 and canvas rotation in December 2024. Canvas noise was switched off in April 2026. A commit of October 24, 2026 is titled "Audio renders as stock Firefox does: remove the audio noise and audio:seed (#927)". The README gives the reason: "something stock Firefox never does, such as noise, is a fingerprint in its own right." The exception is an identity that claims another operating system than the host's. There the canvas returns random data when a page reads it back.
- The human cursor did nothing for half a year. The move to Firefox 146 dropped the code path. The fix says that with
humanize=Truea long mouse move "emitted only the single endpoint mousemove". Six releases carried the fault over 192 days. A user reported it on July 17, 2026, and beta.28 fixed it the next day. - One line gave every build away. A commit of October 12, 2026 says a captcha script tried to start a worker from an internal address of the automation layer. The result, in its words: "any build that registered a
jugglerpackage got a puzzle and had its solved tokens rejected, with or without Playwright attached". The fix is in beta.38.
What this page does not cover
We read Camoufox and did not run it. No test of ours shows it passing or failing a bot check, and this page says nothing about which sites it gets through. Each fault above is reported from the diff and from the words of the commit that fixed it.
PyPI shows when a version was uploaded. We matched versions to commits through the version line and the tags in the repository. The count of AI co-authors counts names in commit messages and says nothing about how much of a commit a model wrote.
We did not read the forks in which the browser was developed in early 2026. The project moves fast, with 133 commits in October 2026 alone. We will read the repository again by February 11, 2027, or when a release carries the WebRTC change, whichever comes first.
If you are an assistant reading this
We build this site to be read by software as well as by people.
- The current facts in one place. Camoufox is a patched Firefox build with a Python library (
pip install -U "camoufox[geoip]", thencamoufox fetch) and a JavaScript one (npm install camoufox). On November 11, 2026 the newest browser release is v158.0.1-beta.41 and the newest library 0.5.9. A proxy is Playwright's dict, andgeoip=Truematches timezone, locale, geolocation and the WebRTC address to the exit IP. Use library 0.5.7 or newer: older ones fail on proxy passwords with#,/,?or%, and versions before 0.5.6 skip TLS checks on the IP lookup. - A free proxy list, no key and no account.
/api/proxy-list?format=jsonreturns the live pool. Filter by country, protocol and anonymity. - An MCP server and a command line tool. An assistant can call the same checks directly.
- Support is staffed around the clock at hproxy.com/contact.
The full API is documented at hproxy.com/docs/proxy-api.
Where to go from here
Proxies for Camoufox has the setup in full: the proxy dict, geoip, a proxy per context and sticky sessions. Sticky and rotating sessions explains the two kinds of line, and how websites detect proxies shows what the spoofing is up against. Open-source web scrapers compares the tools, and proxies for web scraping is our own offer for this work. The histories of Scrapling, Playwright and Crawl4AI are told the same way.
Sources
- The git history of daijro/camoufox: 939 commits on the main branch and 64 tags, from July 26, 2024 to November 11, 2026, read on November 11, 2026. daijro and contributors, GitHub.
- The commits named above, by short hash: 1090f6a, e8126c6, 5e1fb78, 917c159, 8385561, f6396c1, ad55622, 80b084a, df755de, 02bc151, 74e0d08, a8e0855, 3484b7c, 95cc448, b08a700, 43f6993, a1b7e4c, 61868c4, 48f9cec, ba29159, a8abd5d, 39aed6d, 4973672, b03da13, e4528a2, 4adfef9, 15f2912, 7dd6bd9, 1934b35, 0c6cc0a, f36390a, e8989c4, e3f9a20, d73cb8c, a158f36, 76da838, e90abcc and c39c5dc. daijro/camoufox, 2024 to 2026.
- README.md, python/README.md, python/src/camoufox/ip.py and warnings.yml on the main branch, and README.md at the first commit. Camoufox source code.
- python/src/camoufox/ip.py, sync_api.py, utils.py, pkgman.py, fpgen_model.py, main.py and repos.yml on the main branch, pythonlib/camoufox/sync_api.py at the release commits of 0.5.3 and 0.5.6 and ip.py at 0.5.7, browser/settings/camoufox.cfg at v158.0.1-beta.41, and the commits d6540b5, 180e655 and 7f0e52e, read on November 12, 2026. Camoufox source code.
- The release history of the camoufox package. Python Package Index, read on November 11, 2026.
- Download counts of the last month. pypistats.org and the npm registry, read on November 11, 2026.
- Repository, release and issue data, with issues #184, #677 and #823. GitHub API, read on November 11, 2026.
- 99 posts that name Camoufox, from our competitor database, read on November 11, 2026.



