Browserless-v2

Browserless is a self-hosted web service that runs a headless Chromium browser in a container, letting remote clients connect over a WebSocket connection to…

  • Tools & Utilities
Browserless is a self-hosted web service that runs a headless Chromium browser in a container, letting remote clients connect over a WebSocket connection to drive and script it. It provides first-class integrations for Puppeteer, Playwright, and Selenium's WebDriver, along with handy REST (representational state transfer) APIs for common tasks such as taking screenshots and rendering PDFs. It's a good fit for developers and homelabbers who need a reliable, scriptable headless-browser backend for automation, scraping, and testing without running a browser locally.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • 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.

75/100 Good

Maintained
100last commit 17 days ago
Popular
8313,900 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
13,900
Open issues
12
Last commit
2026-11-04
Latest release
v2.59.0
Activity
rising

Checked 17 days ago - source: GitHub (browserless/browserless)

Resources & Compatibility

Minimum requirements: 2 GB RAM.

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

First-install notes

  • Set a TOKEN secret before starting Set TOKEN (the shared password your app uses to make requests) to a secret value before running the start command. Without a proper token, your app may not be able to prove it is allowed to use Browserless, and the service is easier to misuse. source
  • Choose CONCURRENT, QUEUED, and TIMEOUT Use the documented settings like CONCURRENT, QUEUED, and TIMEOUT to control how many browser jobs run at once, how many can wait, and how long a job may run. Keeping these sensible helps prevent your Browserless instance from freezing under load or stopping tasks too early. source
  • Make sure browser files are installed Browserless checks for the browser program files it needs when it starts. If any required file is missing, the start command fails with an error instead of the web service coming online. source
  • Pair with changedetection.io (Playwright fetcher) If you're using Browserless to power changedetection.io's Playwright content fetcher, add the following environment variable to your changedetection.io container after installing (replace <host>, <port>, and <token> with your values): PLAYWRIGHT_DRIVER_URL=ws://<host>:<port>/chromium?token=<token>&launch={"defaultViewport":{"height":1080,"width":1920},"headless":false,"stealth":true}&blockAds=true source

Fetched 47 days ago - each note links to its source

Alternatives (3)

  • Geo-Peek - This website provides screenshots from 25 gepgraphical locations 12 worldover, 12 USA and 5 in europe.
  • Rebrowser - The ultimate cloud browser.
  • easi.run - easi.run is an open-source, self-hosted Chrome workspace for AI agents.

Checked 40 days ago - source: AlternativeTo

Common questions

Which environment variables should I set before starting Browserless?

Set TOKEN to a secret value so clients can authenticate to the service. Use CONCURRENT, QUEUED, and TIMEOUT to control how many sessions run at once, how many jobs can wait, and how long a job may run.

Why does Browserless fail to start in Docker?

It checks for the browser program files it needs when it starts. If a required file is missing, the start command fails with an error instead of bringing up the service.

Which image should I use for Firefox or WebKit support?

Use the Firefox image or the multi image if you need Firefox or WebKit sessions. The default image is for Chromium-based work.

How do I connect changedetection.io to Browserless as a Playwright driver?

Set PLAYWRIGHT_DRIVER_URL in the changedetection.io container to the Browserless chromium WebSocket endpoint, including the token, launch options, and blockAds setting. Use your Browserless host, port, and token.

What port should I expose for a local Docker deployment?

Expose container port 3000 to the host. The WebSocket service is available on that port.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads