How to Save Automated Screenshots to S3

Why deliver to S3?

By default, screenshots are stored on ScreenshotCenter's servers and available via download URL. But for production workflows — archival, compliance, CDN serving, or data pipeline integration — you want screenshots in your storage. The S3 integration delivers every screenshot directly to your bucket as soon as it is captured.

Supported S3-compatible services

The integration works with any S3-compatible storage:

• AWS S3
• Wasabi
• Backblaze B2
• Cloudflare R2
• MinIO
• DigitalOcean Spaces

Setup

Configure the S3 integration in your ScreenshotCenter dashboard or pass it directly in the API request. You need:

• Bucket name
• Region (e.g., us-east-1)
• Access key and secret key — use an IAM user with s3:PutObject permission only
• Path template — controls the file path in the bucket

Path templates

Path templates support variables that are replaced at upload time:

Variable	Example	Description
{yyyy}	2026	4-digit year
{mm}	03	2-digit month
{dd}	05	2-digit day
{domain}	example.com	Target URL domain
{id}	abc123	Screenshot ID
{format}	png	Output format

Example path template

screenshots/{yyyy}/{mm}/{dd}/{domain}/{id}.{format}

This produces paths like screenshots/2026/03/05/example.com/abc123.png.

API example

curl "https://api.screenshotcenter.com/api/screenshot/create\
  ?url=https://example.com\
  &apps[0][app]=s3\
  &apps[0][bucket]=my-screenshots\
  &apps[0][region]=us-east-1\
  &apps[0][path]=captures/{yyyy}/{mm}/{dd}/{id}.png\
  &key=YOUR_API_KEY"

IAM policy (least privilege)

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": "s3:PutObject",
    "Resource": "arn:aws:s3:::my-screenshots/*"
  }]
}

Combining with batch and schedule

S3 delivery works with batch screenshots, website crawls, and single captures. For recurring archival, set up a cron job or Zapier schedule to capture and deliver daily.

See visual website backup for a complete archival workflow using S3.