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
New hover option

New hover option

Use the new hover option to interact with elements before rendering, and choose whether to fail if the hover selector is not found.

Read more

1 min read

Manage your password from dashboard settings

Manage your password from dashboard settings

You can now set, change, or reset your password directly from the dashboard settings.

Read more

1 min read

Improved favicon detection for metadata_icon

Improved favicon detection for metadata_icon

Improved `metadata_icon` to check common favicon link variants more reliably.

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.