Every two weeks I send out a newsletter containing lots of interesting stuff for the modern PHP developer. You can expect quick tips, links to interesting tutorials, opinions and packages. Want to learn the cool stuff? Then sign up now!

Easily convert webpages to images using PHP

Browsershot is a package that can easily convert any webpage into a image. Under the hood the conversion is made possible new headless options in Chrome 59. In this post I’d like to show you how you can use Browsershot v2.

Here’s a quick example of how it can be used:



About three years ago I started working on my first package, called Browsershot. It can convert any webpage to an image. Under the hood PhantomJS was used to perform the transformation. Since it got released it did it’s job pretty well, but unfortunately PhantomJS recently has been abandoned.

A few weeks ago Chrome 59 got released. In that version some pretty cool features were introduced. One of them is the ability to take screenshots of a webpage. A recent version of Chrome probably is better in rendering a correct page then and abandoned version of PhantomJS. That’s why I decided to make a new major release of Browsershot. In this post I’d like to show you how you can use Browsershot v2.

Installing Chrome 59

In order to make use of Browsershot you must make sure that Chrome 59 or higher is installed on your system. On a Forge provisioned Ubuntu 16.04 server you can install the latest stable version of Chrome like this:

sudo wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
sudo sh -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'
sudo apt-get update
sudo apt-get -f install
sudo apt-get install google-chrome-stable

Browsershot has been tested on MacOS and Ubuntu 16.04. If you use another OS your mileage may vary.

Using Browsershot

Here’s the easiest way to create an image of a webpage:


Browsershot will make an education guess where Google Chrome is located. If on your system Chrome can not be found you can manually hint it’s location:


By default the screenshot will be a png and it’s size will match the resolution you use for your desktop. Want another size of screenshot? No problem!

    ->windowSize(640, 480)

You can also set the size of the output image independently of the size of window. Here’s how to resize a screenshot take with a resolution of 1920×1080 and scale that down to something that fits inside 200×200.

    ->windowSize(1920, 1080)
    ->fit(Manipulations::FIT_CONTAIN, 200, 200)

In fact, you can use all the methods spatie/image provides. Here’s an example where a greyscale image is created:

    ->windowSize(640, 480)

If, for some reason, you want to set the user agent Google Chrome should use when taking the screenshot you can do so:

    ->userAgent('My Special Snowflake Browser 1.0')

In closing

The screenshot capabilities of Chrome are already quite good, but there’s a lot of room for improvement still. Right now there’s no way to specify where Chrome should save the screenshot (a problem that the package solves for you behind the scenes). In the DevTools there’s an option to take a screenshot of the whole length of the page. Unfortunately this isn’t possible with the current command line options.

I’m pretty sure the headless and screenshotting options will improve in future versions of Chrome. I intend to update Browsershot as soon as new features become available in Chrome.

Want to get started using Browsershot? Then head over to GitHub. Also take a look at the other packages our team has previously made.

Freek Van der Herten is a partner and developer at Spatie, an Antwerp based company that specializes in creating web apps with Laravel. After hours he writes about modern PHP and Laravel on this blog. When not coding he’s probably rehearsing with his kraut rock band.
  • Pingback: Convert a webpage to an image – PipisCrew Official Homepage()

  • awesome!!

  • Pingback: Easily optimize images using PHP (and some binaries) - murze.be()

  • Stoyan Kyosev

    AFAIK, you cannot specify screenshot delay (tell the browser to wait before taking screenshot) when calling it through CLI. This makes using the headless-chrome with PHP unsuitable for some advanced cases, f.e. javascipt calculations to display some elements after the page has been loaded. You need the nodeJS API there. Correct me if I’m wrong.

    • It’s true that you can’t manually specify a delay. But in my testing Chrome just did the right thing automatically.

      Though I’m not certain I think it save to assume that Chrome will get a delay parameter in a future release.

  • Stefan Cuculeac

    Really nice!!