Verify downloads against Hugging Face checksums

BitTorrent already verifies every piece against the torrent's own hashes — a completed download matches its infohash by construction. The remaining question is whether that infohash corresponds to the official files. Here's how to close the loop.

1. Get the official checksums

Every file on a Hugging Face repo has a SHA-256 hash. On the model page, open the Files tab, click a file, and copy its SHA-256 — or fetch them all:

huggingface-cli download <repo> --dry-run
# or read the LFS pointers directly:
curl -s https://huggingface.co/<repo>/raw/main/<file> | grep sha256

2. Hash your downloaded files

sha256sum model-Q5_K_M.gguf

On large files this takes a while — pv file | sha256sum shows progress.

3. Compare

If the hashes match, your copy is bit-for-bit identical to the official release, regardless of where the bytes came from. If they don't match, delete the files and [report the listing](/browse/) — every torrent page has a report button.

Notes for GGUF users

Quantized GGUFs are usually produced by third parties (or by you). A GGUF won't match the original repo's safetensors hashes — compare against the checksum published by whoever produced that specific quant, which is linked from each listing here whenever available.