# Chrome

Chrome is a self-hosted development app. Headless Google Chrome packaged in a lightweight Alpine Linux container, for self-hosted browser automation, scraping, and screenshot capture. It is open source and self-hosted, installable on ZimaOS, Kubernetes (Helm), Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/447/chrome

## Description

Headless Google Chrome packaged in a lightweight Alpine Linux container, for self-hosted browser automation, scraping, and screenshot capture.

## Platform availability

Available on 3 of 9 platforms: Unraid, ZimaOS, Helm.

## Health score

46/100 (Fair), based on 4 of 4 factors.
- Maintained: 39 (last commit 341 days ago)
- Popular: 67 (2,141 GitHub stars)
- Easy to install: 55 (3 install platforms, install notes, Docker image)
- Light to run: 20 (8 GB minimum RAM, runs on ARM)

## Links

- Official website: https://www.chromestatus.com
- ZimaOS: https://github.com/WisdomSky/CasaOS-LinuxServer-AppStore/tree/master/Apps/Chrome
- Kubernetes (Helm): https://artifacthub.io/packages/helm/self-hosters-by-night/chrome
- Docker Hub: https://hub.docker.com/r/zenika/alpine-chrome
- Unraid: https://ca.unraid.net/apps/chrome-01oyj93117dwgb?q=chrome
- GitHub: https://github.com/jlandure/alpine-chrome

## Common questions

### Where can I pull alpine-chrome if Docker Hub pulls are rate-limited?

The README lists GitHub Container Registry and Google Cloud registries as other registries, but notes they may be deleted or obsolete.

### Which alpine-chrome tags should I use when I need Node.js, Puppeteer, Playwright, or Selenium?

There are dedicated tags such as with-node, with-puppeteer, with-playwright, and with-selenoid, along with version-prefixed variants like 100-with-node.

### Why might a self-hosted Chrome setup reject a valid-looking server certificate?

Chrome, and possibly Firefox, may stop trusting certificates that have been issued for more than one year. Checking the server certificate duration can explain the failure.

### What should I test when Chrome misbehaves behind Nginx Proxy Manager?

Try a new Chrome profile or at least an incognito window. If that fixes it, the issue is likely a Chrome cache problem.

---
Source: Our Local Host (https://ourlocalhost.com/app/447/chrome), the self-hosted and open-source app directory.