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.
To be precise, for example, you were specifying a selector of some elements that is not loaded till you see it in the viewport. That behavior triggered timeout errors in the old implementation.
Now, the algorithm is improved to scroll and to try to trigger a lazy load of the specified element.
That way it is more stable and the request has a higher chance for success.
Enjoy! And if you have any questions, please don’t hesitate to reach out at support@screenshotone.com.
New features, bug fixes, and optimizations...
From today, you can use our screenshot API together with the OpenAI Vision API. It allows you to send screenshots directly to the Vision API without building all the infrastructure yourself.
2 min read
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.
2 min read
ScreenshotOne now renders HTTP-only websites more reliably by avoiding browser HTTPS-upgrade redirect loops.
1 min read
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.