Images load before full-page screenshots

Full-page screenshots no longer show empty slots where lazy-loaded images should be. The API waits briefly for the images to load before it takes the screenshot.

Changelog1 min read

Written by

Dmytro Krasun

Published on

For a full-page screenshot, the API scrolls through the page so that lazy-loaded images are requested. On pages with slow images, some of them were still loading when the screenshot was taken, and they came out as empty boxes.

Now the API waits for the images that will be in the screenshot to load before it takes it:

Rendering time

The wait ends as soon as the images are loaded, so most screenshots take no longer than before. When images are slow, it lasts at most a few seconds, and never longer than a part of the time left before the request times out. Images that fail to load or are blocked, for example by block_ads, aren’t waited for.

An image that still doesn’t load in that time stays empty, as before, and the screenshot is taken anyway.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
ScreenshotOne integration with Dirstarter

ScreenshotOne integration with Dirstarter

Build a directory with Dirstarter and add website screenshots automatically with ScreenshotOne.

Read more

1 min read

Faster dashboard metrics

Faster dashboard metrics

Dashboard usage and error metrics now load faster as ScreenshotOne continues operating millions of screenshots every month.

Read more

1 min read

Improved email change flow

Improved email change flow

Account access now stays aligned with the newly verified email after an email change.

Read more

1 min read

Automate website screenshots

Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.