Docs

Documentation

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

Last updated: 2025
Support

FAQ & Troubleshooting

Common questions, quick fixes, and pointers to the right documentation pages.

SchedulingStorage deliveryAuth & cookiesCommon issues

Fast path: schedule not running

Check timezone, Trigger Windows, and whether the schedule is active. Then verify storage health.

Fast path: page looks wrong

Confirm device/resolution, geolocation, and overlay blocking. Try SelectorHide for noisy UI.

Billing

Is there a free plan?

No. After creating an account, you’ll choose a paid plan to activate scheduling and storage delivery. This keeps the product sustainable and ensures your captures are delivered to your cloud.
Storage

Where are my screenshots and videos saved?

Captures are delivered to your connected destination (Google Drive, Dropbox, or S3-compatible storage). We may keep internal copies only up to your configured retention window (if enabled) to support processing and re-delivery scenarios.
Auth

Can I capture login-protected pages?

Yes. Use your Web Profile to configure session data such as headers and cookies. For complex logins (SSO, MFA), we recommend using a stable session cookie approach when possible.
Troubleshooting

My schedule isn’t running — what should I check first?

  • Is the schedule active and not past its End Date?
  • Is the timezone correct on the schedule?
  • If you use Trigger Windows, are you currently inside the allowed day/time window?
  • Is your cloud integration healthy (permissions/token still valid)?
Storage

I don’t see files in my cloud folder — where did they go?

First, confirm the schedule ran successfully. Then verify the selected destination and folder/bucket in Cloud Storages. If the integration is unhealthy (expired token / wrong permissions), delivery can fail even if capture succeeds.
Concepts

What’s the difference between a Web Profile and a Shot Schedule?

A Web Profile defines how the browser behaves (device, resolution, blocking, geolocation, storage preferences). A Shot Schedule defines what URL to capture and when to run it. Schedules reference profiles so you can reuse the same settings across many URLs.
Captures

What’s the difference between full-page and viewport captures?

Viewport captures only what fits in the browser window. Full-page captures the entire scrollable page. Full-page is best for archiving and audits; viewport is best for above-the-fold monitoring and smaller files.
Captures

Can I capture only a specific part of the page?

Yes. Use Element Screenshots with your selector fields (XPath, Click, Hide, Hover) to isolate a component and keep output focused.
Captures

Cookie banners or popups cover the page — what can I do?

Enable blocking options in your Web Profile, or hide specific elements using SelectorHide on the schedule. For highly dynamic overlays, increase timeouts/scroll delays.
Location

The page looks different than what I see locally — why?

Websites often change content by location, timezone, and device. Check your Web Profile device settings and geolocation configuration. Also verify you’re using the intended timezone.
Scheduling

Do you support hourly or frequent captures?

Yes. Use your schedule frequency options for hourly captures (or smaller intervals where supported by your plan and configuration). If you also use Trigger Windows, captures will only run during allowed hours.
Reliability

What happens if a capture fails?

Failed captures can happen due to timeouts, site blocking, or dynamic rendering. Use higher timeouts, stability/retry settings, and clean-capture rules (where available). If a destination delivery fails, check storage health/permissions first.
Reliability

Can websites block automated captures?

Some websites use bot protection, rate limits, or aggressive scripts. If you see inconsistent results, increase wait/timeout values, avoid extremely frequent schedules, and ensure the page can render normally without interactive challenges.
Infrastructure

Where do captures run from?

Captures run from our supported data center locations. See Data Center Locations for the list.
Support

Still stuck — how do I get help?

Contact support and include: the schedule name, target URL, approximate run time, and which storage provider you’re delivering to. That helps us debug faster.

Still have questions?

If something isn’t working, contact support with the schedule name, URL, and the approximate run time.