Fixed full page screenshot stitching above max height

We fixed full page screenshot stitching so the final image respects `full_page_max_height` more reliably, even when pages report incorrect scroll height.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

We fixed an issue in the full page screenshot stitching algorithm where some final screenshots could end up taller than full_page_max_height.

The root cause was that some websites report a smaller scroll height than the content that is actually captured while scrolling and stitching sections together.

Now, the full page algorithm enforces the cap based on the stitched image height itself and applies extra cropping safeguards when needed.

This makes full_page_max_height behave more reliably for problematic pages and reduces cases where oversized full page screenshots slip through.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Get favicon used by a website with ScreenshotOne API

Get favicon used by a website with ScreenshotOne API

Now you can get favicon used by a website with ScreenshotOne API in just one simple API call.

Read more

1 min read

Set locale and language of the browser

Set locale and language of the browser

A new version of the ScreenshotOne API has been just deployed. It allows you to set both locale and language of the browser when rendering screenshots with one simple option.

Read more

1 min read

Choose the format of the page content returned by the ScreenshotOne API

Choose the format of the page content returned by the ScreenshotOne API

Now you can choose the format of the page content returned by ScreenshotOne API with the metadata_content_format option.

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.