Reference Glossary
Checksum
A short fixed-length value computed from a file's contents, using an algorithm like MD5 or SHA-256, used to confirm a file wasn't corrupted or altered during transfer or storage.
Why it matters in a DAM
DAM systems move large binary files — multi-gigabyte video masters, RAW photography — across networks, storage tiers, and cloud regions constantly, and a checksum computed at ingest and re-checked after upload, migration, or transcoding confirms the bytes arrived intact without anyone having to open and visually inspect the file. It's also the mechanism many DAM dedup engines use to detect that two differently named uploads are actually the identical file.
A worked example
Common mistake
Teams treat a matching checksum as proof two files are "the same asset" for licensing or rights-tracking purposes, when it only proves the bytes are identical — a re-exported file with one pixel or one metadata field changed produces a completely different checksum even though it's visually and editorially the same photo, so checksum-based dedup misses near-duplicates that a perceptual or visual-similarity check would catch.
A checksum is a fixed-length digest computed by running a file’s full contents through a hashing algorithm — commonly MD5 for speed or SHA-256 for stronger collision resistance. Any change to the underlying bytes, down to a single flipped bit, produces a completely different checksum, which is what makes it useful as an integrity check: compute it once at upload, store it, and recompute it later to confirm the file is still exactly what was originally stored.
DAM platforms rely on this at several points in an asset’s lifecycle: verifying an upload completed without network corruption, confirming a file survived a storage migration or cloud-region move unchanged, and detecting exact-duplicate uploads so the same master isn’t stored twice under different filenames. For archival masters especially, a stored checksum gives a way to periodically audit that cold storage hasn’t silently degraded the file — a real risk over years-long retention periods.
Checksums verify integrity, not similarity or authenticity. Two genuinely different files that happen to depict the same subject will never match, and a checksum match says nothing about who is authorized to use the file — it only confirms the content is byte-for-byte what it was when the checksum was first recorded.
Frequently asked
What is a checksum?
A short fixed-length value computed from a file's contents using an algorithm like MD5 or SHA-256, used to confirm a file wasn't corrupted or altered during transfer or storage.
Where does a DAM use checksums?
At upload to confirm no network corruption occurred, after a storage migration or cloud-region move, and to detect exact-duplicate uploads so the same master isn't stored twice under different filenames.
Does a matching checksum mean two files are the "same asset" for licensing purposes?
No. It only proves the bytes are identical. A re-exported file with one pixel or one metadata field changed produces a completely different checksum even though it's visually and editorially the same photo.
What's the difference between MD5 and SHA-256 checksums?
MD5 is faster to compute; SHA-256, standardized by NIST, offers stronger collision resistance. Both flag any change to the underlying bytes, down to a single flipped bit.
Can checksum-based dedup catch a resized or recompressed re-export?
No. Checksum matching only catches byte-identical files; catching near-duplicates requires a perceptual or visual-similarity check layered on top.
Why are checksums useful for archival masters specifically?
A stored checksum lets a DAM periodically audit that cold storage hasn't silently degraded the file — a real risk over years-long retention periods.
Sources
- SHA-256 is a secure hash algorithm standardized by NIST that produces a 256-bit condensed digest of a message, and any change to the input results, with very high probability, in a different digest. checked 2026-08-07 — NIST FIPS 180-4 — Secure Hash Standard (SHS)