Pagan File Hash Checker

Verify every single byte.

Calculate checksums, compare two files or verify a published hash. Large files are read in small chunks inside a background worker and are never uploaded.

What this proves — and what it does not

A strong matching hash proves identical bytes, not a trustworthy file.

SHA-256, SHA-384 and SHA-512 are useful for integrity checks. A match means the file bytes match the expected digest. It does not prove that the publisher is trustworthy, that the file is malware-free or that the expected hash came from a legitimate source.

Local file readingYour file stays on this device. It is read through the browser File API.

Lazy hashing engineHash-WASM is downloaded only when calculation starts. The CDN receives a script request, never the selected file.

Chunked processingLarge files are processed piece by piece instead of being loaded into memory all at once.

Legacy warningMD5 and SHA-1 remain available for compatibility, but should not be trusted against deliberate collisions.

Checksum workspace

Choose what you need to prove.

Drop files here or choose up to 50 files Any file type · processed sequentially to protect memory

Checksum guide

Small fingerprints, precise meanings.

What does a matching SHA-256 prove?

It provides extremely strong evidence that both inputs contain identical bytes. It does not independently prove who created the file or whether its content is safe.

Why are MD5 and SHA-1 marked as legacy?

They have known collision weaknesses and should not be used where a malicious party could deliberately create two different files with the same digest. They remain useful for matching old published checksums and detecting ordinary corruption.

Does Pagan Earth receive the file?

No. The browser reads local file chunks and sends them to a Web Worker on the same page. The optional hashing library request downloads code only; file bytes are never included.

Can I hash a very large file?

Yes, within browser and device limits. The tool reads 8 MiB chunks sequentially, avoiding the full-file memory requirement of the native Web Crypto digest API.