Find pages to review
Use the previous-collection report to narrow down added or changed pages. Keep collection scope comparable.
← Use cases
✓Save & compare revisions
Keep before and after. Review what changed.
Keep separate copies so you can explain which wording you reviewed. Use the collector’s previous-run change report to find affected pages, then read the before-and-after material or ask an external comparison tool or AI about the actual content.
Download Grab All Files in your browser:Download for ChromeDownload for EdgeDownload for FirefoxSecurity
Keep previous and current pages
Before- guide.html
- notes.html
After- guide.html
- notes.html
- new.html
Save the change report
changes.md- + Added
/new - ~ Body updated
/guide - ~ Title changed
/notes
- + Added
Review before and after
Manual handoff
Before After Form Form + Attachment
Compare this extension’s most recent completed collection on the same site with the current pages, using comparable scopes. You review the originals; this is not automatic monitoring or a line-by-line diff. Unavailable entries do not prove site deletion.
Save & compare revisions in the extension
Choose the pages to collect again
Actual extension screen using sample materials. Confirm the pages to collect again and their output settings before recollection. A Free example with one selected page, showing settings and controls before saving. Pro combines multiple selected pages as described in this guide.
Open the full-size image ↗After collection: change-report menu
Choose the action for saving a change report against the previous completed collection on the same site.
Open the full-size image ↗Settings you can choose — pictures from the extension
Pictures and names are the extension’s own cards.
Separate change detection from content comparison
Compare the wording
Read saved originals or use external tools to compare requirements and exceptions. Verify findings in both versions.
Best for
- ✓Check revised procedures, requirements or public guidance against a saved copy.
- ✓Retain the stated revision and source so an update can be explained later.
Workflow
- 1Open the permitted source and choose “Combine pages into HTML” in the extension. Select the pages and note the source’s stated revision yourself.
- 2Save the collection with a recognizable before label. Later, manually collect the same site and comparable page scope and save a separate after copy.
- 3After the later collection, press “Save change report vs. previous run”. Check added, updated and removed-or-unavailable entries against the collection results.
- 4Read the two originals side by side or manually give supported before/after files to an external comparison tool or AI. Confirm any claimed change in the source wording.
Ask for evidence of a change
Compare a procedure
Compare only the supplied before and after materials. List changed steps, requirements and exceptions with supporting passages and source URLs. Mark uncertain comparisons rather than inferring a revision.
Keep a clear comparison set
| Material | Role |
|---|---|
| Before / after HTML | Store separately and read collected page content with context. |
| Previous-run Markdown report | Summarizes changes relative to the same site’s previous completed collection. |
| Source notes / AI export | Record the manual’s stated revision yourself. Use AI source URLs and capture dates for checking. |
FAQ
What does the built-in change report compare?
The report uses this extension’s most recent completed collection before the current one on the same site. It summarizes page-URL, title and collected-body changes, not line-by-line or official-revision interpretation. For arbitrary saved PDFs or other before/after files, compare their content in an external tool.
Does a removed entry prove the site deleted that page?
No. It may reflect different selection, collection failure or unavailable content. Compare the page scope and results before treating it as a source deletion.
Does the extension watch for updates or recover old versions?
You collect again manually. Use previously saved material or versions published by the source; it does not monitor pages automatically or recover an older version you never saved.
How do I record the revision, and what does Free cover?
Record the source’s stated revision yourself in titles or notes; the source URLs and capture dates in the AI output help with tracing. Free saves one chosen page per run, so compare one key page at a time; Pro collects multiple selected pages, which suits comparing a whole section.
What if a page needs me to sign in?
Collection uses your own browser session and does not collect credentials. If a page is marked “Sign-in needed”, press “Open the site to sign in”, sign in in that tab, then press “Resume”. Pages that still need a sign-in are not saved, and the result says how many were left out.
Why is some text missing from the saved page?
Some sites add text only after you scroll or click. Open “If a page is missing text: content and JavaScript settings”, turn on “Scroll down to load content that appears later” or “Press ‘Show more’ to include the continuation”, and collect again. If the wrong part of the page was kept, use “Select on screen” there to pick the main text.
Related use-case guides
Product catalogs & datasheetsIR & financial report PDFsTender & application documentsFile links to CSVSDS & technical documentsarXiv PDFs & research filesWeb tables to CSVSave & compare revisionsRename & organize PDF downloadsGovernment documents & guidanceWeb sources as MarkdownSave manuals & knowledge pagesCollect, read & analyze with AICombine pages into HTMLLocal HTML files into onePages with the original designDownload all PDFsBulk-download imagesDownload files from a pageInternal portals & LMSMerge PDFs locally
Try Grab All Files on your browser.
Free saves up to 10 files per download in the file downloader, and one chosen page per run when you combine pages into HTML; that page’s linked files are saved 10 at a time with “Save the next 10”. Pro ($19.99 one-time, up to 3 devices) removes the per-download cap and combines multiple pages into one HTML.