How Samsara did stress test automation of their app with Browserless

Wanna see how our customers used Puppeteer & Browserless to implement one-time passwords in the banking industry! Check it out!

Wanna see how our customers used Puppeteer & Browserless to automate PDF & PNG exporting from slide decks. Check it out!

We'll share session management tactics, so you know how to manage sessions for web automation with Puppeteer + Browserless!

IrishEnegryBot did a great job around Puppeteer Web Scraping!

Send your clients a weekly or monthly report through email - they'll be grateful!

[April Fools Prank] Introducing Headless Internet Explorer

This post gives an introduction to web automation with Browserless. Learn the most common use cases, libraries that work with browserless, and features the service provides.

Without a doubt, one of the most helpful tools when working with any browser automation library is a visual debugger. We've written quite a bit about it.

We're proud to announce that we have a new data center setup in Amsterdam! With the recent exit of the United Kingdom from the European Union, we've heard from a lot our users about having a location that's still located in the EU for legal purposes.

One of the things we've heard often is that our Worker settings is confusing, and today we rectify that by removing a slew of unnecessary information, and adding three simple buttons: Force Restart, Relaunch, and Settings.

This is the first of seven chapters in an ongoing blog series on headless browsers and best practices.

We're happy to announce that, as of version 1.42.0 of our docker image, we've added support for launching chromium in "stealth" mode. Using stealth mode is as simple as adding a stealth argument to your launch args.

If you've been printing PDF's in puppeteer for some time, you've no doubt encountered issues where fonts don't render properly. Blotchy, pixelated, or even plain incorrect renderings are common when using headless-browsers. Luckily, there's a few quick things you can do to fix the problem!

It's what every Node developer fears: the process that keeps eating memory and won't stop, that's right we're talking about memory leaks today folks, and more specifically the NodeJS kind. This post shares is how we found, diagnosed, and fixed a particular memory leak that caused us some headaches in browserless.

Having recently rewritten our implementation of screencasting for Puppeteer, we decided that the implementation was interesting enough to go over in a blog post. We'll of course go over how we landed on the decision, and talk more about tradeoffs made for our particular API.

Effective January 1st, 2020 we'll be updating our prices. Learn more about the new rates and how they will impact you.

Today, I wanted to take a look at the darker side of running a business, mostly the small things that will absolutely kill it. My intent here is to shed light on symptoms so you can course-correct before they become and out of control problem.

Today, I'd like to go over how browserless can help you mitigate some of these slower operations, and in certain cases even cut your loading time in half.

Puppeteer can be frustrating and time-consuming it can be to debug, that's we're happy to announce our new Live Debugger.

We're happy to announce that usage-based accounts on browserless are now live! Similar to our dedicated accounts, usage-based accounts come with all the API's that you now expect from the browserless service with the convenience of only paying for what you use.

At the time of this writing, we currently run nearly 5 million headless sessions a week. Given all of this growth and time passed, it's time once again for us to divulge what we've learned running a headless browser company at scale.

It's my hope that, at the end of this post, you'll have much better tools and methods for debugging some of the tougher problems in headless Chrome. And if not you'll at least know where to get started!

Browserless has just recently had its first birthday! Though there is so much to write about, today I want to go over the core of what browserless does and pass on all of our biggest findings, whether you're just beginning your headless Chrome journey or have been doing so for a while.

We're happy to announce that you can now launch browserless instances across the globe! With this comes two new load-balancers that can better handle routing your traffic as well. No matter where you are you'll be closer to your browserless workers.

One of the most hotly talked about topics in tech right now is starting an indie business. As the sole-developer, founder, and doer of all things at browserless; I wanted to take chance and paint a better picture of what's like to be independent in the technology world.

We're excited to announce that we've recently just crossed over 2 million sessions served! We'd like to take some time and outline common best practices when running headless browsers (and puppeteer) in a production environment.

We're extremely excited to announce that we'll soon be entering a closed-beta for browserless functions and a new payment option: usage-based payment!

You've written your Puppeteer code, you've made sure it works, and now it's time to get your project running someplace. This might be on a hosting provider like Amazon Web Services or on your own hardware. In any case chances are that you're running some flavor of Linux, and if you're reading this then you've undoubtedly run into some issues getting Chrome to run properly.

Puppeteer has the ability to take screenshots of a website, but it comes with some size limitations. The solution is pretty easy and we share it here.