Screenshot API questions.
No hidden capabilities.
Rendering, security, private artifacts, agent workflows, availability, and pricing—answered against the same development-preview contract.
What is Screenshot API?
Screenshot API is a development-stage service designed to turn a public webpage URL into a bounded screenshot job, private image artifact, and explicit render metadata.
Is the screenshot API available for production traffic?
Not yet. The public website and design-preview documentation are available, but account signup, billing, customer API access, and production browser rendering remain disabled.
Will it support full-page screenshots?
The planned contract supports viewport and full-page capture with an explicit maximum page height, execution timeout, and artifact byte limit.
Which image formats are planned?
The initial contract includes PNG, JPEG, and WebP with bounded quality settings for lossy formats.
Can I select mobile and desktop viewports?
Yes. The design preview includes named mobile and desktop presets plus bounded custom viewport dimensions.
Can the renderer access private or internal URLs?
No. Only HTTP and HTTPS are accepted, and the architecture is designed to block loopback, private, link-local, cloud-metadata, and other special-use destinations after DNS resolution and on redirects and subrequests.
Are screenshot artifacts public?
The planned delivery model stores artifacts privately and returns short-lived signed download URLs only after an account ownership check.
Can I send cookies, authorization headers, or custom JavaScript?
Those capabilities are intentionally excluded from the MVP. Persistent authenticated sessions and arbitrary customer JavaScript create additional security and privacy risks.
Why is screenshot creation asynchronous?
Page load time and queue time vary. A durable asynchronous job avoids holding client connections open and gives retries, cancellation, metering, and failure states a stable resource.
How will duplicate requests be handled?
The development-preview contract requires an idempotency key when creating a screenshot job so a network retry can replay the original result instead of creating duplicate work.
How much will Screenshot API cost?
Final pricing is not published. Plans will be proposed only after browser CPU, memory, bandwidth, storage, cleanup, and failure costs are measured.
Start with the public contract.
The documentation states what is implemented locally, what remains disabled, and which safety boundaries must pass before launch.
Read the documentation →