Deploy and Host Browserless on Railway

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

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.