A screenshot is often what survives after everything interactive is gone.
It can preserve a headline, layout, username, photograph, comment, error message, or strange little piece of interface that no crawler captured. That makes screenshots valuable. It also makes them dangerously easy to overread.
A screenshot preserves pixels. A website is more than pixels.
What the image actually proves
With sound provenance, a screenshot can show that a particular screen displayed particular visible material at a recorded moment. It can preserve typography, relative placement, colors, advertisements, timestamps printed by the site, and content that was visible only after interaction or login. Without provenance, the pixels alone cannot prove when, where, or even whether the image came from the claimed live page.
What it usually does not preserve is the target of a hyperlink, the HTML source, hidden text, alt text, JavaScript state, network requests, content below the captured viewport, or the difference between something rendered by the server and something inserted by a browser extension.
That difference is why professional web archiving normally saves structured web material rather than only taking pictures of it. The Library of Congress describes the WARC web-archive format as a container for harvested resources plus record information such as target URI, date, type, and other metadata. Its preservation guidance also says archived content should identify the archiving institution, capture time, and limitations in functionality.
A PNG by itself carries far less context.
Provenance makes a screenshot stronger
Suppose the only surviving evidence of a deleted forum post is Screenshot_2024-03-11.png.
That is better than nothing, but a researcher immediately wants more. What was the full URL? Who took the screenshot? Was the user logged in? What time zone did the site’s displayed timestamp use? Was this the whole thread or a cropped section? Was the image edited after capture?
A useful preservation package records the original URL, capture date and time, browser or app, account state if relevant, and a short explanation of what was being documented. Keeping the uncropped original alongside any annotated derivative is better than saving only the version with arrows and circles added later. A checksum can help show that the preserved image itself has not changed since it entered the collection.
Nearby screenshots can also restore context. Capturing the page above and below the disputed item, the profile that posted it, or the navigation that led there can be more useful than one perfectly framed viral rectangle.
Screenshots are evidence, not a replacement website
Sometimes nothing better survives. In that case the screenshot deserves preservation precisely because it may be the last visible trace of the artifact.
But the limits should travel with it.
A screenshot cannot normally prove that a link worked. It cannot reconstruct a deleted video. It may not reveal whether text was selectable, dynamically loaded, or changed seconds later. And without provenance, future researchers may be unable to distinguish a genuine capture from a mockup.
The proper conclusion is not that screenshots are useless. It is that they need witnesses.
When the living webpage is gone, a screenshot may be the body. URLs, timestamps, capture notes, surrounding files, and independent corroboration are what give it a name.