selenium/standalone-all-browsers repository overview

⁠Selenium Grid Standalone with all browsers

⁠This image provides a single Selenium Grid Standalone⁠ with Chrome, Edge and Firefox pre-installed, which enables you to run WebDriver tests remotely⁠.

Where selenium/standalone-chrome, selenium/standalone-edge and selenium/standalone-firefox each serve one browser, this image registers stereotypes for all of them at once. A session request matching browserName=chrome, MicrosoftEdge or firefox is served by the same container — one port, one container, any of the three browsers.

Available from image tag 4.35.0 onwards. It suits you if you:

• prefer a single "all-in-one" container over one Standalone per browser;
• do not mind the image size — it is considerably larger than a single-browser Standalone, because it carries three browsers and three drivers;
• run a lightweight workload and are able to size the container's resources yourself.

Browser availability differs per architecture:

Both the Chrome and the Chromium binary are present on linux/amd64, with Chrome activated by default. To switch to Chromium, set SE_BROWSER_BINARY_LOCATION_CHROME=/usr/bin/chromium.

⁠How to run this image

1. Start a Standalone with all browsers

docker run -d -p 4444:4444 -p 7900:7900 --shm-size="3g" \
    selenium/standalone-all-browsers: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 to use the host's shared memory. Because this container can run any of three browsers, --shm-size=3g is the recommended starting point.

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

• Note: Only one Standalone container can run on port 4444 at the same time.

⁠How to configure the browsers

Set SE_NODE_ENABLE_BROWSER_<BROWSER>=false to stop a browser from being registered, with <BROWSER> in uppercase — CHROME, EDGE or FIREFOX. For example, to run without Firefox:

docker run -d -p 4444:4444 -p 7900:7900 --shm-size="3g" \
    -e SE_NODE_ENABLE_BROWSER_FIREFOX=false \
    selenium/standalone-all-browsers:4.48.0-20260905

The following environment variables accept the same _<BROWSER> suffix, so each browser can be configured independently within the one container:

SE_NODE_STEREOTYPE
SE_NODE_BROWSER_NAME
SE_NODE_BROWSER_VERSION
SE_NODE_PLATFORM_NAME
SE_BROWSER_BINARY_LOCATION
SE_NODE_STEREOTYPE_EXTRA
SE_NODE_MAX_SESSIONS

The full list of environment variables is documented in ENV_VARIABLES.md⁠.

⁠How to choose the correct tag for you

This image is tagged with the Selenium Grid version only — there is no per-browser tag, since it carries several browsers at once.

selenium/standalone-all-browsers-<Major>.<Minor>.<Patch>-<YYYYMMDD>

⁠Example of a release with Selenium Grid Server 4.48.0, released on 20260909

    Selenium Server 4.48.0
    Release date 20260909


e126989f151e        selenium/standalone-all-browsers   4
e126989f151e        selenium/standalone-all-browsers   4.48
e126989f151e        selenium/standalone-all-browsers   4.48.0
e126989f151e        selenium/standalone-all-browsers   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⁠.