HEAD requests

Render screenshots with HEAD requests without downloading them. They count towards your quota like GET.

Changelog1 min read

Written by

Dmytro Krasun

Published on

The API now supports HEAD requests. They take the same options as GET and return the same status and headers, without the file. Previously, HEAD requests failed with a validation error.

HEAD requests that render count towards your quota, just like GET, even though you don’t receive the file. Without cache=true, every HEAD request renders again and counts. If link checkers, crawlers or uptime monitors send HEAD requests to your API URLs, turn on caching or point them elsewhere.

With cache=true, a HEAD request renders ahead of time: a later GET with the same options is served from the cache and doesn’t count towards your quota.

See HEAD requests.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Added an Above-the-Fold Checker Tool

Added an Above-the-Fold Checker Tool

A new ScreenshotOne tool to capture what users see before the first scroll.

Read more

1 min read

Fail rendering if the content is missing a string

Fail rendering if the content is missing a string

There is a set of use cases when you want to fail screenshot rendering and retry it if the content of the page is missing a string.

Read more

1 min read

Notifications when the usage reaches 50% of the limit

Notifications when the usage reaches 50% of the limit

You can now get notifications when the usage reaches 50% of the limit.

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.