Compute MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes of text or a file at once, and compare them with a published checksum.
If this tool isn’t working as expected, please take a screenshot of the error and report the problem here so we can investigate and improve it.
A hash generator that computes five digests of the same input at once: MD5, SHA-1, SHA-256, SHA-384 and SHA-512, so it serves as an MD5 hash generator and a SHA-256 generator in one. The input is either typed text, hashed as UTF-8, or a file you choose from your device.
SHA-1 to SHA-512 come from the browser's Web Crypto API; MD5, which Web Crypto doesn't offer, is computed by a built-in implementation tested against known values. Nothing is uploaded.
Paste a published checksum into the compare box and the matching algorithm is highlighted - the quick way to check a download against the value on its download page. A matching hash says the bytes are identical, not that the content is trustworthy: if someone can alter the file and the checksum together, a match proves nothing.
Type or paste text, or pick a file with Hash a file instead.
MD5, SHA-1, SHA-256, SHA-384 and SHA-512 appear together.
Paste a published checksum to see which algorithm it matches.
Use the Copy button next to the algorithm you need.
Choose the file, paste the checksum from the download page into the compare box, and see which algorithm matches. Files are read into memory, so the limit is 256 MB.
Hash both. The same digest means the same bytes, including spaces and line endings.
Hash a known string to get the digest that code under test should produce.
Some older download pages and file lists still publish MD5, which is why it's here alongside the SHA family.
Text
HelloHashes
MD5: 8b1a9953c4611296a827abf8c47804d7 (32 hex chars)
SHA-1: f7ff9e8b7bb2e09b70935a5d785e0cc5d9d0abf0 (40)
SHA-256: 185f8db32271fe25f561a6fc938b2e264306ec304eda518007d1764826381969 (64)
SHA-384: 3519fe5ad2c596efe3e276a6f351b8fc0b03db861782490d45f7598ebd0ab5fd5520ed102f38c4a5ec834e98668035fc (96)
SHA-512: 3615f80c9d293ed7402687f94b22d58e529b8cc7916f8fac7fddf7fbd5af4cf777d3d795a7a00a16bf7e7f3fb9561ee9baae480da9fe7a18769e71886b03f315 (128)Digest length depends only on the algorithm, never on the input: every MD5 is 32 hex characters and every SHA-256 is 64.
Text
"Hello" vs "hello"SHA-256
Hello → 185f8db32271fe25f561a6fc938b2e264306ec304eda518007d1764826381969
hello → 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824Changing only the capital H gives a completely different digest, which is what makes an exact match meaningful.
Text
A single spaceMD5
7215ee9c7d9dc229d2921a40e899ec5fSpaces, tabs and line breaks are hashed like any other character. Only an empty box produces no hash.
There's no key input, so keyed hashes such as HMAC-SHA256 can't be generated or checked here.
bcrypt, scrypt and Argon2 aren't available. These digests are fast by design, which is the wrong property for storing passwords.
A file is read into memory in one piece before hashing, so larger files are refused with a message. For those, use a command-line tool such as sha256sum or Get-FileHash.
All five digests are computed together, but they aren't interchangeable when someone might craft the input.
| MD5 / SHA-1 | SHA-256 / SHA-384 / SHA-512 | |
|---|---|---|
| Digest length | 128 bits (32 hex characters) / 160 bits (40) | 256 bits (64) / 384 bits (96) / 512 bits (128) |
| Collision attacks | Practical ones have been demonstrated for both | None known |
| Fine for | Matching a published checksum | Anything where an attacker could choose the input |
Which should you use?
Use SHA-256 by default. Reach for MD5 or SHA-1 only because a system or checksum list you're matching uses them.
These cover reversing hashes, password storage, and why a hash can differ from the one your terminal prints.
Type or paste text, or choose a file with Hash a file instead, and the MD5 digest appears with the four SHA digests. To check one, paste the expected MD5 into the compare box and the MD5 row lights up on a match. MD5 is fine for catching accidental corruption or matching an older checksum list, but it isn't collision-resistant, so where someone could craft the input, use SHA-256.
None of these. MD5 and the SHA family are fast on purpose, so an attacker holding a stolen hash can try enormous numbers of guesses per second. Passwords should be stored with a slow, salted algorithm built for the job - bcrypt, scrypt or Argon2 - which this page doesn't offer.
No. A hash isn't encrypted, so there is nothing to decrypt: it's a one-way fingerprint. Sites that claim to reverse MD5 only look the digest up in tables of known inputs, which works for short or common values and nothing else.
Choose Hash a file instead, pick the file, and paste the checksum from the download page into the compare box. If one of the algorithms matches, it lights up. The file is read in your browser and is limited to 256 MB; for larger files use sha256sum on Linux and macOS or Get-FileHash in PowerShell.
Usually because the input isn't byte-for-byte the same. Text typed here is hashed exactly as you see it, with no trailing newline, while echo hello | sha256sum hashes the word plus a newline. Windows line endings (CRLF instead of LF) and a hidden byte-order mark change the digest too.
Leave your email so we can prioritize similar tools and updates.