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
Documentation for LLMs

Documentation for LLMs

ScreenshotOne now supports documentation format specifically targeted for LLMs—llms.txt and llms-full.txt.

Read more

1 min read

ScreenshotOne CLI is available

ScreenshotOne CLI is available

Use command line interface to automate screenshots in your workflows with ScreenshotOne.

Read more

1 min read

Add ScreenshotOne to Clay

Add ScreenshotOne to Clay

Generate website screenshots inside Clay to qualify leads, assess content, and enrich rows with visual context automatically.

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.