Skip to content
Outrich Data

Glossary

Checksum manifest

A checksum manifest is a list of every file in a dataset delivery with its name, size and cryptographic hash, usually SHA-256. The recipient recomputes each hash after transfer and compares it with the list. Matching values show the files arrived complete and unaltered, and identify exactly what was delivered.

A hash function reads a file and produces a short fixed-length string. SHA-256 produces 64 hexadecimal characters. Changing a single byte of the file produces a completely different string, so a matching hash is strong evidence that two files are identical. The seller builds the manifest before sending the data and transmits it separately. The buyer runs the same calculation on what it received.

The manifest serves two purposes. The first is integrity. Large transfers fail in quiet ways, and a hash mismatch points to the exact file that needs to be sent again. The second is identity. Attached to the license and the closing statement, the manifest fixes which files the deal covers. If a dispute arises later about what was delivered, either party can hash its copy and compare. A manifest proves nothing about the content of the files, only that they are the same files. The free tools on this site build and verify manifests in the browser without uploading data.

A manifest is usually a plain text or CSV file, so it can be read without special software. Each refresh or corrected delivery gets its own manifest, and older manifests are kept so that every version can be traced.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc