The Case for the Corrupted File: Why Digital Purity is a Preservation Fallacy

In digital preservation, the goal is often framed as an unwavering pursuit of purity. We seek the perfect, unaltered bitstream. We venerate the pristine master file, the exact original, the flawless copy. Corruption—that dreaded word—is the ultimate enemy, the sign of failure, the digital equivalent of mold and decay. But what if, in our zeal for this kind of purity, we’ve misunderstood the nature of history and are archiving a sterile fiction? What if the corrupted file has something vital to tell us?

The common advice is clear: validate, checksum, repair, and migrate to a perfect new format. The artifact must remain functionally identical. But this process systematically scrubs away the evidence of time’s passage. A pristine PDF from 1998, rendered flawlessly on a modern screen, feels timeless, disconnected. It tells us what was written, but not how it was *lived with*. A corrupted version of that same file, however, one with garbled fonts from a missing encoding, or a graphic dissolved into pixelated blocks, is a document of a different kind. It is a fossil bearing the marks of its environment. It shows us what broke, what was fragile, what dependencies were severed. The corruption is a historical event, etched into the data itself.

The Ghost in the Glitch

Think of a scanned municipal record from the early 2000s, saved in a proprietary format. Our instinct is to migrate it to a modern, open standard, creating a clean, accessible file. In doing so, we erase the digital ‘foxing’—the compression artifacts, the software-specific rendering quirks that placed that document squarely in its technological moment. The glitch becomes a ghost, a whisper of the obsolete operating system or the long-defunct scanner driver. This isn’t data loss; it’s a layer of metadata about technological obsolescence that no descriptive tag can capture.

By treating all corruption as noise to be eliminated, we risk creating archives that are paradoxically ahistorical. They are collections of perfect, placeless documents, floating in a timeless digital void. They lack the patina, the wear, the evidence of use and technological shift that give physical archives their rich texture. A 300-year-old ledger with water stains, marginalia, and brittle pages doesn’t just contain information; its physical state *is* information. Our digital preservation standards often aim to create the equivalent of that ledger’s text perfectly typeset in a new book, losing the object’s biography in the process.

This isn’t an argument for negligent storage. Backups should be robust, and functional access is paramount. But perhaps our repositories need a new kind of shelf—one for the ‘damaged’ artifacts. We should be capturing and curating not just the restored file, but the journey of its decay. A preservation system could hold the original corrupted bitstream alongside its repaired counterpart, alongside the emulation environment that can render its glitches, treating the corruption not as an error but as a feature of the artifact’s life.

In our quest to save everything perfectly, we may be saving a sanitized version of our past. The broken bits, the corrupted sectors, the files that scream in error when opened—they are the digital equivalent of cracked pottery, faded ink, and torn bindings. They are the record of the medium’s own mortality. To archive only the pure is to believe we can freeze time. To archive the corrupted, and understand its story, is to finally archive time itself.

Notes & further reading

A few pages I came back to while writing this: