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
Convert any website to Markdown format with ScreenshotOne API

Convert any website to Markdown format with ScreenshotOne API

Now you can convert any website to Markdown format with ScreenshotOne API in just one simple API call.

Read more

1 min read

Rendering reliability and consistency improvements

Rendering reliability and consistency improvements

More reliable rendering servers and full-page scrolling, more consistent screenshots with reduce_motion, and more accurate fail_if_content_contains matching.

Read more

2 min read

Transfer organization ownership

Transfer organization ownership

From today, you can transfer organization ownership to another user.

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.