Improved full-page screenshot rendering

Fixed a few issues related to full-page screenshots rendering.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

Scrolling websites with wrapped content containers

A few cases were reported where API timed out when rendering websites with wrapped content containers. That usually means that the page has viewport adjust max height and the content inside is scrolled.

We improved the API to detect and handle a subset of such cases. Now, you will see better success rate for full-page screenshots in such cases.

Content visibility

For specific subset of elements caused by a well-known plugin for a well-known CMS, we update and force CSS styles to make the content visible always, not only when lazy loaded.

Your feedback is always appreciated

We are constantly working on improving the quality of full-page screenshots rendering. But if you notice more issues with full-page screenshots rendering, please let us know at hey@screenshotone.com.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Available in Context7

Available in Context7

ScreenshotOne documentation is now available in Context7.

Read more

1 min read

Better and more extensible PDF rendering

Better and more extensible PDF rendering

ScreenshotOne supports PDF rendering for a long time but it was used till recently by a small group of customers. Growing demand in PDF rendering required updating the API. And today, we introduce new options for PDF customization.

Read more

1 min read

Improved blocking of cookie banners

Improved blocking of cookie banners

We just released an updated version of our algorithm to block cookie banners by heuristics.

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.