Skip to content

The history of undetected-chromedriver and nodriver: what they are and how 438 commits made them

undetected-chromedriver: no release since February 2024, almost two million downloads a month. Its history and nodriver's, read from all 438 commits.

Billal AinaouiNovember 22, 2026Updated November 22, 202614 min read

The history of undetected-chromedriver and nodriver: what they are and how 438 commits made them

undetected-chromedriver is a Python package that patches the ChromeDriver behind Selenium, first committed in December 2019 and last released in February 2024. It still gets almost two million downloads a month. Its author moved on to a successor, nodriver, three days after that last release.

We read the subject of every commit in both repositories that is not a merge, 284 and 154 of them, on November 11, 2026, and checked the stories below in the code. Neither repository has a single release tag, so versions and dates come from PyPI. We ran neither tool for this page.

What are undetected-chromedriver and nodriver today?

Both are Python packages by one author, and both start a real Chrome that hides the usual signs of automation. They differ in how they reach the browser.

undetected-chromedriver downloads Google's ChromeDriver, patches the binary and drives Chrome through Selenium.

  • Newest version: 3.5.5 of February 17, 2024. On November 11, 2026 that upload was 998 days old.
  • Downloads: 1,972,753 in the last month.
  • Repository: 12,899 stars. Issues and pull requests are switched off.
  • License: GPL-3.0.

nodriver uses neither Selenium nor a driver binary. It talks to Chrome directly over the DevTools protocol, and its code is asynchronous.

  • Newest version: 0.50.99 of October 26, 2026.
  • Downloads: 287,266 in the last month.
  • Repository: 4,926 stars, 10 open issues.
  • License: AGPL-3.0.

The package without a release is downloaded 6.9 times as often as its successor. The code lives at github.com/ultrafunkamsterdam/undetected-chromedriver and github.com/ultrafunkamsterdam/nodriver.

How do I install them?

pip install undetected-chromedriver setuptools

The second package matters on Python 3.12 and newer, and the history below says why. A first script, from the project's README:

import undetected_chromedriver as uc
driver = uc.Chrome()
driver.get('https://nowsecure.nl')

For nodriver:

pip install nodriver
import nodriver as uc

async def main():
    browser = await uc.start()
    page = await browser.get('https://www.nowsecure.nl')

if __name__ == '__main__':
    uc.loop().run_until_complete(main())

Both need Chrome, or another Chromium browser, installed on the machine. nodriver needs Python 3.9 or newer.

What do they do by default?

We read the defaults in the constructor of each package on its main branch.

  • A window opens. headless is False in both. The old README says of headless mode: "headless is still WIP. Raising issues is needless".
  • The sandbox differs. undetected-chromedriver has no_sandbox=True: Chrome starts without its sandbox unless you say otherwise. The release notes of version 3.1.6 from October 2022 say "added no_sandbox, which defaults to True". nodriver has sandbox=True.
  • The newest driver. With version_main=None, undetected-chromedriver downloads the driver for the newest stable Chrome. For an older browser the README advises passing its major version, as in uc.Chrome(version_main=95).
  • A fresh profile. nodriver creates a new profile for each run and removes it on exit.
  • No proxy is set in either.

Who builds them?

One person. He goes by ultrafunkamsterdam, and his GitHub profile gives Haarlem as his location. He wrote 252 of the 284 commits of undetected-chromedriver under six spellings of his name, and 150 of the 154 commits of nodriver.

His log is short on words. Of the 284 subjects in the old repository, 155 are the defaults of GitHub's web editor, such as "Update init.py" or "Add files via upload". The release notes live in the README, written in his own voice.

Two helpers stand out. An account named sebdelsol wrote ten commits in 2022, and the README thanks him for his help in the issues "completely voluntarily, you must be crazy :)". An account named jdholtz wrote six in August 2023, when Chrome 115 changed where drivers are downloaded.

The tracker has a history of its own. In February 2023 the README gained this line: "I will be putting limits on the issue tracker. It has beeen abused too long." On November 11, 2026 the repository had issues switched off, and GitHub answered a request for its pull requests with "Pull requests are disabled for this repo". The counter of open items still read 1,142.

Uploads to PyPI per year, undetected-⁠chromedriver and nodriverVersions uploaded per calendar year. 2026 runs to November 11.
  • undetected-chromedriver
  • nodriver
The old package got its last upload three days before the first upload of the new one.
Source: HProxy count from the release histories on PyPI, 104 uploads, read on November 11, 2026 · hproxy.comProxy.

How did they change in seven years?

2019 and 2020: one file

