A hash generator turns text or a file into a short, fixed-length fingerprint called a digest. This hash generator covers the checksums people ask for most, from MD5 and SHA-1 through SHA-256, SHA-384 and SHA-512, to SHA-3, RIPEMD-160, Whirlpool, BLAKE2b, BLAKE3, CRC32 and NTLM. It also makes keyed HMAC values and the slow password hashes bcrypt and Argon2id. Everything runs in your browser, so your text, files and keys are never uploaded.
How to use the hash generator
- Pick an algorithm from the list. If you only need a checksum for a download, choose the one the publisher lists, usually SHA-256 or SHA-512.
- Choose Text or File, then type the text or select the file.
- Add the extra setting if the algorithm needs one: a secret key for HMAC, a cost for bcrypt, or passes, parallelism and memory for Argon2id.
- Paste an expected hash if you want a match check, then press Generate hash.
- Copy the result as hexadecimal, or use the Base64 version shown below it.
What a hash does
A hash function takes data of any size and returns a value of fixed size. The same input always gives the same output, but a one-character change gives an unrelated result, and you cannot work backwards from the digest to the original data. FIPS 180-4 describes the hash algorithms that detect whether a message has changed. [1] That is why a published checksum lets you confirm that your copy of a file is identical to the original.
SHA-2, SHA-3 and the older algorithms
SHA-256, SHA-384 and SHA-512 belong to the SHA-2 family, and SHA-224 is its shorter sibling. The SHA-3 family was standardized later in FIPS 202. It is built on the Keccak algorithm and defines SHA3-224, SHA3-256, SHA3-384 and SHA3-512. [2] This tool offers SHA3-256 and SHA3-512. MD5 gives a 128-bit digest and was written up in RFC 1321 for digital signatures. [6] Today MD5 and SHA-1 are fine for spotting accidental damage or matching a legacy checksum, but you should not rely on them where someone might deliberately forge a file.
| Algorithm | Digest size | Typical use |
|---|---|---|
| MD5 | 128 bits | Legacy checksums, cache keys |
| SHA-1 | 160 bits | Legacy checksums, Git object names |
| SHA-256 | 256 bits | Download checksums, certificates |
| SHA-512 | 512 bits | Download checksums, signatures |
| SHA3-256 | 256 bits | Modern alternative to SHA-2 |
| CRC32 | 32 bits | Error detection in archives, not security |
HMAC: a hash with a secret key
HMAC mixes a secret key into a hash so that only someone with the key can produce or check the result. RFC 2104 defines it as the hash of the key XORed with one padding value, followed by the hash of the key XORed with another padding value and the message. [3] If the key is longer than the hash block it is hashed first, and a shorter key is padded with zeros. Choose one of the HMAC-SHA options, type your key, and the page returns the keyed digest. HMAC is used to sign webhooks and API requests.
Password hashes: bcrypt and Argon2id
Fast hashes are the wrong tool for storing passwords, because an attacker can try billions of guesses per second. bcrypt was designed by Niels Provos and David Mazières and is based on the Blowfish cipher. Its cost factor is the base-2 logarithm of the iteration count, so cost 12 means 4,096 iterations. It uses a 16-byte salt, writes its output as a string such as $2a$12$ followed by the salt and hash, and many implementations ignore anything past 72 bytes of password. [5]
Argon2id is the variant of Argon2 that RFC 9106 says every implementation must support. You set the memory in kibibytes, the number of passes and the parallelism, and the RFC suggests a salt of 16 bytes. [4] Its second recommended option, for memory-limited systems, is 3 passes, 4 lanes and 64 MiB, which are the defaults here. Because a random salt is added each time, the same password produces a different string on every run. To check a password, paste an existing bcrypt or Argon2id string into the compare box and press the button: the page answers match or different.
Hash generator examples
The SHA-256 of the three letters abc begins with ba7816bf and ends with f20015ad. The MD5 of abc is 900150983cd24fb0d6963f7d28e17f72, and the CRC32 of 123456789 is cbf43926. The NTLM hash of the word password is 8846F7EAEE8FB117AD06BDD830B7586C, which this page works out as MD4 over the text written in 16-bit little-endian characters. Capital letters, spaces and line endings all change the result.
Verify a download
Publishers often list a checksum beside a download. Choose File, pick the downloaded file, paste the published value into the compare box and generate. A match means your copy is identical. A mismatch means the download is incomplete or has been changed, so delete it and fetch it again from the official site. The checksum is only as trustworthy as the place you got it from.
Common mistakes
- Hashing the wrong text. A trailing space or a different line ending gives another digest.
- Mixing up algorithms. Compare like with like: a 64-character value is probably SHA-256 or SHA3-256.
- Using MD5 or SHA-1 for security. Pick SHA-256 or better.
- Using SHA-256 for passwords. Use bcrypt or Argon2id instead.
Privacy
The page hashes data with code that runs on your device. Nothing is sent to a server, which makes it suitable for confidential documents. Very large files need to be read into memory, so a big file may take a moment on an older phone.
What next
Use this often? Add Hash to your Home screen.
Frequently asked questions
What is a hash generator?
A hash generator turns text or a file into a fixed-length digest. The same input always gives the same digest, a tiny change gives a very different one, and the original cannot be recovered from it.
Which hash generator algorithm should I choose?
Use the one the publisher lists for a download. For new work, SHA-256 or SHA-512 are good general choices. Use bcrypt or Argon2id for passwords, and HMAC when a secret key is involved.
Is MD5 or SHA-1 still safe?
They are fine for catching accidental corruption or matching an old checksum, but not where an attacker could forge a file or a signature. Use SHA-256 or better for security.
Why does bcrypt give a different hash each time?
bcrypt and Argon2id add a random salt to every hash. To check a password, paste an existing hash into the compare box and the page verifies it against the text.
Are my files uploaded to hash them?
No. The hashing runs in your browser and nothing leaves your device. Files up to 512 MB can be hashed.
Sources
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.