There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check. See how it stays private.
How to hash a file or text
- Add input. Drop a file or type/paste text into the tool.
- Pick an algorithm. Choose SHA-256 (recommended) or SHA-384/512, SHA-1, or MD5 for legacy checks.
- Read the digest. The hex digest appears; copy it with one click.
- Verify. Paste the expected checksum to see an instant match / no-match result.
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.
Frequently asked questions
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.