Protecting Your Archive Against Bit Rot

How to Generate and Verify File Checksums (MD5 / SHA-256)

In protecting your archive against bit rot when digitizing film or preserving legacy photographic archives, creating high-resolution archival master files is only the first step. Over time, digital media faces a silent threat: bit rot (data degradation caused by storage media wear, cosmic rays, or subtle read/write errors).

Without proactive tracking, a corruption event might go unnoticed until you open a TIFF file years later only to find half the image replaced by gray bars or distorted pixels. Thankfully, I have noty yet experienced this issue.

Generating and periodically verifying checksums gives your archive a digital fingerprint. If a single bit in a 100 MB file flips, the calculated checksum changes completely, warning you immediately so you can restore the damaged file from a clean backup.

What Is a Checksum? (MD5 vs. SHA-256)

A checksum (or cryptographic hash) processes every byte in a file through a mathematical algorithm to output a unique string of characters.

• MD5 (Message Digest 5): Faster to compute across massive image libraries, generating a 32-character hexadecimal string. While no longer recommended for cryptographic security due to collision vulnerabilities, it remains widely used for simple storage error detection.
• SHA-256 (Secure Hash Algorithm 256-bit): The modern gold standard for data integrity. It generates a 64-character hash and offers robust protection against corruption and collision risks.

How to Generate and Verify Checksums

1.Generate Checksums on macOS (Terminal):Native command line setup.

Open Terminal and navigate to your archive folder. To generate a manifest of SHA-256 hashes for all TIFF images in a directory:

Bash

cd /Volumes/ArchiveDrive/2026_Film_Scans/
shasum -a 256 *.tif > checksums.sha256

This creates a plain text file named checksums.sha256 containing every file name alongside its unique hash.

2.Generate Checksums on Windows (PowerShell):Native Windows utility.

Open PowerShell and navigate to your target folder:

PowerShell

Set-Location "E:\ArchiveDrive\2026_Film_Scans"
Get-FileHash -Algorithm SHA256 *.tif | Select-Object Hash, Path | Out-File -FilePath checksums.sha256

For GUI-based cross-platform workflows, tools like RapidCRC Unicode or GUI-tar automate this process with right-click context menus.

3.Verify Integrity Against the Manifest:Detecting bit rot.

To check whether any files have degraded or changed over time, run the verification command against your saved manifest:

macOS / Linux:

Bash

shasum -c checksums.sha256

Windows (PowerShell):

PowerShell

Get-Content checksums.sha256 | ForEach-Object { ... }

If the terminal returns OK for every file, your archive remains byte-for-byte identical to the day it was hashed. Any FAILED status signals bit decay, alerting you to swap the affected file with a healthy redundant backup.

Integrating Checksums into Batch Conversion & Open-Source Negative Inversion Workflows

When processing raw camera scans of film negatives, checksum verification fits naturally into every stage of the pipeline:

[ Camera Raw Capture ] ──> (1. Hash Raw Masters)
                                │
                                ▼
[ Batch Negative Inversion ] (e.g., Darktable / RawTherapee)
                                │
                                ▼
[ Export Archival TIFFs ]  ──> (2. Hash Final TIFFs)
                                │
                                ▼
[ Storage / Cold Backup ] ──> (3. Periodic Audit)

1. Protect the Raw Captures: Immediately generate SHA-256 hashes on your source RAW files (.CR3, .NEF, .ARW) before running automated color conversions.
2. Process in Open-Source Tools: Import your RAW files into open-source processing software like Darktable or RawTherapee. Apply your batch film negative inversion curves, color corrections, and non-destructive adjustments.
3. Export & Hash Archival Masters: Export your final inverted images as 16-bit uncompressed TIFF files. Generate a master checksums.sha256 file in the destination folder prior to syncing the directory to long-term cold storage or cloud mirrors.
4. Schedule Periodic Audits: Run a automated audit script every 6 to 12 months. Verifying hashes periodically ensures bit rot is caught and corrected long before you ever open the file for editing or publishing.

Was This Post Helpful?

Building this free educational archive is a labor of love! If this post helped you solve your problem today, please leave a like below to let me know you enjoyed it. Your support helps keep this site 100% free and ad-free for the archiving community.

Other posts in this new series – The Hardware & Optical Precision Loop.

Physical and Optical Precision: Masking, Alignment, and Newton’s Rings

Flatness Calibration & Depth-of-Field Precision

Digitizing 3D History & Complex Formats

Capturing Complex Scrapbooks, Fold-Outs, and Framed Media

DNG vs. RAW: Safeguarding Your Digital Master Files

Sharing Your Archive with Non-Technical Family

Ethical Archiving: Handling Sensitive Secrets, Medical Records, and Personal Privacy

Open-Source Film Inversion: Mastering Darktable’s Negadoctor Module

HOME

External Links

Here are two authoritative resources covering digital preservation, bit rot, and file fixity strategies for legacy collections:

• Digital Preservation Coalition (DPC) HandbookThe DPC provides comprehensive technical standards on bit preservation, checksum generation, and media decay risks. It covers hardware monitoring, fixity checks, and strategies to protect long-term digital media against silent data corruption.
• Library of Congress – Personal Digital ArchivingThe Library of Congress details practical guidelines for preserving high-resolution digital master files, photos, and family history collections over decades. It covers file format selection, storage redundancy, and long-term digital maintenance practices.