selenium/standalone-chrome-for-testing repository overview

⁠Selenium Grid Standalone with Chrome for Testing

⁠This image provides a Selenium Grid Standalone⁠ with Chrome for Testing⁠, which enables you to run WebDriver tests remotely⁠.

Chrome for Testing (CfT) is a Chrome flavour published by the Chrome team specifically for automation. Every CfT build is released together with the exact ChromeDriver built from the same revision, so the browser and the driver in this image are always a known-good pair. Unlike the regular selenium/standalone-chrome image, CfT does not auto-update and does not carry the components a consumer browser ships with, which makes it the better choice when you need a build that stays exactly where you pinned it.

• Chrome for Testing is published for linux64 only, so selenium/standalone-chrome-for-testing is available for linux/amd64 only. On ARM64, use selenium/standalone-chrome⁠ or selenium/standalone-chromium⁠ instead.
• The Grid registers the capability browserName=chrome, so existing tests need no change.

⁠How to run this image

1. Start a Standalone Chrome for Testing

docker run -d -p 4444:4444 -p 7900:7900 --platform linux/amd64 --shm-size="2g" \
    selenium/standalone-chrome-for-testing:4.48.0-20260905

1. Point your WebDriver tests to http://localhost:4444⁠

2. That's it!

3. (Optional) To see what is happening inside the container, head to http://localhost:7900/?autoconnect=1&resize=scale&password=secret⁠. Port 7900 serves the built-in noVNC session; the default password is secret.

• When executing docker run for an image that contains a browser please use the flag --shm-size=2g to use the host's shared memory. Chrome will crash on the default 64 MB /dev/shm otherwise.

• The example above pins a full tag. Pinning a specific browser and Grid version is the recommended way to run these images. Please see Tagging Conventions⁠ for details.

• Beta, Dev and Canary channels of Chrome for Testing are also published, as selenium/standalone-chrome-for-testing:beta, :dev and :canary.

⁠How to choose the correct tag for you

The tag structure is as follows:

selenium/standalone-chrome-for-testing-<Major>.<Minor>.<Patch>-<YYYYMMDD>

Also with browser version and browser driver version

selenium/standalone-chrome-for-testing-<browserVersion>-<browserDriver>-<browserDriverVersion>-<Major>.<Minor>.<Patch>-<YYYYMMDD>

Plus all the permutations from the above one

⁠Example of a release with Chrome for Testing 152, ChromeDriver 152.0 and Selenium Grid Server 4.48.0, released on 20260909

    Chrome for Testing 152.0
    ChromeDriver 152.0
    Selenium Server 4.48.0
    Release date 20260909


e126989f151e        selenium/standalone-chrome-for-testing   4
e126989f151e        selenium/standalone-chrome-for-testing   4.48
e126989f151e        selenium/standalone-chrome-for-testing   4.48.0
e126989f151e        selenium/standalone-chrome-for-testing   4.48.0-20260909
e126989f151e        selenium/standalone-chrome-for-testing   152.0
e126989f151e        selenium/standalone-chrome-for-testing   152.0-20260909
e126989f151e        selenium/standalone-chrome-for-testing   152.0-chromedriver-152.0
e126989f151e        selenium/standalone-chrome-for-testing   152.0-chromedriver-152.0-20260909
e126989f151e        selenium/standalone-chrome-for-testing   152.0-chromedriver-152.0-grid-4.48.0-20260909

With that, you can use any of the different tags to get the most recent release in a simplified way.

⁠Full documentation

The Docker-Selenium project in GitHub has an extensive README⁠ that will help you find the correct way to get this images up and running for your use case.

⁠License

The project is made possible by volunteer contributors who have put in thousands of hours of their own time, and made the source code freely available under the Apache License 2.0⁠.