Checksums and verification

Every delivered file has a SHA-256 hash, recorded twice: in its manifest record (sha256) and in the delivery's SHA256SUMS file. The same hashes are in the hash log written inside the owner's environment, so a match proves the file is the one that left it.

Check one file here

Drop a file and paste the hash from its manifest record. The hash is computed in your browser; nothing is uploaded.

verify a fileruns in your browser · nothing is uploaded

Drop a delivered file, or choose one

sha256 from the manifest

computed—

Check a whole delivery

From the delivery's root folder:

# Linux
sha256sum -c SHA256SUMS

# macOS
shasum -a 256 -c SHA256SUMS

Every line should end in OK. To check against the manifest instead:

jq -r '"\(.sha256)  audio/\(.record_id).flac"' manifest.jsonl | sha256sum -c -

If a hash doesn't match

Download the file again. If it still differs, tell us with the record_id: it's re-delivered and the mismatch is investigated against the hash log.