# Hash & checksum — SHA-256, SHA-512 & MD5, no upload

> Free hash tool: generate SHA-256, SHA-512, SHA-1, or MD5 digests of files and text, and verify a download's checksum by comparing against an expected value — in your browser.

Compute SHA-256, SHA-384, SHA-512, SHA-1, or MD5 digests of a file or a string, and verify a download by comparing its hash against the checksum the publisher listed. Large files are streamed on your device, so nothing is uploaded.

A hash is a fingerprint: the same input always yields the same digest, and any change flips it completely. That makes hashing the standard way to prove a downloaded ISO or release binary arrived intact, and to compare two files without opening them.

SHA-256 is the sensible default; SHA-384/512 add margin, while SHA-1 and MD5 remain here only for verifying against legacy systems that still publish them. Text hashing is handy for quick fingerprints and cache keys.

For turning a password into a stored hash use the Password hasher instead, and to encrypt the file rather than fingerprint it, use AES file encrypt.

## How to

1. **Add input.** Drop a file or type/paste text into the tool.
2. **Pick an algorithm.** Choose SHA-256 (recommended) or SHA-384/512, SHA-1, or MD5 for legacy checks.
3. **Read the digest.** The hex digest appears; copy it with one click.
4. **Verify.** Paste the expected checksum to see an instant match / no-match result.

## FAQ

### How do I check a file's SHA-256 checksum?

Drop the file, choose SHA-256, and compare the result to the value the download page published. A match means the file wasn't corrupted or altered in transit.

### Can it hash very large files?

Yes. Files are read in slices with the File API and hashed incrementally, so multi-gigabyte files work without loading the whole thing into memory at once.

### Should I still use MD5 or SHA-1?

Only for non-security checksums against systems that require them — both are broken for collision resistance. Use SHA-256 or stronger whenever integrity actually matters.

### Are my files sent anywhere to be hashed?

No. Hashing uses the browser's Web Crypto on this device; the file's contents are read locally and never transmitted.


## Related tools

- [Password hasher](https://www.safepaper.app/security/password-hash)
- [AES file encrypt](https://www.safepaper.app/security/file-encrypt)
- [JWT decoder](https://www.safepaper.app/security/jwt-decoder)
- [X.509 decoder](https://www.safepaper.app/security/x509-decoder)

---

Canonical HTML: https://www.safepaper.app/security/hash-verify
Markdown: https://www.safepaper.app/security/hash-verify.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.