Improved full-page screenshot rendering

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

Changelog1 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
Fail rendering if the content is missing a string

Fail rendering if the content is missing a string

There is a set of use cases when you want to fail screenshot rendering and retry it if the content of the page is missing a string.

Read more

1 min read

A Simple Website Screenshot Tool by ScreenshotOne

A Simple Website Screenshot Tool by ScreenshotOne

A few words about why to launch yet another website screenshotting tool.

Read more

1 min read

Rendering Google Documents and Slides is now available

Rendering Google Documents and Slides is now available

You can now easily render Google Documents and Slides with ScreenshotOne.

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.