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
The new ScreenshotOne dashboard is out

The new ScreenshotOne dashboard is out

It is a long-term move and rebuilding the ScreenshotOne dashboard was a decision to continue improving customer experience. The previous version of the dashboard was outdated and didn't serve new arising customer needs well.

Read more

1 min read

Remove organization members

Remove organization members

Improvements to the organization management.

Read more

1 min read

Add ScreenshotOne to n8n workflows

Add ScreenshotOne to n8n workflows

You can now use ScreenshotOne in n8n workflows to render website screenshots, PDFs, scrolling screenshots and videos.

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.