Improved guards for full-page screenshots by sections

Improved guards for full-page screenshots by sections.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

When you use the full_page_algorithm=by_sections option, the API scrolls the page and captures each section.

In some cases, the API did not stop scrolling and could get stuck in an infinite loop.

We added additional guards to the scrolling algorithm to prevent this.

If you have any questions or suggestions, please let us know at support@screenshotone.com.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Improved the behavior and stability of the "scroll_into_view" option

Improved the behavior and stability of the "scroll_into_view" option

Before the change, there was a subset of cases when the rendering requests were failing when using the scroll_into_view option. Now, it is improved and will make rendering more stable.

Read more

1 min read

Choose the format of the page content returned by the ScreenshotOne API

Choose the format of the page content returned by the ScreenshotOne API

Now you can choose the format of the page content returned by ScreenshotOne API with the metadata_content_format option.

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.