The Headless Browser Service.

Tired of trying to run Chrome on linux or inside docker? Then just use browserless.


Try it Out
const puppeteer = require('puppeteer');

  browserWSEndpoint: 'wss://'
}).then(async browser => {
  const page = await browser.newPage();
  await page.goto('');
  await page.screenshot({path: 'screenshot.png'});

A headless browser in the cloud

Browserless solves the problem of running Chrome on a web server. If you're tired fighting to get Chrome running on AWS, Heroku, or Digital Ocean then browserless is for you.

In just minutes you'll have access to Chrome anywhere, and time to focus on your core business. Stop wasting days or weeks and just use browserless.

"Browserless is a great browser-as-a-service tool that just works. We use it as a micro-service that renders thousands of dashboards per day as image of PDF and are very happy with the stability and performance."

Ian Formanek, CEO Cluvio

Flexible pricing

Launch up to 20 instances of any size. Add or remove at any point.

Accounts get their own dedicated browser instance, on-going updates, and email support.


Up to 10 concurrent sessions per worker

Small sites and apps with static content



Up to 15 concurrent sessions per worker

Sites with interactivity, video or 2D canvas



Up to 20 concurrent sessions per worker

Big sites with 3D graphics, video and more


Commercial License

Commercial usage via the docker image

Scale as many as you want. Run anywhere including on-site



  • High availability

    Each account gets at least one dedicated browser instance so you're guaranteed availability. If you need to scale up it's as easy as pressing a button to upgrade.

  • Parallelization

    With near-zero startup times, and plans that go up to 100 concurrent connections, it's hard to beat the speed of browserless.

  • Blazing fast speed

    Unlike lambda's or other services that require the browser to warm up (taking seconds), browserless is "always on" making sure everything is fast. It even automatically restarts Chrome when resources are constrained.

  • No Setup

    Once you sign up you're ready to go. There's no deployments to do, updates to run, or software to install. Simply alter a few lines of code in your app and you're ready.

  • Easy Updates

    With browser technology moving at lightening speed it's hard to stay current. Browserless lets you upgrade when your ready, and offers direct compatibility with popular libraries.

  • Scale on your time

    The Corporate plan allows you access to all the images of browserless via docker. Once you've signed up you can begin pulling and running anywhere you wish.

The only live debugger

Save hours by interactively building your puppeteer scripts with the browserless debugger. With this tool you can see how the site is rendering, monitor network requests, and even insert debug statements during your scripts execution. It even includes the puppeteer docs directly inside the editor.


Get valuable insights into your headless sessions. Crucial information like timeouts and resource usage is displayed intuitively.

Frequently Asked Questions

  • Can't I just use docker?

    Yes and no. Chrome takes quite a few additional packages in order to run correctly, and then you'll have to install missing fonts on top of that. Most base images aren't suitable for running Chrome either, so you'll have to experiment with that as well. We've spent months refining the software that powers browserless so you don't have to lose time as well.

  • Aren't you just running Chrome?

    On top of getting Chrome up and running, browserless also takes care of the management issue as well. In order to offer a service around a web browser you'll have to do some form of rate-limiting and load-balancing. Both of which are difficult with Chrome as it uses both HTTP and Websockets for incoming connections.

  • Can't I just execute Chrome from my program?

    At first, sure. But what happens when you're program starts handling more and more requests? Chrome can start swallowing resources pretty quickly and cause your application to be unresponsive. That's why it's important to have Chrome contained and made serviceable so it doesn't bring down your entire infrastructure.

  • How secure is my account?

    We don't store any sensitive information in browserless whatsoever. We use Stripe's payment API, so we never store credit card or other personal information, and we securely store your password with a one-way hashing algorithm. Your email is only used to contact you about updates to the service, and we don't sell or expose it to third-parties.

  • Can I cancel if I'm not happy?

    Yes. There's no contracts to sign, and you can cancel your account at any time without question. Once the billing period is over you won't be charged further.

  • Can I run this on my own infrastructure?

    Yes, we have a corporate plan available for directly pulling the browserless images. If you want more information, please contact us.

  • What libraries do you support?

    Pretty much any out there that allow you to specify URL for where Chrome is running. Puppeteer, chromeless, and more allow you to hook into an existing Chrome session and drive it remotely, which is fundamentally how browserless works. Be sure to check out our docs for more information.

  • What happens if a new version of Chrome comes out?

    We have tooling and automation to automatically download, test, and deploy new Chrome packages almost instantly. If you subscribe to a hosted plan then you simply login to your account and deploy whenever you wish. Corporate plans can pull and run however they chose as well.

Sign up now.

You'll be up in and running in less than 5 minutes