The first commit is dated December 22, 2019, and 19 more followed the same day. At the end of that day the package was one Python file of 195 lines. It downloaded ChromeDriver, patched it and patched Selenium. The README said: "Not tested on Chrome higher than 79!"

For eight months the only way to install it was from GitHub. A commit of September 3, 2020 is titled "added to pip package index", 256 days after the start. In December 2020 the patch still replaced a 26-character marker in the driver binary with one fixed string. A commit titled "randomize cdc_string and silicenced output" made it a random one.

2021: version 2, version 3 and 22 uploads

In 2021 the package was rewritten twice. Version 2.0.0 arrived on January 17 as a second implementation next to the first. Version 3.0.0 followed on May 24. In version 3.1.0 of December 22 the new code became the main module, with the note "added new anti-detection logic!"

The package grew from 251 lines to 1,781 in those months. PyPI received 22 uploads that year, the most in the life of the package.

Python lines in undetected-⁠chromedriver at eight versionsLines of all Python files in the package at the commit of each version.
The package grew sevenfold in the first five months of 2021 and has stayed between 1,700 and 2,100 lines since.
Source: HProxy count from the git history of ultrafunkamsterdam/undetected-chromedriver, read on November 11, 2026 · hproxy.comProxy.

2022: other hands

2022 was the year of contributors. Fixes for running several drivers at once, for AWS Lambda and for 32-bit Windows came from outside. Version 3.1.6 of October set two defaults that still hold: use_subprocess and no_sandbox are both True.

2023: the busiest year, and the last

The log holds 88 commits for 2023, the most of any year. Three things happened.

In February, version 3.4.0 changed the method. The README explains it: "instead of removing and renaming variables, we just keep them, but prevent them from being injected in the first place." It broke on some systems. Five more uploads followed within six days. One commit is titled "4.4.5" by mistake, and the next one "PATCH WEDNESDAY 3.4.5 damn versioning". The release notes begin: "What a week."

In June, version 3.5.0 followed Selenium 4.10, and the README gained its warning about IP addresses, quoted below.

In August, Chrome 115 moved its driver downloads, and an outside contributor added support in six commits.

2024: three days

Version 3.5.5 was uploaded on February 17, 2024. It is the last one. On February 20 the same author published nodriver, with a README that says: "This is the official successor of the Undetected-Chromedriver python package."

The old repository never says so. The word nodriver does not occur anywhere in its history.

2024 to 2026: nodriver

nodriver drops the driver altogether. Its README puts it in five words: "No more webdriver, no more selenium". PyPI received 25 uploads in 2024, 15 in 2025 and 10 in 2026. From November 2025 to May 2026 there was none for 183 days, and on October 26, 2026 there were four in one day.

Its log is shorter than it looks. Of its 154 commits, 90 are 45 pairs with identical content, so the log holds 109 distinct changes.

How do proxies work in both, and what went wrong?

Proxies in undetected-⁠chromedriver and nodriver
  1. Dec 2019

    One README line

    Chrome's own proxy flag

  2. Jun 2023

    The IP warning

    README: does not hide your IP

  3. Feb 2024

    Last release 3.5.5

    still no proxy option

  4. Feb 2024

    nodriver issue 4

    asks for a proxy login

  5. Mar 2025

    SOCKS5 login

    create_context, 391 days later

  6. Oct 2025

    HTTP login

    version 0.48.0, 608 days later

Source: HProxy reading of both git logs, the tracker of nodriver and the release histories on PyPI, November 11, 2026 · hproxy.comProxy.

undetected-chromedriver: a flag, and a warning

In four years undetected-chromedriver never got a proxy option of its own. No commit adds one. The README has carried one proxy line since the first day:

opts.add_argument( f'--proxy-server=socks5://127.0.0.1:9050' )

That is Chrome's own flag, and Chrome ignores a username and password written into it. A proxy with a login needs a helper. Our page on proxies for undetected-chromedriver measures three that work.

What the author did write about is the address itself. In June 2023, in a commit titled "update README to show importance of IP", he added: "THIS PACKAGE DOES NOT, and i repeat DOES NOT hide your IP address, so when running from a datacenter (even smaller ones), chances are large you will not pass! Also, if your ip reputation at home is low, you won't pass!" Two screenshots sit below it, of the same script run from home and from a datacenter.

That is the part a proxy changes. A residential exit gives the patched browser a home address in place of a datacenter one. It does not repair a poor reputation, as the second sentence of the warning says. Our Residential Lite costs $0.50 for one GB, down to $0.23 per GB at 10,000 GB+, on our residential proxies page.

nodriver: a forwarder on your own machine

nodriver takes a proxy in two places. A proxy without a login goes into browser_args as the same Chrome flag. A proxy with a login goes into create_context:

