Docs

Documentation

Learn how to configure capture schedules, timezones, trigger windows, and cloud storage — from first setup to production workflows.

Last updated: 2025
Automation & Stability

History & Retention

Capture History shows what ran, when it ran, and where the output was delivered. Retention defines how long metadata and files remain accessible.

Execution historyDelivery statusCloud-first storageAuditable timelines

Website Screenshot World is designed around a cloud-first model. Your screenshots and videos are delivered to your connected storage, while we keep lightweight execution history for visibility and troubleshooting.

Capture history

Each Shot Schedule maintains a chronological history of its executions.

  • • Execution timestamp
  • • Status (success, retry, failed)
  • • Linked Web Profile and Trigger Window
  • • Destination storage reference

This history allows you to confirm that jobs ran as expected without storing full files indefinitely.

File storage model

Captured screenshots and videos are delivered directly to your configured cloud storage.

  • • Google Drive folders
  • • Dropbox directories
  • • AWS S3 or S3-compatible buckets

We do not act as the long-term file host. Your cloud storage is the system of record.

Retention policy

Retention applies to execution metadata, not your files.

  • • Execution logs are retained for operational visibility
  • • Metadata supports audits and troubleshooting
  • • Actual files remain in your cloud storage until you delete them

Why this matters

  • • You control storage costs and lifecycle policies
  • • Easier compliance and legal audits
  • • No vendor lock-in for historical files
  • • Clear separation between execution and storage