ScreenshotOne Changelog
New ScreenshotOne features, bug fixes, and rendering improvements.
Product updates in the last 12 months
Stricter checks for signed requests and access keys
Signed requests are only accepted as GET, a request can carry only one access key, and the lists of request patterns to block or to fail on accept up to 100 patterns each.
1 min read
HTML rendering waits for the page to load
Like URLs, HTML now waits for the load event by default, so its scripts, styles and images are ready before your scripts run and the screenshot is taken.
1 min read
Improved hiding selectors
The option to hide selectors now hides every element that matches each selector, as documented, so screenshots of the same page are more consistent.
1 min read
Fewer failed requests and clearer storage errors
Requests that reach a busy rendering server are retried on another one, HTML and markdown of pages that redirect themselves no longer fail, and storage errors say what to fix.
1 min read
PDFs without metadata
PDFs no longer include the browser details, page title, or rendering time in their document properties. They contain only the rendered page.
1 min read
Screenshots and PDFs as files for AI agents
AI agents connected to ScreenshotOne can now receive a screenshot or PDF as a file, so tools like Harvey can save it directly.
1 min read
More consistent screenshots and clearer errors
When reducing motion, sliders, carousels and looping animations stay still more often, so repeated screenshots of the same page match. Errors name the failed requests and password-protected sites.
2 min read
wait_for_selector follows your timeout
The wait_for_selector option now waits for as long as your request's timeout allows, loads the page once, and returns a clear error if the element doesn't appear.
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.