---
title: "Deploy Browserless"
description: "Headless Chromium over WebSocket and REST for Puppeteer and Playwright"
category: "Automation"
url: https://railway.com/deploy/browserless-1
---

# Deploy Browserless

Headless Chromium over WebSocket and REST for Puppeteer and Playwright

**[Deploy Browserless on Railway](https://railway.com/template/browserless-1)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/browserless-1/manifest.json

- **Creator:** zer0person's Projects
- **Category:** Automation
- **Total deploys:** 1

## Template content

### Browserless

- **Image:** ghcr.io/browserless/chromium:latest
- **Public domain:** Yes

## Documentation

# Deploy and Host Browserless on Railway

[Browserless](https://github.com/browserless/browserless) runs headless Chromium in a container and exposes it over WebSocket and HTTP. Your Puppeteer or Playwright scripts connect to it instead of launching a local browser, and REST endpoints cover screenshots, PDFs, content scraping and more.

## About Hosting Browserless

This template runs the official `ghcr.io/browserless/chromium` image. A random access token is generated for you as the `TOKEN` variable, and every browser session and API call needs it, so strangers cannot use your browsers. Open the service's Variables tab in Railway and copy `TOKEN`.

Connect a script with `wss://?token=` (Puppeteer `connect` or Playwright `connectOverCDP`), or call the REST APIs with `?token=`. The interactive API docs are served at `/docs`. The service keeps no data, so it needs no volume.

## Common Use Cases

- Run Puppeteer or Playwright scripts without installing Chrome on your own server
- Generate screenshots and PDFs of web pages through a simple HTTP API
- Scrape JavaScript-heavy sites for AI agents and data pipelines

## Dependencies for Browserless Hosting

- One service; no volume or database

### Deployment Dependencies

- [Browserless on GitHub](https://github.com/browserless/browserless)
- [Container image](https://github.com/browserless/browserless/pkgs/container/chromium)
- [Browserless documentation](https://docs.browserless.io/)

## Why Deploy Browserless on Railway?

Railway gives you a public HTTPS and WebSocket endpoint, automatic restarts and room to scale up, with no server to maintain. Keep the token private: anyone who has it can run browsers on your service.


## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — Automate WhatsApp workflows with Evolution API, n8n, and Postgres.
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/browserless-1