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
Add ScreenshotOne to Clay

Add ScreenshotOne to Clay

Generate website screenshots inside Clay to qualify leads, assess content, and enrich rows with visual context automatically.

Read more

1 min read

Fail ScreenshotOne API requests on purpose

Fail ScreenshotOne API requests on purpose

Use a new option to fail ScreenshotOne API requests on purpose.

Read more

1 min read

Hosted ScreenshotOne MCP server is now available

Hosted ScreenshotOne MCP server is now available

Connect your AI agents to ScreenshotOne through the hosted MCP server with OAuth. No local server or copied API key is required.

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.