Standalone-chrome

Selenium Standalone Chrome is a self-contained Docker image that runs a single Selenium Grid node with Google Chrome and ChromeDriver, letting developers and…

  • Development
  • Tools & Utilities
Selenium Standalone Chrome is a self-contained Docker image that runs a single Selenium Grid node with Google Chrome and ChromeDriver, letting developers and QA teams run automated browser tests from one container.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

56/100 Fair

Maintained
75last commit 18 days ago
Popular
3988 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM
Security check
90no serious findings, CI
GitHub stars
88
Open issues
2
Last commit
2026-11-03
Latest release
156.0.8078.80
Activity
rising

Checked 18 days ago - source: GitHub (bigmangos/chrome-offline-installer)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 1 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Pick only the parts you need to install List the pieces you want with ADDLOCAL in the installer command, such as Studio, Robot, or ChromeExtension. If you forget a needed piece, it will not be installed and that feature won’t work. source
  • Set Orchestrator details when installing If you install the Robot, include its Orchestrator address with ORCHESTRATOR_URL or SERVICE_URL. Without this, the Robot may not know where to connect and won’t show up as a managed robot. source
  • Keep project.json with your project folder Save project.json in the same folder as your workflow files, because it stores settings like dependencies and which file starts the project. If it’s missing or mismatched, Studio may not open the project correctly. source
  • Usage Run the image and point your Selenium client at the node's HTTP port (default 4444) to drive automated Chrome sessions. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need selenium/standalone-chrome-debug to inspect rendered pages?

Use the -debug image if you need the VNC server for page rendering. The plain selenium/standalone-chrome image does not include that VNC server.

Why might my self-hosted certificate be rejected?

Chrome may no longer trust server certificates issued for more than one year. This can make long-lived self-hosted certificates fail in the browser.

Can it run without a display?

It can be run as a headless Chrome container for Selenium WebDriver testing.

What should I check when local Chrome works but the standalone grid fails?

Check the remote WebDriver setup, because local Chrome and ChromeDriver can work while webdriver.remote fails.

Answers sourced from stackoverflow.com, www.reddit.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads