More reliable caching and downloads

Improved cache failure handling, screenshot URLs, and partial downloads.

Changelog1 min read

Written by

Dmytro Krasun

Published on

We made caching and downloads more reliable:

  • If caching fails, you still get the screenshot. JSON responses include screenshot_url even then; cache_url appears only when caching succeeds.
  • Async requests and response_type=empty skip the cache, and "cache": "false" in POST requests now disables caching.
  • Resuming cached downloads is more reliable: Range and If-Range requests are handled correctly, and every cached file has a consistent ETag. HTML and Markdown downloads with Unicode characters report the correct file size.

Each new cached render now gets its own URL. Use the URL from the latest API response rather than expecting an old one to update.

See the caching guide and cache options.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Fail if there is nothing to click on

Fail if there is nothing to click on

A new option has been added to fail or not to fail the screenshot rendering if there is nothing to click on.

Read more

1 min read

Agent skills are available

Agent skills are available

Use ScreenshotOne agent skills in your agent workflows.

Read more

1 min read

Better organization invitations

Better organization invitations

Organization invitations are now easier to notice and respond to in the dashboard.

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.