How to use the hash generator
- Choose Text or File mode.
- Type the text, or pick a file to hash.
- Select SHA-1, SHA-256, SHA-384 or SHA-512.
- Copy the hex digest and compare it with the published checksum.
A cryptographic hash turns any input into a fixed-length fingerprint. Two properties matter in practice: it is infeasible to produce two inputs with the same digest, and any change to the input — a single byte — produces a completely different output. That is what makes checksums a reliable way to confirm a download arrived intact and unmodified.
SHA-256 is the default choice for file verification and modern signatures. SHA-1 still appears in old certificates and git object IDs, but it is broken for collision resistance and must not be used for new security work. If you need a password hash, none of these are appropriate: passwords need a deliberately slow function such as Argon2id, bcrypt or scrypt.
Hashes are not encryption
You cannot reverse a hash to recover the input. "Cracking" a hash means guessing candidates and hashing them — which is why unsalted SHA-256 of a common password is recovered in seconds, and why services that leak such hashes are treated as a full password disclosure.
Verifying a large download locally is also faster and safer than trusting a mirror: compute the digest here and compare character by character, or sha256sum on the command line.
Frequently asked questions
Can I hash a large file?
Yes, the file is read as an ArrayBuffer in memory and hashed locally. A few hundred megabytes is comfortable on a normal machine.
Why is MD5 not offered?
MD5 is broken for collisions and unsuitable for integrity or security. SHA-256 is the correct replacement, and both digests have the same practical cost.
Is the digest the same as a digital signature?
No. A signature encrypts a hash with a private key; a hash alone proves nothing about who produced the file.
Does line ending matter?
Yes — text hashed with Windows CRLF differs from the same text with Unix LF. Compare like with like.