Movie Encoder
Windows 10 & 11 Buy license · $79.95
Archive & pro

How to Verify Video Files with SHA-256 Checksums on Windows and Beyond

Create and check SHA-256 checksums for video files and whole folders on Windows with certutil and PowerShell, and learn what a matching hash proves.

Updated 4 minute read The Movie Encoder team

To verify a video file with a SHA-256 checksum, generate a hash of the file when you know it is good, save it, and later generate the hash again and compare the two. If they match exactly, the file has not changed by a single bit. On Windows you can do this without extra software using certutil -hashfile video.mp4 SHA256 in Command Prompt or Get-FileHash video.mp4 in PowerShell.

This guide explains what checksums prove and what they do not, how to create and check them for single files and whole folders, and how to fit verification into a sensible routine for video archives and transfers.

What a checksum is

A checksum (or hash) is a short fingerprint calculated from every byte of a file. SHA-256 produces a 64-character hexadecimal string. Change even one bit in a multi-gigabyte video and the hash changes completely, so comparing hashes is a reliable way to tell whether two files are identical.

Checksums are useful whenever video moves or sits in storage for a long time:

  • After copying to an external drive, NAS or cloud storage, to confirm the copy is perfect.
  • Before and after delivery, so the recipient can confirm they received exactly what you sent.
  • Periodically in an archive, to catch silent corruption ("bit rot"), failing drives or accidental edits before your backups are also affected.
  • After a download, to check the file against a hash published by the source.

Why SHA-256

AlgorithmHash lengthStatus
MD532 hex charactersFine for detecting accidental corruption, but broken for security - files can be deliberately crafted to collide
SHA-140 hex charactersAlso has practical collision attacks; being phased out
SHA-25664 hex charactersCurrent standard; no practical collisions known
xxHash and similarVariesVery fast, popular in film and TV data wrangling; not designed for security

For simply spotting accidental damage, any of these works. SHA-256 is a good default because it is secure, universally supported and accepted by archives and institutions. Many older archives use MD5, and there is no need to recalculate them all - just be consistent and record which algorithm each checksum uses.

Checking a single file on Windows

In Command Prompt:

certutil -hashfile "D:\Video\interview.mov" SHA256

In PowerShell:

Get-FileHash "D:\Video\interview.mov" -Algorithm SHA256

SHA-256 is the default for Get-FileHash, so the -Algorithm part is optional. Either command prints the 64-character hash. Compare it with your saved value; capitalisation does not matter, as hex hashes are case-insensitive.

On macOS and Linux the equivalent is shasum -a 256 file.mov or sha256sum file.mov.

Checking whole folders

For a collection, save a list of hashes as a manifest. In PowerShell, this creates a CSV of every file in a folder and its subfolders:

Get-ChildItem "D:\Archive" -Recurse -File | Get-FileHash | Export-Csv "D:\Archive-hashes.csv" -NoTypeInformation

Store the manifest with the archive and keep a second copy elsewhere. To verify later, generate a fresh list the same way and compare the two by path and hash. A file whose hash differs has changed; a file missing from the new list has disappeared; a new file has been added.

On macOS and Linux, sha256sum can write and then check a manifest directly: create it with sha256sum *.mov > manifest.sha256 and verify with sha256sum -c manifest.sha256. Many archives also use the BagIt packaging format, which bundles files with a checksum manifest in a standard structure.

What a checksum does not tell you

A matching hash proves the file has not changed. It does not prove the file was good to begin with, and it says nothing about whether two different encodes look the same.

  • Re-encoded or remuxed files will never match the original. Converting MOV to MP4, even with stream copy, rewrites the container and changes the hash, though the video data may be identical. To compare content rather than files, use per-frame hashes of the decoded video, as described in FFV1 lossless video archiving.
  • Metadata edits change the hash. Renaming a file does not, but changing tags inside it does.
  • A corrupt file hashed when it was already corrupt will verify perfectly. Check that files play correctly before creating the reference checksum.

For a quick check of whether a video decodes cleanly, FFmpeg can decode it without writing an output and report any errors:

ffmpeg -v error -i input.mkv -f null NUL

No output means no errors were found while decoding. If a file has problems playing after conversion, our guide to converted videos that won't play covers other causes.

A simple verification routine

  1. Check the source plays and decodes cleanly before you trust it.
  2. Create SHA-256 checksums at the point of ingest, before copying anywhere.
  3. Copy, then verify every copy against those checksums. Do not delete originals from a camera card or old drive until the copies verify.
  4. Store manifests with the files and separately.
  5. Re-verify on a schedule - many archives check every six to twelve months - and after any migration to new storage.
  6. Repair from a good copy when a check fails, then re-verify.

Checksums work best combined with multiple copies on different media. They tell you which copy has gone bad; the other copies let you fix it. For moving between file formats safely, how to convert video on Windows covers the basics.

Doing it with Movie Encoder

Movie Encoder's Archive and Verify tools create SHA-256 checksums of sources and outputs, verify them later, and compare streams, duration, resolution and metadata between files. It produces preservation manifests and reports in JSON, CSV and plain text, and can verify whole batches at once.

Its encodes are written to a temporary file and only moved into place after finishing and passing a check, partial encodes are never marked complete, and originals are never overwritten or deleted.

Frequently asked questions

Does renaming a video file change its SHA-256 checksum?

No. The hash is calculated from the file's contents, not its name or location. Editing metadata inside the file, however, does change it.

Why doesn't my converted MP4 match the original's checksum?

Any conversion or remux rewrites the file, so the hash will always differ even if the video data is identical. To compare content, use per-frame hashes of the decoded video instead.

Is MD5 good enough for checking video files?

For spotting accidental corruption, MD5 still works. SHA-256 is preferred because it is also secure against deliberate tampering and is the common standard for archives today.

Get three guides like this every month, plus software update notices.Subscribe →