Improved full-page scrolling for lazy-loaded content

Better scrolling routine to load content reliably on long pages.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

We improved the scrolling routine used for full-page screenshots to make lazy-loaded content appear more reliably before capturing:

  • Tuned scrolling cadence and guards to account for deferred rendering and wrappers.
  • Reduced timeouts for pages that previously stalled during full-page renders.

As a result, more pages with infinite scroll or heavy lazy-loading now render fully without missing sections.

If you still see missing parts on a specific URL, send it to support@screenshotone.com.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
ScreenshotOne skill for OpenClaw is available

ScreenshotOne skill for OpenClaw is available

Use the ScreenshotOne Render Website Screenshot skill in OpenClaw via ClawHub.

Read more

1 min read

Improving performance and stability by consolidating validation and access check logic in the API gateway

Improving performance and stability by consolidating validation and access check logic in the API gateway

For the past few days, I have been working on improving the stability and performance of the ScreenshotOne API. I started from low-hanging fruits—moving validations and access key management from rendering services to ScreenshotOne's API gateway. The API will be more stable and performant as a result. If you are curious why, please continue reading.

Read more

2 min read

Screenshot URL in webhooks

Screenshot URL in webhooks

Now, you can get the screenshot URL in the webhook response.

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.