Archivepanel

One file that still renders when the site is gone.

A capture drives a real browser, waits for the page to settle, and writes a single document with every stylesheet, image and font embedded and every script removed. It opens offline, anywhere, for as long as you keep it.

What happens, in order

Most pages take a minute or two. You do not have to wait on the page: progress updates in place, and a notification arrives when the capture lands.

1

Screen

The address, and every redirect after it, is checked. Private, loopback and link-local destinations are refused.

2

Open

Headless Chromium loads the page. A recognised consent banner is answered with its own accept button.

3

Settle

The browser waits for loading to finish, so content further down the page is fetched too.

4

Save

SingleFile embeds every stylesheet, image and font, prunes unused CSS and strips all scripts.

5

Verify

The preview is taken from the saved file, not the live page, so a broken capture looks broken on day one.

Five files per capture, each with a job

FileMade fromWhat it is for
.htmlThe live pageThe archive itself. Self-contained, script-free, opens offline.
.jpgThe saved fileRecognition and proof. Shows the capture kept its styling.
.txtThe saved fileReading and quoting. Headings, lists, tables and link targets kept.
.warc.gzAll of the aboveInterchange. WARC 1.1 for other archiving tools.
.jsonAll of the aboveAudit. A size and SHA-256 digest for every file, plus the tools and times behind it.
Only the document is essential. If one of the other four cannot be produced, the capture is still kept and the record says which is missing.

The page, not the overlay

A cookie banner is the usual reason a capture records nothing useful. It covers the page, and most lock scrolling while they are up, so the content below the fold never loads.

How banners are handled

  • Known consent platforms only. Each one's own accept control is pressed, which also opens pages that are gated behind consent.
  • No guessing. There is no "looks like a banner" rule that could remove a piece of the page with it.
  • Stated on the record. The snapshot says consent was accepted automatically, so it is honest about how it was taken.

When an attempt fails

A failure another try could get past, such as a timeout or a host that did not resolve, is retried automatically. Only the last failure raises an alert. A failure no retry can fix is reported at once.

StatusMeans
QueuedWaiting its turn, or waiting to try again.
RunningA browser is on the page now.
CompleteStored. The only status with files.
FailedThe record says what went wrong.
CanceledYou stopped it. Nothing was written.

Three attempts in all

  1. At once

    First attempt

    Requests you make by hand go ahead of scheduled work.

  2. 2 minutes later

    Second attempt

    The progress card says which attempt failed, why, and when the next starts.

  3. 10 minutes after that

    Third attempt

    If this fails too, you get one alert, and an email for a scheduled capture.

Snapshots are immutable. Nothing rewrites one. "Capture again" files a new snapshot beside the old, and deleting is the only way one leaves your account.

More features

Start with one page.

Create an account on the free tier, paste an address, and see the snapshot land in your archive.