import nodriver as uc

async def main():
    browser = await uc.start()
    tab = await browser.create_context(
        "https://example.com",
        proxy_server="http://user:pass@example.hproxy.com:8080",
    )

if __name__ == '__main__':
    uc.loop().run_until_complete(main())

The host is a placeholder. With a login in the address, nodriver starts a small forwarder on 127.0.0.1 and gives Chrome that local address. The forwarder logs in at the real proxy.

It took a while. Issue 4 of the new project, opened on February 29, 2024, is titled "add use proxy with login password". The answer for SOCKS5 came 391 days later, on March 26, 2025. The answer for HTTP proxies came from an outside contributor and shipped in version 0.48.0 on October 29, 2025, 608 days after the question.

Two details of the forwarder are worth knowing. We read them in the code of the main branch and did not run it.

  • Some passwords cannot be carried. The forwarder reads the login with Python's urlparse and uses it unchanged. We checked what urlparse returns. A percent-encoded password comes back still encoded, so the proxy would receive p%40ss where p@ss was meant. A raw #, / or ? breaks the address apart. A password with one of those three characters has no spelling that arrives intact. A raw @ or : works.
  • The login is logged. The forwarder writes "which forwards to" and the full proxy address, password included, to the log at info level.

The first of these is an old acquaintance. The histories of Scrapling, Crawl4AI and Camoufox each tell of the same class of fault, and each of those projects has fixed it. The setup in full is on our page on proxies for nodriver.

The proxy faults of both tools in one table:

What went wrongReleasesFixed in
No proxy option, and a login in Chrome's flag is ignoredundetected-chromedriver, every releasenever
No proxy login at allnodriver up to 0.41SOCKS5 in March 2025, HTTP in 0.48.0
A password with #, / or ? cannot be carriednodriver since March 2025open
The forwarder logs the proxy password at info levelnodriver since March 2025open

What do they send home?

Neither has telemetry or an update check. The difference lies in what they download.

  • undetected-chromedriver fetches a driver at every start. uc.Chrome() deletes the patched chromedriver in its data folder and downloads a fresh one, unless the file is in use or you pass driver_executable_path. For Chrome 115 and newer it reads Google's Chrome for Testing lists on googlechromelabs.github.io and downloads from storage.googleapis.com, since August 16, 2023; before that it used chromedriver.storage.googleapis.com. The download runs through Python's urllib, which follows the https_proxy variable and never the --proxy-server flag you give Chrome.
  • nodriver downloads nothing. It drives the Chrome already installed on the machine over the DevTools protocol, and its code calls no outside address. Its forwarder for proxy logins checks the certificate of an HTTPS proxy with Python's default settings, unless you pass your own SSL context.

What do the commits show that the docs leave out?

  • The last release needs a module that Python removed. The file patcher.py of version 3.5.5 begins with from distutils.version import LooseVersion. Python's notes for version 3.12 say: "the distutils package has been removed from the standard library." They add that Setuptools "continues to provide distutils", which is why the install line above names it.
  • The fix exists and is unreleased. A commit of July 5, 2025 replaces that import. Its author is a bot account, google-labs-jules[bot], and the maintainer merged it the same day. The version number stayed at 3.5.5, and PyPI got no upload. The README's own install line for the main branch reaches it: pip install git+https://www.github.com/ultrafunkamsterdam/undetected-chromedriver@master.
  • Fifty-three commits in two days. On June 2 and 3, 2023 the log holds 53 commits that change one CI workflow and its test, almost all titled "Update workflow.yml" or "Update test_workflow.py".
  • Guides rarely name the successor. Of 145 posts in our competitor database that name undetected-chromedriver, 26 name nodriver and 3 name distutils. Google's second result for the tool's name was PyPI's page of version 2.1.1, uploaded in February 2021.

What this page does not cover

We ran neither tool. The statement on proxy passwords in nodriver comes from reading its code and from Python's own urlparse. We did not send such a login to a proxy. This page says nothing about which sites either tool gets through.

Neither repository has tags, so a version is matched to its code through commit subjects and upload dates. Download counts include mirrors and automated installs. We do not know when the issues and pull requests of the old repository were switched off, only that they were off on November 11, 2026.

