
Web archiving for journalists means keeping a checkable copy of the online material a story relies on. It helps when a page changes, a link disappears or an editor asks what you actually saw. The useful unit is a particular source at a particular time, together with enough context to explain why it matters.
Start with one page you expect to cite. Save it, open the saved result and check the exact passage or image your reporting depends on. A successful capture message is only the start of that check.
Choose a public or confidential workflow first
A public press release and a confidential source document need different handling. Decide who should be able to retrieve the material before sending it to an archive or capture service. The fact that you can open a page does not mean it belongs in a public archive.
The Internet Archive is useful for finding older versions and saving accessible public pages. Its Wayback Machine help explains that coverage can be missing because of access restrictions or exclusions. An on-demand save is not a whole-site backup or a promise to capture future changes.
For confidential material, use your newsroom’s approved storage and source-protection process. In Permavault, regular captures can be retrieved by anyone with their address. Private file capture locks a local file in the browser before upload; Private web-page capture has a different capture process. Read how Private works before choosing a lane for sensitive material. Do not assume that a private web page is hidden from every service involved in making the capture.
Record the exact source and the reason for keeping it
Use the specific article, statement or document address rather than a site’s homepage. Note the title, author or publishing organization if shown, the time you accessed it and the passage or image relevant to your story. Keep a displayed publication date separate from the date you accessed the page.
Store those notes beside the source record in a place your editor can access. A useful note is specific: “The second paragraph states the project starts in June.” “Background material” is harder to use when the page changes six months later.
If the source is an attachment, preserve the attachment itself as well as the page that links to it, when you have the right to do so. A saved link to a PDF does not establish that the PDF’s bytes were included in a web capture.
Check what the saved copy actually contains
Open the saved page or replay the downloaded archive. Inspect the parts that support your reporting, not only the first screen. A capture can miss a chart, a loaded-on-scroll image, a linked document or content that required a signed-in session.
Keep a small check record:
- The text or image relied on is present and readable.
- The relevant address and recorded date are identifiable.
- Important attachments have their own saved copies when needed.
- Missing or incomplete elements are described rather than guessed.
- The saved material can be reopened outside the original browser session.
A screenshot or PDF can help explain what was visible. It is a different kind of record from a replayable web archive. If you keep both, label them clearly; do not describe either as a complete recording of a whole site.
Keep the original package and the context together
Download the archive and evidence package when your capture method offers them. Keep those originals in approved storage, with a separate working copy for annotations or redactions. Editing a working copy should not silently replace the preserved original.
A file hash is a fingerprint calculated from its bytes. Comparing hashes can show whether two copies match. A signature can show that a signing key signed a recorded value. An independent timestamp supports when the value it commits to existed. Those checks do not establish that the source’s claims were true or who wrote the original page.
Our WACZ verification walkthrough explains how to inspect a packaged web archive and its proof material. For Permavault, use the actual package’s instructions and proof status. A staged save has not yet completed permanent storage, and a submitted Bitcoin timestamp can still be pending. Private packages have their own encrypted-record and verification requirements.
Give your editor a retrievable source record
For a fictional council-spending story, a useful handoff could say: “Council project update, accessed October 30. The quoted budget is in paragraph three. The archived text is readable; the linked spreadsheet was saved separately. Original packages are in the reporting folder; the annotated PDF is a working copy.”
Agree on who can open each item, where the originals live and who keeps the reference if you leave the assignment. Test retrieval once with the intended recipient. Do not forward private vault recovery material or a confidential source address merely to make a handoff easier.
When you revisit the source, preserve a new version if it matters to the story and record what changed. Keep both versions. A hash difference tells you the files differ; the reporting still needs to explain the relevant change.
Where Permavault fits
Permavault can capture an accessible web page and store the result permanently, with downloadable proof material for checking it independently. It does not bypass publisher restrictions or guarantee that every page or resource can be captured. Review the result before relying on it, and confirm permanent storage has completed.
Use the public archive when it serves the source and your disclosure needs. Use a capture you can retain and verify when you need your own record. The web-archiving comparison explains those choices; current pricing distinguishes capture methods and optional certificates. No certificate makes a source true or guarantees acceptance in a dispute.
The practical habit is small: preserve the exact source, check the saved content and keep the context that lets another person understand it later.



