CodeKitHubWhat Is This Tool?
A hash function takes any input and turns it into a fixed-length string of hex characters called a digest. The same input always produces the same digest, and changing even one character produces a completely different result. This tool runs five widely used algorithms — MD5, SHA-1, SHA-256, SHA-384 and SHA-512 — on the same input so you can compare them or grab whichever one you need.
These digests are one-way: it is mathematically infeasible to reconstruct the original text from a hash. What people call "decrypting" a hash online is actually a lookup — the site is just checking whether your hash matches one of billions of precomputed hashes of common passwords and phrases. If your input isn't in their table, it can't be found, because there is no reverse function to run.
Why Use It?
- Compute five hash algorithms at once instead of switching between tools.
- Compare an MD5, SHA-1 or SHA-256 checksum against a published value to verify integrity.
- Generate stronger SHA-384 or SHA-512 digests for applications that require longer output.
- Build deterministic IDs or cache keys from arbitrary text.
- 100% local: your input never leaves the browser, so it's safe for sensitive text.
How to Use
- Type or paste your text into the input box.
- Click "Generate".
- Read the MD5, SHA-1, SHA-256, SHA-384 and SHA-512 results (check "Uppercase output" if your target system expects capital letters).
- Click "Copy" next to whichever hash you need.
Example
Input
helloOutput
MD5: 5d41402abc4b2a76b9719d911017c592
SHA-1: aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
SHA-256: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824Hashes are deterministic: "hello" produces these exact values on every tool, every time.
Only need MD5?
If you just need a quick MD5 checksum and don't need the other four algorithms cluttering the page, our focused single-algorithm tool is faster to scan.
Comparing the five algorithms
All five are one-way hash functions, but they differ in output length and security strength.
| Algorithm | Output size | Security status | Typical use |
|---|---|---|---|
| MD5 | 128-bit (32 hex chars) | Broken — collisions can be manufactured | Checksums, cache keys, deduplication |
| SHA-1 | 160-bit (40 hex chars) | Broken — practical collision attacks exist since 2017 | Legacy system compatibility only |
| SHA-256 | 256-bit (64 hex chars) | Secure, current industry standard | Digital signatures, TLS, blockchain, integrity checks |
| SHA-384 | 384-bit (96 hex chars) | Secure, longer output than SHA-256 | High-assurance signatures, some TLS/PKI setups |
| SHA-512 | 512-bit (128 hex chars) | Secure, largest output here | Applications requiring maximum digest length |
Common use cases
- Verifying a downloaded file matches the publisher's published checksum before running it.
- Generating deterministic cache keys or IDs from arbitrary text.
- Checking whether two documents or records are byte-identical without comparing them directly.
- Producing a stronger digest (SHA-384/SHA-512) when an application specifically calls for it.
Frequently Asked Questions
Can I decrypt a hash back into the original text?
No. Hashing is designed to be one-way — there is no key and no mathematical operation that reverses a digest back into its input. Sites that claim to "decrypt MD5" or "decrypt SHA-256" are really just searching a giant precomputed table of common inputs and their hashes. If your original text was unusual enough not to be in that table, it simply cannot be recovered, by anyone.
Then how do sites check my password without storing it in plain text?
They store the hash of your password, not the password itself. When you log in, they hash what you typed and compare the two hashes. If they match, the passwords matched too — without the site ever needing to store or "decrypt" your actual password.
Which algorithm should I use?
For security-sensitive purposes (signatures, certificates, verifying downloads), use SHA-256 or higher — MD5 and SHA-1 are both cryptographically broken and should not be trusted for security. For non-security purposes like checksums, cache keys or deduplication, MD5 is still fine and faster to compute.
Why do I get a different hash than another tool for the same text?
Usually an invisible difference: a trailing newline or space, different line endings (\r\n vs \n), or a different text encoding. Byte-identical input always produces an identical hash on every correct implementation.
Is my text sent to a server?
No. MD5 is computed with JavaScript running in your browser, and SHA-1/SHA-256/SHA-384/SHA-512 use your browser's built-in Web Crypto API. Nothing leaves your device.