Archivepanel

Save any page exactly as it looks today.

One file with everything inside it: text, images and styling. It opens in any browser, offline, long after the original has changed or disappeared.

Looks like the original

A real browser loads the page, so modern layouts, web fonts and images come out right.

Nothing to break later

Everything is inside one file. Move it, email it or file it anywhere, and it still opens.

The banner doesn't get in the way

Known cookie banners are accepted first, so you save the page, not the overlay. The record says so.

What happens when you press Capture

1

Check

The address, and every redirect after it, is checked before anything is fetched.

2

Open

A real Chrome browser loads the page and accepts a known cookie banner.

3

Wait

It waits for the page to finish loading, including content further down.

4

Save

Images, styles and fonts go inside one file. Scripts are removed.

5

Prove

The preview is taken from the saved file, so a broken capture looks broken straight away.

Questions

What is stored for each capture?

Five files, all counted towards your storage:

  • The page as one self-contained .html file. This is the archive.
  • A preview image, taken from the saved file rather than the live page.
  • A plain-text version for reading, quoting and searching.
  • A WARC file for other web-archiving tools.
  • A manifest with a size and SHA-256 fingerprint for every file.

If one of the last four cannot be made, the capture is still kept and the record says which is missing.

Why are scripts removed?

So the archive cannot change after it is saved, and cannot contact anything when it is opened. The saved file also carries its own rule against network access, wherever it ends up. Video and audio are not captured.

How are cookie banners handled?

Where a known consent platform is recognised, its own accept button is pressed before the page is saved. That also reveals pages that are hidden until you consent. There is no guessing: anything that is not a recognised banner is left alone, so no part of the real page is removed by mistake. The record states that consent was accepted automatically.

What if a capture fails?

Problems another try could fix, such as a timeout, are retried automatically after 2 minutes and again after 10. You get one alert if the last attempt fails too. Problems no retry can fix, such as a page over the size limit, are reported at once. A capture you stop writes nothing and costs no storage.

Can a saved page be changed later?

No. Nothing rewrites a snapshot. Capturing the address again files a new snapshot beside the old one, and deleting one takes your password.

Are there limits?

Each capture has 150 seconds, the saved page can be up to 48 MB, and pages are loaded in a 1440 × 900 window. Every limit is listed in the documentation.

More features

Keep the version that matters.

Start free with 100 MB of storage. No card required.