Verify a video copy with a SHA-256 checksum
Updated: November 17, 2026
A filename and a matching duration do not prove that a transferred video is identical. A checksum helps compare the local master with an original-file copy received elsewhere.
Diagnose before editing
Use this check only when the transfer is supposed to preserve the exact bytes. An edited or transcoded playback version is a different file and should normally have a different hash.
Work on a separate copy
- 1On Linux with GNU Coreutils, run the first command on the two local files. Compare the complete hash strings, not their filenames.
- 2The next command saves a record for the master. Keep that record in a trusted location.
- 3Later, run the final command in the folder containing the unchanged original filename. A mismatch means investigate the transfer or edit before replacing your master.
sha256sum original.mp4 copy.mp4
sha256sum original.mp4 > original.mp4.sha256
sha256sum -c original.mp4.sha256Check before sharing
On macOS, use shasum -a 256; PowerShell provides Get-FileHash -Algorithm SHA256. A matching hash supports byte identity but does not prove authorship, safety or rights. Keep local originals independently of Dembed; do not compare an intentionally re-encoded player version as though it were the original.
Technical reference
https://www.gnu.org/software/coreutils/manual/html_node/sha2-utilities.html
Frequently asked questions
Yes. The file bytes determine this hash, not the filename.