How to Use PageCrawl.io to Archive Website Screenshots Automatically
Set up PageCrawl to save screenshots to Dropbox when monitored pages change, and learn when to record every check or use a replayable WACZ archive.
To automatically save PageCrawl.io screenshots, add a URL as a monitor, enable screenshots for that monitor, and connect Dropbox under Settings > Integrations > Dropbox. After you authorize PageCrawl and choose a Dropbox folder, PageCrawl uploads a screenshot there when it detects a change on the monitored page. The documented path pattern is {your-folder}/{page-name}/{datetime}.jpg. This is change-triggered saving; it does not mean a screenshot is uploaded after every check. PageCrawl documents the Dropbox integration as available on all plans. [PageCrawl: Save Screenshots to Dropbox]
Set up automatic screenshot archiving
- Create a monitor. Add the page URL in PageCrawl and choose a check frequency. Configure the screenshot options available in your account and plan. Interface labels and options may change, so use the current monitor editor as the source of truth.
- Connect Dropbox. Open Settings > Integrations, choose Dropbox setup, authenticate with Dropbox, authorize PageCrawl, and select the destination folder.
- Enable screenshots on the monitor. The Dropbox connection alone is not enough: screenshots must be enabled for the individual monitored page.
- Verify the workflow. After PageCrawl detects a change, check the monitor’s change history and the selected Dropbox folder for the new image. Files follow the documented pattern
{your-folder}/{page-name}/{datetime}.jpg.
Use a destination folder that makes it easy to identify the monitor and its captures. If several pages are monitored, verify that the page-name subfolders and timestamps make the files easy to retrieve.
Choose the capture trigger
There are two distinct workflows. The Dropbox guide describes uploads when a monitored page changes. PageCrawl also documents a Record every check setting that stores captures even when a check finds no change. Do not assume the Dropbox change-triggered workflow uploads on every poll; configure and verify the every-check option separately if you need a record of unchanged checks. [PageCrawl: Record every check]
| Need | Workflow | What to check |
|---|---|---|
| Keep images when a page changes | Enable monitor screenshots and connect Dropbox. | Confirm a detected change creates a file in the selected folder. |
| Keep a screenshot at every poll, including unchanged pages | Enable Record every check. | The documentation requires the Screenshots feature and Full Page Screenshots to be enabled for every-check screenshots. |
| Preserve more than a flat image | Consider a WACZ web archive. | Check plan and frequency requirements; PageCrawl documents change-triggered WACZ archiving on Ultimate for monitors checked every six hours or less often. |
Every-check recording can produce substantially more stored files than change-only capture, because unchanged checks are included. Choose the trigger based on the record you actually need and review PageCrawl’s current storage and plan details before enabling it broadly.
Screenshot or full web archive?
A screenshot is a flat image of the page’s visual state. It is useful for visual reference and comparisons, but it does not preserve the page as an interactive website. A WACZ archive preserves a fuller page state and can be replayed, including interactions such as scrolling and clicking, according to PageCrawl’s documentation. PageCrawl names ReplayWeb.page and Webrecorder as compatible viewers. [PageCrawl: Web Archiving]
Use screenshots when an image is sufficient. Consider an archive when you need page content and assets that can be replayed. PageCrawl documents change-triggered WACZ archiving as an Ultimate feature and specifies a monitor frequency of six hours or less often. To configure archives, enable Web Archiving, then configure it for the monitor, a template, or the workspace. Its separate every-check option can store screenshots, web archives, or both when there is no detected change; every-check archives require Web Archiving and the documented frequency condition. Confirm current eligibility and settings in PageCrawl before relying on this workflow.
A screenshot or replayable archive is not, by itself, a guarantee that a record satisfies a legal or regulatory requirement. If you need records for that purpose, define the required retention, integrity, and review process separately.
Access, reliability, and storage considerations
- Dropbox authorization: If authorization expires, PageCrawl says the integration is disabled and a notification is generated. Reconnect under Settings > Integrations, then check that the destination folder is still selected.
- Change detection: A screenshot upload depends on PageCrawl detecting a change and having screenshots enabled on that monitor. If a page looks different but no capture appears, inspect the monitor’s change history and screenshot settings.
- Check frequency: A change-triggered workflow cannot capture a change before the next monitor check. For WACZ, follow PageCrawl’s stated frequency requirement.
- Storage volume: Change-only captures avoid files for unchanged checks. Every-check recording creates a larger archive of images or WACZ files; account for the storage and retention you need.
- Destination verification: Check both PageCrawl’s history and Dropbox. A history entry helps distinguish a missing upload from a page that was never recorded as changed.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| No screenshot appears in Dropbox | No change was detected, screenshots are disabled for the monitor, or Dropbox is disconnected. | Review the monitor’s change history, confirm its screenshot setting, and inspect Settings > Integrations for Dropbox status. |
| PageCrawl reports a disconnected Dropbox integration | The Dropbox authorization expired. | Reconnect Dropbox in Settings > Integrations, authorize PageCrawl again, and verify the selected folder. |
| Files appear only when a page changes | The Dropbox instructions describe change-triggered uploads; every-check recording is a separate setting. | Enable Record every check if you need captures on unchanged checks. For screenshots, ensure Screenshots and Full Page Screenshots are enabled. |
| No WACZ archive is produced | Web Archiving may be disabled, the plan may not include the feature, or the monitor frequency may not meet the documented condition. | Check the current plan, enable Web Archiving, configure the monitor or its template/workspace, and confirm it runs every six hours or less often. |
| The Dropbox filename or folder is unexpected | PageCrawl organizes the upload using the selected folder, page name, and datetime. | Look under the configured destination for the page-name subfolder and timestamped JPG file. |
Cost and plan checks
PageCrawl’s Dropbox guide says the integration is available on all plans. Screenshot settings, full-page capture, WACZ access, check frequency, and storage limits can have separate plan conditions. In particular, PageCrawl documents WACZ archiving on Ultimate with the stated monitor-frequency requirement. Plan prices and limits can change; check the current PageCrawl plan page and your account before choosing a monitoring cadence or enabling every-check recording. [PageCrawl plans]
Or skip the browser setup
If you need a screenshot API for an application or script rather than PageCrawl’s change-monitoring and Dropbox workflow, ScreenshotNeo takes a URL in one GET request and returns an image or PDF. The examples use Stripe as the target URL; replace it with the page you need. See the ScreenshotNeo API documentation for request options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Python
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)
Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));
ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for ScreenshotNeo’s free plan.
FAQ
Does Dropbox receive a screenshot at every PageCrawl check?
The documented Dropbox workflow uploads when a change is detected. Use the separate Record every check setting when unchanged checks must also be captured.
Can I replay a screenshot like a website?
No. A screenshot is a static image. PageCrawl describes WACZ archives as replayable records of a fuller page state.
Where do uploaded screenshots go?
They go under the Dropbox folder selected during integration setup, in a page-name folder with a datetime-based filename.
Does PageCrawl offer the Dropbox integration on every plan?
Its Dropbox guide says the integration is available on all plans. Check your current plan for screenshot and archive feature requirements.


