File Hash Generator
Compute SHA-256, SHA-384, SHA-512 and CRC32 checksums.
Algorithms
SHA-256 and CRC32 stream in chunks, so they handle files larger than memory.
About File Hash Generator
Generate checksums for any file without sending it anywhere. SHA-256 and CRC32 read the file in 8 MB chunks, so multi-gigabyte files work; SHA-384 and SHA-512 use the browser’s Web Crypto implementation and need the whole file in memory. Paste an expected hash to verify a download in one step.
A hash is a fingerprint: read every byte, produce a short string, and change one byte anywhere to change the string completely.
SHA-256, SHA-384, SHA-512 and CRC32 for any file.
- Processed on your deviceEverything you open or type here is handled by this page and never uploaded anywhere.
- No queue, no limitsNothing waits on a server, so the only limit is your own hardware.
- No account neededNo sign-up and no email address required.
How File Hash Generator works in your browser
SHA-384 and SHA-512 use the Web Crypto API — crypto.subtle.digest — which is the browser’s own audited implementation, the same primitive used for TLS. SHA-256 and CRC32 are computed by a worker in this tab that reads the file in chunks, which is what lets them handle files larger than memory. Each digest is rendered as lowercase hexadecimal.
Web Crypto is only available over HTTPS or on localhost. A hashing function delivered over a connection an attacker could modify would offer no assurance at all, and that restriction is enforced by the browser rather than by this page.
One thing to be clear about: a hash is a fingerprint, not encryption. It cannot be reversed, but identical input always produces identical output, so a plain hash of a common password is trivially reversed with a lookup table. Storing passwords needs a deliberately slow, salted algorithm such as bcrypt, scrypt or Argon2 — not any of these.
When to use it
Verifying a download against the checksum its publisher published. Confirming a file transferred or copied without corruption. Proving two files are identical when their names and dates differ. Recording a fingerprint of a document as evidence it has not been altered since.
Read more about this
Frequently asked questions
Can it handle very large files?
Yes for SHA-256 and CRC32, which read the file in chunks rather than loading it whole. SHA-384 and SHA-512 load the whole file into memory first, so a very large file can fail with those two.
How do I verify a download?
Paste the hash published by whoever provided the file. A match confirms the bytes are identical; a mismatch means the file is corrupt or has been altered.
Is the hashing done in the browser?
Yes, using the browser's native Web Crypto implementation for SHA-384 and SHA-512 and a background worker in this tab for SHA-256 and CRC32, so the file is never sent anywhere to be checksummed.