Improved full-page screenshot rendering

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

Blog post 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
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

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

Extract Open Graph metadata while rendering screenshots

Extract Open Graph metadata while rendering screenshots

From today, you can get parsed Open Graph metadata and screenshots in one API request.

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.