Hash Generator (All)

Hashes one piece of text with every common algorithm at once — MD5, SHA-1, SHA-256, SHA-384, SHA-512 — so you can compare a checksum without having to know in advance which one produced it. Digest length is usually the giveaway.

Live demo · real result from this tool
Output

Table

AlgorithmBitsDigest
MD51289e107d9d372bb6826bd81d3542a419d6
SHA-11602fd4e1c67a2d28fced849ee1bb76e7391b93eb12
SHA-224224730e109bd7a8a32b1cb9d9a09aa2325d2430587ddbc0c38bad911525
SHA-256256d7a8fbb307d7809469ca9abcb0082e4f8d5651e46d3cdb762d02d0bf37c9e592
SHA-384384ca737f1014a48f4c0b6dd43cb177b0afd9e5169367544c494011e3317dbf9a509cb1e5dc1e85a941bbee3d7f2afbc9b1
SHA-51251207e547d9586f6a73f73fbac0435ed76951218fb7d0c8d788a309d785436bbb642e93a252a954f23912547d1e8a3b5ed6e1bfd7097821233fa0538f3db854fee6
SHA3-25625669070dda01975c8c120c3aada1b282394e7f032fa9cf32f4cb2259a0897dfc04
SHA3-51251201dedd5de4ef14642445ba5f5b97c15e47b9ad931326e4b0727cd94cefc44fff23f07bf543139939b49128caf436dc1bdee54fcb24023a08d9403f9b4bf0d450
Keccak-2562564d741b6f1eb29cb2a9b9911c82f56fa8d73b04959d3d9d222895df6c0b28aa15
RIPEMD-16016037f332f68db77bd9d7edd4969571ad671cf9dd3b
BLAKE2b-512512a8add4bdddfd93e4877d2746e62817b116364a1fa7bc148d95090bc7333b3673f82401cf7aa2e4cb1ecd90296e3f14cb5413f8ed77be73045b13914cdcd6a918
BLAKE32562f1514181aadccd913abd94cfa592701a5686ab23f8df1dff1b74710febc6d4a
CRC-3232414fa339

13 rows — scroll inside the table, or download the CSV.

Hashed 43 bytes of UTF-8 text. A trailing space or newline changes every digest.

Processed on your device — nothing is uploaded.

How to use Hash Generator (All)

  1. Paste the text you want to fingerprint.
  2. All digests compute at once as you type.
  3. Copy the one you need, or match an unknown checksum by its length.
  4. Input is encoded as UTF-8 before hashing, which is what other tools and libraries default to.
  5. SHA algorithms use the browser’s Web Crypto implementation; MD5 is computed in JavaScript since Web Crypto deliberately omits it.
  6. Nothing is uploaded — the text stays in the page.

Identifying a hash by its length

Hex digests have a fixed width per algorithm, which is the quickest way to identify an unlabelled checksum. 32 characters is MD5. 40 is SHA-1. 56 is SHA-224, 64 is SHA-256, 96 is SHA-384 and 128 is SHA-512. If it is 60 characters and starts with $2a$ or $2b$ it is bcrypt, which is a password hash with its cost and salt embedded and cannot be reproduced here. Anything ending in = is probably Base64 rather than hex, so decode it first.

Which of these you should actually use

SHA-256 for anything new. SHA-512 where you want a larger margin, and it is often faster on 64-bit hardware. SHA-1 only to verify something legacy — it has practical collisions and browsers and certificate authorities dropped it years ago. MD5 only for non-adversarial checksums: cache keys, deduplication, spotting accidental corruption. For passwords, none of these: they are all far too fast, and you want Argon2id, scrypt or bcrypt.

Comparing two digests properly

Compare the whole string, case-insensitively — hex is conventionally lowercase but some tools print uppercase, and both are the same value. A digest matching on the first eight characters proves nothing. Also check you are hashing the same thing: a published checksum covers a file’s raw bytes, while this tool hashes the text you paste, and a trailing newline is enough to change every digit of the result.

Frequently asked questions

What is a cryptographic hash?
A one-way function that maps arbitrary data to a fixed-size digest. Changing one character produces a completely different hash.
Which hash should I use?
SHA-256 is the usual choice for checksums and signatures, and SHA-512, SHA-3 and BLAKE3 are also sound. MD5, SHA-1 and CRC32 still catch accidental corruption, but should not be trusted where someone could deliberately forge a match.
Are these hashes reversible?
No — hash functions are one-way. You cannot recover the input from the hash.
How can I tell which algorithm produced a hash?
By length: 32 hex characters is MD5, 40 is SHA-1, 64 is SHA-256, 128 is SHA-512. Hash your known input here and compare against all of them at once — whichever matches identifies the algorithm.
Which hash should I use for passwords?
None of these. Every algorithm here is designed to be fast, which is exactly wrong for passwords — a GPU tries billions per second. Use Argon2id, scrypt or bcrypt, which are deliberately slow, salted and memory-hard.
Why does my hash not match the one on the download page?
The download's checksum covers the file's bytes, not text you copied out of it, and a trailing newline alone changes the entire digest. Use a file-checksum tool for files, and verify the checksum came from a source you trust independently of the download itself.

Written by the ToolsRift team · Last updated

Pages are drafted with AI assistance and checked by automated tests. How we write and check pages.

Was this tool useful?

Report a problem

Start typing to search every tool.

↑ ↓ to moveEnter to openEsc to close