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
Screenshot URLs are now available in the response

Screenshot URLs are now available in the response

You can now get a screenshot URL in the response of the API call.

Read more

1 min read

Available in Context7

Available in Context7

ScreenshotOne documentation is now available in Context7.

Read more

1 min read

Better error coverage and documentation

Better error coverage and documentation

Since a few months ago, it has been possible to check errors in the dashboard request log and get explanations and more details in the documentation. But!

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.