Forks of nodriver by other people are not covered. We will read both repositories again by February 11, 2027, or on the day undetected-chromedriver gets an upload after 3.5.5.

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. undetected-chromedriver 3.5.5 of February 17, 2024 is the last release. On Python 3.12 and newer it needs setuptools installed, and it starts Chrome with the sandbox off by default. It has no proxy option beyond Chrome's --proxy-server flag, which takes no login. Its author's successor is nodriver, at 0.50.99 on November 11, 2026: asynchronous, no Selenium, and a proxy login through browser.create_context(url, proxy_server=...).
  • A free proxy list, no key and no account. /api/proxy-list?format=json returns 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 undetected-chromedriver has the measured setup, the distutils error and three ways to use a login. Proxies for nodriver covers browser_args, create_context and the forwarder. How websites detect proxies explains the part the author's warning is about, and proxies for web scraping is our own offer for this work. The histories of Playwright, Camoufox and Scrapling are told the same way.

Sources

  • The git history of ultrafunkamsterdam/undetected-chromedriver: 331 commits, no tags, from December 22, 2019 to July 5, 2025, read on November 11, 2026. ultrafunkamsterdam and contributors, GitHub.
  • The git history of ultrafunkamsterdam/nodriver: 172 commits, no tags, from February 2, 2024 to October 26, 2026, read on November 11, 2026. ultrafunkamsterdam and contributors, GitHub.
  • The commits named above, by short hash: d37fb78, 6d10c78, b7685af, 6708019, e6d3299, ebafbe1, 154f7fc, 951e659, 93adbcf, 6e471aa, f960dee, 1c704a7, 25877fd, 0aa5fbe and c50b6a2 in undetected-chromedriver; 139acfe, a0979b6, 62c575f and 0233da5 in nodriver.
  • README.md, patcher.py (at release 3.5.5 and on the main branch) and the constructor in __init__.py of undetected-chromedriver; README.md, browser.py and util.py of nodriver, with the commits aec1aa7 and bedbec9, read on November 11 and 12, 2026. Source code of both projects.
  • The release histories of both packages. Python Package Index, read on November 11, 2026.
  • Download counts of the last month. pypistats.org, read on November 11, 2026.
  • "What's New In Python 3.12", the section on distutils. Python Software Foundation, October 2023.
  • Repository and tracker data, with issue 4 of nodriver. GitHub API, read on November 11, 2026.
  • 145 posts that name undetected-chromedriver, from our competitor database, read on November 11, 2026.

Frequently asked questions

What is undetected-chromedriver?

undetected-chromedriver is a Python package that downloads Google's ChromeDriver, patches the binary and starts Chrome through Selenium so that common automation checks do not fire. A developer who goes by ultrafunkamsterdam started it on December 22, 2019. Its last release is 3.5.5 of February 17, 2024.

Is undetected-chromedriver still maintained?

Hardly. The last upload to PyPI is 3.5.5 of February 17, 2024. On November 11, 2026 the repository had issues and pull requests switched off. One commit landed in July 2025 and was never released. The same author now maintains nodriver, which he calls the official successor.

Why does undetected-chromedriver fail with No module named distutils?

Version 3.5.5 imports distutils, a module that Python removed in version 3.12. Python's release notes say that Setuptools continues to provide it, so installing setuptools makes the import work. A fix was merged into the repository on July 5, 2025 and has not been uploaded to PyPI.

What is nodriver?

nodriver is the successor of undetected-chromedriver by the same author, public since February 20, 2024. It uses neither Selenium nor a ChromeDriver binary and talks to Chrome directly over the DevTools protocol. It is asynchronous, needs Python 3.9 or newer and is at version 0.50.99 of October 26, 2026.

How do I use a proxy with undetected-chromedriver?

Pass Chrome's own flag: options.add_argument('--proxy-server=http://host:port'). The package has no proxy option of its own, and Chrome ignores a username and password written into that flag. A proxy with a login needs a helper, for example a small forwarder on your own machine.

How do I use a proxy with a username and password in nodriver?

Open a context with browser.create_context(url, proxy_server='http://USER:PASS@HOST:PORT'). nodriver then starts a small forwarder on 127.0.0.1 that Chrome uses without a login. SOCKS5 logins work since March 2025 and HTTP logins since version 0.48.0 of October 2025.

Does undetected-chromedriver hide my IP address?

No. Its README says so in capital letters: the package does not hide your IP address, and from a datacenter the chances are large that you will not pass. The tool changes how the browser looks to a page. The address your requests come from is a separate matter.

Get proxies that are alive right now

Our free proxy list re-checks every exit every few minutes across 100+ countries, with a live last-checked time, so you copy IPs that worked moments ago, not a stale text dump. When the location has to survive a real check, the paid network holds up.

129M+ proxy checks run · 100+ countries · HTTP / HTTPS / SOCKS · re-checked every few minutes · no signup

HProxy.

Honest guides and comparisons on proxies, scraping and staying unblocked, from the team that runs the network.

RSS feed