The Fixity Fingerprint: A Simple Script to Prove Your Digital Files Haven't Changed

We often talk about preserving digital files for the long term, but how do you know the file you have today is the same file you had yesterday? Or last year? Bit rot, accidental overwrites, or even undetected corruption during a transfer can silently alter a file, turning a crucial document into a worthless string of gibberish. The first line of defense in any personal archiving strategy isn't a complex backup system—it’s something far simpler: the act of creating and verifying a fixity fingerprint.

In archival terms, 'fixity' just means the文件's state is fixed, unchanged. The fingerprint is a cryptographic checksum, a unique string of letters and numbers generated by an algorithm that reads every single bit in a file. The most common and reliable tool for this is the SHA-256 hash function. Change a single pixel in a photo, a single comma in a text file, or even its filename (in some cases), and the resulting hash will be completely different. It’s a digital seal of authenticity.

You don't need expensive software for this. The power is already in your computer's command line. On macOS and Linux, open the Terminal. On Windows, open PowerShell. The command is simple. Navigate to the folder containing your file and type: shasum -a 256 [your-filename-here] (on macOS/Linux) or Get-FileHash [your-filename-here] -Algorithm SHA256 (on Windows PowerShell). Hit enter, and in a second, you'll get a long string of characters. This is your fingerprint.

The real power, however, comes from storing this fingerprint separately from the file itself. I keep a simple text file, a 'manifest,' in a different location—even printed out in a physical notebook for my most critical archives. This manifest lists each filename alongside its unique SHA-256 hash. The separation is key; if my hard drive fails and I restore from a backup, I can run the checksum command on the restored file and compare it to the hash in my notebook. If they match, I have mathematical proof of integrity.

This practice transforms archiving from a passive act of storage into an active process of verification. It’s a ritual that forces you to confront the fragility of the digital object. Running the verification command is like checking the foundations of a building you assume is sound. Most of the time, it will be. But on the rare, heart-stopping occasion that the hashes don’t match, this simple fingerprint has just saved you from a future of relying on a corrupted, potentially unusable file.

It’s a small habit, but one that instills a deeper discipline. It reminds us that preservation isn't just about having copies; it's about having trustworthy copies. In a world of endless digital duplication, the fixity fingerprint is the quiet, unshakeable witness that confirms the chain of custody remains unbroken, one bit at a time.

Notes & further reading

A few pages I came back to while writing this: