The page does not reverse a digest. People search “md5 decrypt” because they hope a hash is a locked box. It is not. MD5 throws information away. This tool only runs the hash forward, and it says so in the result.
How to use
- Type the text you want to hash. An empty box is refused.
- Press Hash and copy the 32 hex characters, not the label.
- Reset restores hello so you can check the well-known digest.
Formula / how it works
What the digest is. The text is encoded as UTF-8 bytes, padded the way RFC 1321 specifies, and run through the four rounds. The result is 128 bits, written as 32 lowercase hex digits. “hello” is five characters and hashes to 5d41402abc4b2a76b9719d911017c592. “world” hashes to 7d793037a0760186574b0282f2f435e7. A capital letter, a space or a different encoding would change the digest. The character count under the digest is the number of Unicode characters you typed, which can differ from the number of UTF-8 bytes if you typed an accent or an emoji. The hash uses the bytes.
What it will not do. It will not search a list of common passwords, and it will not “look up” a hash. If you paste a 32-character hex string, the page hashes those characters as text. It does not treat them as a digest to invert. There is no second mode. MD5 is also a poor password store: collisions have been practical for years, and a fast hash is easy to guess against. Use it for a checksum of a short note, or to match an old system that already speaks MD5. Do not use it to store a new password. The SHA-256 tool is the stronger neighbour on this site. The base64 encoder is a reversible encoding, which MD5 is not. If you can get the original back, it was not a hash.
Checks. The hello digest above is the standard test. If your other tool prints something else for the letters h-e-l-l-o and nothing else, one of the tools is hashing different bytes, often a newline you did not notice or a UTF-16 encoding. This page uses UTF-8 without a newline unless you typed one.
Limits. Twenty thousand characters. Lowercase hex only. No file upload. A file checksum is a different job, because a file’s bytes include structure this text box does not have. Paste the text you mean, not a path to a file.
The result line. Copy the hex. The sentences under it are the warning, and they belong on the page rather than in your checksum field.
A one-character change. Hello and hello differ by one bit in a letter and by the entire digest. That is the property you are checking when you compare two notes. It is also why “almost the same” is not a useful thing to say about two digests. Either they match or you have different bytes. There is no partial credit in the hex
Worked examples
The standard hello digest
Inputs: Text: hello
Leave the text as hello and press Hash. The digest is 32 lowercase hex characters.
Result: MD5: 5d41402abc4b2a76b9719d911017c592
Characters: 5
MD5 is a one-way hash. This page does not reverse a hash back into the text that made it.
A different five-letter word
Inputs: Text: world
Change the text to world and press Hash. The digest is not the hello digest.
Result: MD5: 7d793037a0760186574b0282f2f435e7
Characters: 5
MD5 is a one-way hash. This page does not reverse a hash back into the text that made it.
Use cases
- Checking a known test vector before you trust another implementation.
- A checksum of a short note that an old system still expects as MD5.
- Showing a student that a one-letter change moves the whole digest.
- Refusing a “decrypt” request by having no such control.
Tips & limitations
- Do not store new passwords with MD5.
- Watch for a hidden newline. It changes the digest.
- Copy the hex, not the warning sentence.
- Use SHA-256 when you are choosing a hash rather than matching an old one.
FAQ
Can this decrypt an MD5 hash?
No. The hash throws information away. Pasting a digest hashes those characters. It does not recover an earlier text.
Why is hello a known value?
It is a standard test vector. If you get a different digest, the bytes being hashed are not the five letters alone.
Does capitalisation matter?
Yes. Hello and hello are different byte strings and different digests.
Is MD5 safe for passwords?
No. It is fast and collisions are practical. Do not use it for new password storage.
What encoding is hashed?
UTF-8, with no extra newline unless you typed one.
Is the text uploaded?
No. The digest is computed in the browser.
Runs entirely in your browser; nothing is uploaded. Check the output before you rely on it in production code, data or security decisions.