Capture Collections is not available yet
PageShotter’s free single-page capture is the current product. We are publishing this plan early to learn which batch workflows are worth building.
From repeated captures to one collection
Capturing one page is simple. Capturing twenty pages means repeating the same clicks, renaming files, tracking failures and combining the output yourself.
The Capture Collections concept turns that repetition into one visible queue. The current plan includes:
- adding the current tab or selecting several open tabs;
- pasting a list of URLs;
- capturing pages sequentially;
- retrying an individual failure without restarting the collection;
- filename templates;
- ZIP and combined PDF export;
- a per-page success and failure report;
- local history for recent collections.
This is a product direction, not a promise that every listed feature will ship unchanged.
Why run batch capture inside Chrome?
Many remote screenshot services work best on public URLs. That becomes awkward when the pages you need are dashboards, staging environments, internal tools or other pages behind your existing login.
Capture Collections is intended to use the browser environment you already have instead of asking you to upload credentials or recreate authentication in a remote service.
It will not bypass authentication or access controls. You remain responsible for having permission to view and capture every page in a collection.
An honest constraint of Chrome screenshot capture
Chrome may require each target tab to become active while its screenshot is taken. If that remains necessary, PageShotter will make the tab switching clear rather than requesting broad or alarming permissions to hide it.
Any broader site access needed for a future collection workflow will be requested only when that workflow needs it. Free capture of the current page will keep its minimal-permission model.
Who is this for?
Capture Collections may be useful for people who repeatedly archive or review sets of webpages, including:
- quality assurance and release teams;
- design and content review;
- research and documentation;
- client reporting;
- records of authorized dashboards and internal tools.
Help choose what gets built
Email us with the number and kind of pages you capture, how often you do it, and the output you need. Please do not send private URLs, credentials or confidential screenshots.