The Myth of the Frozen State: Why Digital Preservation is Not a Passive Art

There’s a quiet, powerful image that often shapes our thinking about digital preservation: the time capsule. The notion that we can capture a piece of the web, a dataset, or a document, seal it in a digital vault, and know it will remain exactly as it was. It’s a comforting idea, a promise of permanence in a fluid world. But it’s also a myth—a dangerous one that misunderstands the very nature of the work.

The myth tells us preservation is about creating a perfect, static copy. It suggests that once the metadata is logged, the checksums are run, and the file is safely tucked into three geographically dispersed servers, the job is done. The record is ‘preserved.’ This is the frozen state ideal. It’s clean, it’s technical, and it’s entirely passive. The keeper’s role is merely to prevent thaw.

But data is not an insect in amber. It is a set of instructions, a performance waiting for a stage. A spreadsheet from 1995 isn’t just bits; it’s a dance between those bits and a specific software that understands their particular arrangement. Preserve only the bits, and you have a fossilized script for a play no one can perform. The platform, the operating system, the codec, the font renderer—the entire technological ecosystem—are part of the artifact. And that ecosystem is in constant, violent motion.

True preservation, then, is not passive curation but active translation. It is the continuous, often interpretive work of making old signals intelligible to new receivers. It means migrating file formats, emulating obsolete environments, and maintaining the context that gives raw data its meaning. It’s less like storing a specimen and more like keeping a flame alive, constantly feeding it new fuel as the old burns away.

The Cost of the Freeze

Believing in the frozen state has consequences. It leads to collections that are technically ‘safe’ but functionally dead—petrified forests of data that no contemporary tool can animate. It encourages a focus on the ‘what’ over the ‘how,’ on the artifact over the experience. We end up with perfect copies of things that are, for all practical purposes, lost.

Worse, it absolves us of the harder, more philosophical work. If preservation is just freezing, we don’t have to ask difficult questions: Which versions of this dynamic database should we keep? How do we preserve the feel of a 90s GeoCities page, not just its HTML? What do we do when the ‘original’ experience required proprietary software that no longer exists? The myth lets us off the hook, allowing us to confuse storage with stewardship.

The reality is messier, more human, and more vital. Digital preservation is a craft of perpetual care. It accepts that some loss is inevitable, and focuses instead on maintaining intelligibility across time. It acknowledges that every act of preservation is also an act of interpretation—a decision about what is worth carrying forward and how it should be presented to the future.

So let’s retire the metaphor of the vault and the time capsule. A better image might be the gardener tending a heritage seed bank, who must not only store the seeds but periodically plant them, learn their quirks, and save new stock, ensuring the line remains viable in changing soil. The work is never finished, because the ground is always shifting beneath our feet. Preservation isn’t about stopping time. It’s about building a bridge through it.

Notes & further reading

A few pages I came back to while writing this: