Cached screenshots, PDFs, and videos are now handled more reliably, with cache links returned only when the cached result is available.
We shipped a reliability improvement for cached rendering requests.
ScreenshotOne is now more careful about returning cache URLs only after the rendered result is available in the cache. This reduces rare cases where a cached screenshot, PDF, or video link could be requested before the cached file was ready.
The change is fully behind the scenes, and no API changes are required.
New features, bug fixes, and optimizations...
There is a set of use cases when you want to fail screenshot rendering and retry it if the content of the page contains a string.
1 min read
You can now use multiple API keys to the access ScreenshotOne API.
1 min read
Download filtered request logs as a zipped CSV for analysis, debugging, and reports.
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.