Skip to main content
store:true changes a synchronous screenshot from binary bytes to JSON containing media. Async, regions, and Visual Style Guide screenshot requests store automatically. Scrinly uses its Backblaze B2 provider by default. Generated screenshot, crop, and diff URLs point directly to the configured provider. The main stored object also appears in X-Scrinly-Storage-URL; Scrinly does not proxy image delivery. storage_path is a prefix. Generated screenshots and region crops are content-addressed from their encoded bytes, so the same prefix can safely hold repeated captures of one page.

​
Customer storage

POST requests may provide request-scoped settings for b2, s3, or r2:
  • storage_provider
  • storage_bucket or provider-specific bucket identifiers
  • storage_endpoint and storage_region
  • storage_access_key_id and storage_secret_access_key
  • B2 application-key fields where applicable
  • storage_public_domain
  • storage_return_location
Treat these fields as credentials. Send them only from a trusted server through HTTPS JSON. They must never enter frontend code, query strings, generated examples, logs, or webhooks. Visual diffs and monitors require publicly fetchable direct source URLs. Configure public-read delivery or storage_public_domain for customer storage used by those features. Customer-owned objects follow the customer’s retention policy. storage_return_location:true adds provider-specific location metadata for backends that need it. It is independent of the direct media.url contract.