Web Preservation System
Archivepanel captures a page into a single self-contained HTML file — every stylesheet, image and font embedded, every script stripped — and files it in your private account. Nothing is ever rewritten, and nothing depends on the original site still being there.
Free tier, no card required/ 50 MB of snapshot storage/ Two-factor sign-in on every account
The problem
Pages get edited, paywalled, redirected and deleted. Screenshots lose the text. "Print to PDF" loses the layout. A saved page dumps a folder of assets that half-loads a year later. And a link in a citation, a contract, a compliance file or a dispute is only worth what the other side's server still says today.
Terms, prices, policy statements, published claims. Each snapshot is stamped with the address it came from and the moment it was taken, and it is never modified afterwards.
Capture the page you cited, keep the plain text beside it for quoting and grepping, and export WARC when an institution accepts nothing else.
Point a schedule at a page — or at a sitemap, and get the whole section — and the history builds without anyone remembering to press a button.
How a capture works
The address is validated first. Anything resolving to loopback, private, link-local or carrier-grade NAT space is refused outright.
Headless Chromium loads the page, dismisses a cookie banner if it recognises one, and waits for the page to settle. Stylesheets, images and fonts are embedded, unused CSS pruned, scripts stripped.
The preview is a screenshot of the saved file, not the live page — so a capture that lost its styling looks wrong immediately, not a year later.
A structured plain-text version is derived from the same bytes, so the text and the archive can never disagree about what the page said.
Document, preview, text, WARC and manifest are written to private storage under your account, and counted against your allowance.
What you get
Not one format you have to live with. The document for reading, the image for recognising, the text for quoting, the container for everyone else's tools, and a manifest that accounts for all four.
| File | What it is | What it is for |
|---|---|---|
| .html | Self-contained document | The page itself, assets inlined as data URIs and scripting removed. Opens in any browser with no network access at all. |
| .jpg | Preview image | Rendered from the saved file. Makes a snapshot recognisable in a list, and proves the capture actually kept its styling. |
| .txt | Plain-text snapshot | Headings underlined, lists bulleted, tables drawn as an ASCII grid, link targets printed beside their text. Read, quote, grep and diff without opening a megabyte of HTML. |
| .warc.gz | WARC 1.1 container | The interchange format the rest of the web-archiving world reads. Downloads as one file carrying the document, the text and the screenshot together. |
| .json | Capture manifest | A size, a SHA-256 digest and a content type for every stored file, plus the addresses, times, viewport and tool versions behind the capture. An inventory or an integrity check without opening the snapshot. |
Capabilities
A page schedule captures its own address. A sitemap schedule reads the address as an XML sitemap and captures the pages it lists — index files included — so one schedule covers a whole section of a site and keeps covering it as the site grows.
Status, stage and progress update in place while a capture runs. When one finishes, fails or is stopped by a quota, a notification is waiting in the tray — and arrives as a toast if you are still looking.
Every capture is also rendered to structured plain text from the stored bytes. Compare one week to the next, quote a paragraph, or search a snapshot without loading it.
Every capture is packaged as a WARC file so a snapshot taken here is not trapped here. It replays in ReplayWeb.page and pywb, and satisfies an archive that accepts nothing else.
The bucket is private and no signed URL is ever handed out. Viewing, downloading and WARC export each stream the object from behind the session gate, so a link to an archive is worthless to anyone else.
Sign-ins, captures, schedule changes and deletions are recorded, so the question "who did what to this record, and when" has an answer.
Every snapshot you hold is grouped by host. Searching inside a site reads the stored text of its snapshots and shows you the passage that matched, so a page can be found by something it said rather than by its title.
A cookie banner covers the page and usually locks scrolling with it, so everything below the fold never loads. Where a known consent platform is recognised, its own button is pressed before the page is saved — and the record says what was done about it.
Each record carries what the page declared about itself — language, canonical address, author, published date — and how its host resolved at that moment: the addresses it answered on, the CNAME behind a CDN, the authoritative nameservers and the certificate it served.
Security
An archive is somebody else's HTML, stored on our infrastructure and later opened in your browser. Most of the engineering here is about making that safe rather than merely convenient.
Create an account on the free tier, paste an address, and watch the snapshot land. Every archive is exportable as WARC from the moment it exists.