Computing • A PRACTICAL GUIDE

Use file hashes to check a copy without overclaiming what they prove

A matching checksum can answer whether two files contain the same bytes. It cannot answer every question about trust, safety or recoverability.

Portable storage equipment

The narrow question a hash can answer

Imagine copying a folder of finished recordings to an archive drive. The filenames look correct and the sizes appear plausible, but you want another way to check that the files arrived intact. A cryptographic file hash is a compact value calculated from a file's contents. When the same suitable algorithm produces matching values for an original and a copy, that is strong evidence that the bytes match. It is a useful check precisely because the question is narrow. You are comparing content, not judging whether the recording is good or whether the archive will survive the next ten years.

A hash is not a miniature copy of the file and cannot restore missing material. Nor does it automatically make an unfamiliar download trustworthy. A malicious file can have a perfectly valid hash. If both the file and the advertised checksum come from the same compromised source, comparing them does not establish an independent chain of trust. Keep this distinction in view before adding checksum checks to an archive routine: integrity, authenticity and recoverability are related concerns, but they require different evidence.

Choose a small safe starting point

Start with one non-sensitive file and a copy made through the normal file manager. Keep the original unchanged. Give the destination a clear name and check the full path before running a tool against it. Working with a single known file avoids the confusion of comparing two folders that happen to contain similarly named documents. It also makes the result easy to understand when you are learning the process.

Use a built-in or well-established tool documented for your operating system, rather than uploading private files to an online checksum calculator. Local calculation lets the content stay on your computer. Windows PowerShell provides Get-FileHash, with SHA256 as its default algorithm according to Microsoft's documentation. Other systems have their own documented commands and utilities. Read the relevant help for your version, choose the same algorithm on both sides and save the result with the file's path. Avoid relying on a screenshot that shows a value without identifying the file it came from.

Compare like with like

The algorithm is part of the result. Values from two different algorithms are not comparable, even when they describe the same file. Likewise, a hash of a compressed archive is not the same thing as a hash of the folder's extracted contents. Decide which object you want to verify and calculate the value for that object on both sides. If you downloaded a single archive and the publisher provides its checksum, compare the downloaded archive before extracting it.

Copy the complete value rather than comparing the first few characters by eye. A reputable comparison utility can reduce transcription errors, especially for many files. If you do compare manually, use a text view where long lines are not truncated. Check for a hidden horizontal scroll bar or a shortened display column. A partial match is not a complete verification. Record the algorithm, full value and filename together so the evidence remains understandable when you return to it later.

Let a mismatch interrupt the workflow

A mismatch means that the inputs or the calculation conditions differ; it does not immediately identify the cause. You might have selected the wrong copy, calculated a value before an application finished saving, or compared a newly edited document with an older version. Check those possibilities before concluding that a cable or drive has corrupted data. Do not overwrite the original while investigating. Preserving both versions gives you something to compare and prevents a confusing situation from becoming a loss.

Close the file in the application that created it, wait for the save to finish and recalculate both sides. Confirm the paths again. If the mismatch persists, make another copy into a new destination folder and compare that copy. Repeated inconsistent reads or copy errors deserve attention, but avoid treating one unexplained difference as a diagnosis of a particular hardware fault. The useful response is to stop the archive job, preserve evidence and check the equipment through supported diagnostics or qualified assistance if needed.

Make a manifest people can read

For a collection, a manifest is simply a record that associates each file with its relative path, chosen algorithm and calculated value. Relative paths help when the collection moves from one drive letter or folder location to another. Include a short note describing when the manifest was made and whether the collection was intended to remain unchanged. A manifest without context can become another mysterious file that nobody knows how to use.

Store the manifest with the collection and keep another copy alongside your archive records. Do not put passwords or recovery secrets inside it. A checksum list usually reveals filenames, so consider whether those names contain personal information before sharing it. For a small family photo collection, readable names and a short explanation may matter more than a sophisticated automation script. The next person should be able to tell what is being checked and where to find the originals without reconstructing your computer setup.

Expect edited files to produce new values

A hash comparison is exact about bytes, which means ordinary, legitimate edits can change the result. A document might look almost identical after an application updates internal metadata. A photo can acquire a new tag or editing instruction. A media container can be rewritten without an obvious difference during casual playback. These are reasons to understand the workflow, not reasons to ignore mismatches. If you expect files to be edited, make a new manifest for a clearly named new version.

Separate an active working collection from a completed archival package. In the working collection, change is normal. In the archival package, unexpected change deserves investigation. Keep dates and version notes at the package level rather than renaming every file after each minor edit. This approach makes verification meaningful: you know whether a changed value reflects an intentional revision or a surprise. It also reduces the urge to replace the old manifest automatically whenever a check fails, which would erase the very signal you wanted to preserve.

Verification does not replace a restore exercise

A matching hash says nothing about whether you will remember an encryption password, find the correct backup or have an application capable of opening the file. Test those parts separately. Restore a sample into a separate temporary folder, open it and check that the content you care about is usable. Never perform a trial restore over the only working copy of a live project. A safe rehearsal should add confidence without risking current work.

For complex projects, check dependencies as well as the main file. A video-editing project may refer to media stored elsewhere; a design document may depend on fonts or linked images. Hashing the project file cannot detect assets you forgot to include. Write down what belongs in the package and verify that the restored folder contains it. For particularly important records, consider an additional widely readable export where appropriate, while retaining the original. Exact bytes and practical usability are both worth checking, but neither should be mistaken for the other.

Keep the habit proportionate

You do not need to calculate checksums every time you move a casual shopping list. The technique is most helpful when silent changes would matter, a large transfer is difficult to inspect manually, or a publisher provides an independently meaningful checksum for a download. Start with one finished collection and make the process understandable before automating it. A small procedure you can repeat reliably is more useful than an elaborate script nobody knows how to maintain.

Keep a brief verification log containing the collection, date, algorithm, result and any action taken. If a later check fails, preserve the old manifest and the suspect copy rather than editing the record to make it pass. Look for a known-good independent copy and seek help if the material is irreplaceable. Checksums are evidence, not insurance. Their value comes from using that evidence carefully, alongside separate copies, readable formats and rehearsed recovery, rather than asking a long string of characters to guarantee the entire future of your archive.

Handle the record as part of the collection

The manifest should travel with enough explanation that a future reader does not need the original author's memory. Include the tool name, the chosen algorithm and the folder layout it expects. If you rename or reorganise files, update the path information deliberately and retain a note describing the change. Moving an unchanged file can preserve its content hash while invalidating the path recorded in a manifest. That is an organisational difference, not evidence that the file's bytes changed.

Be careful when interpreting the results of a folder-wide tool. Some tools report a missing path and stop; others continue and summarise missing or additional files separately. Read the summary and the documented behaviour rather than looking only for a green indicator. A collection with an extra unrecorded file can have a different practical meaning from one with a missing recorded file, even if every file that was compared matched successfully. The verification report needs to say which objects were actually checked.

For a handover, put a short plain-language explanation beside the technical list. State that the values check exact file contents and that the files still need ordinary backups. Name the person or organisation responsible for maintaining the collection. This turns a checksum manifest into a usable maintenance record rather than an unexplained technical attachment.

Further reading

Questions or a correction? Contact Tian Xin Kai at [email protected].

General educational guidance. Features vary; check your device documentation before changing settings.

Search the journal

Privacy choices

Google advertising is integrated. Consent settings are not available until the consent platform is configured.

When Google's consent platform is configured, this link will reopen its settings. This information panel does not record consent.

Read our Privacy Policy

Contact: [email protected]