Four fingerprints for any text, in one click
A hash function reads any input and emits a fixed-length fingerprint — change one character and the fingerprint changes beyond recognition. That single property powers half of computing's bookkeeping: verifying a download wasn't corrupted, checking whether two records differ without comparing them byte by byte, generating cache keys and content IDs, deduplicating data. This tool computes the four canonical hashes — MD5, SHA-1, SHA-256, SHA-512 — simultaneously for any text you paste, each with its own copy button.
How to generate hashes
- Paste or type your text (full UTF-8 supported — any language).
- Click Generate hashes.
- All four digests appear as lowercase hex; copy whichever your task needs.
Choosing an algorithm in 2026
SHA-256 is the modern default — collision-resistant, universally supported, the backbone of TLS certificates and blockchain alike. SHA-512 is its bigger sibling: longer digest, comparable security family, sometimes faster on 64-bit systems; pick it when a spec demands it. SHA-1 is cryptographically broken (real-world collisions since 2017) but persists as a non-security fingerprint — Git object IDs most famously. MD5 is doubly broken yet remains everywhere as a checksum because it's fast and good enough to catch accidental corruption — which is exactly the rule of thumb: legacy compatibility and integrity-against-accidents, fine; any defence against a deliberate adversary, use SHA-256.
The password rule (read this once, remember forever)
Hashes are deterministic — the same password always produces the same hash — and that's precisely why a bare MD5/SHA of a password is not protection: attackers hold precomputed tables of billions of common passwords' hashes. Real password storage uses deliberately slow, salted algorithms (bcrypt, scrypt, Argon2) designed to make mass-guessing expensive. This tool is for checksums and fingerprints; if you're building login storage, reach for those instead. (Checking whether some string matches a hash you found in a config? Paste candidates here and compare — that's legitimate debugging.)
Practical properties worth knowing
- Deterministic: same input → same hash, forever, on every machine — that's what makes them comparable.
- Avalanche: “hello” vs “Hello” share no visible similarity in output; hashes prove difference, not closeness.
- One-way: you cannot compute the input from the hash (only guess-and-check).
- Exact-input dependent: a trailing space or different line ending changes everything — the #1 cause of “hashes don't match” confusion.
Everything computes locally — hashing a secret here doesn't transmit it anywhere, which is more than most online hash sites can say.
Quick reference
| Property | Detail |
|---|---|
| Algorithms | MD5, SHA-1, SHA-256, SHA-512 — all at once |
| Output | Lowercase hex, copy button per digest |
| Unicode | UTF-8 — all languages hash correctly |
| Modern default | SHA-256 |
| MD5/SHA-1 status | Broken for security; fine as checksums |
| Passwords | Use bcrypt/Argon2 — never bare hashes |
| Processing | 100% in-browser — secrets stay local |
Frequently asked questions
Why don't my hashes match the other tool's output?
The inputs differ invisibly — a trailing space, a final newline, or Windows (\r\n) vs Unix (\n) line endings. Hashes change completely on any byte difference. Trim whitespace and normalise line endings, then compare again.
Can I reverse a hash to find the original text?
Not mathematically — hashing is one-way. Attackers “reverse” weak-password hashes only by hashing billions of guesses and comparing. That asymmetry is why hashes verify integrity but don't store secrets safely on their own.
Is MD5 still okay to use?
For detecting accidental corruption (download checksums, cache keys, dedupe), yes — it's fast and ubiquitous. For anything facing a deliberate attacker (signatures, passwords, certificates), it's been broken for two decades; use SHA-256.
Which algorithm do I need for a file checksum someone published?
Match theirs — checksums only verify if computed with the same algorithm. Published as “sha256sum”? Use SHA-256. Note this tool hashes pasted text; identical text yields identical hashes everywhere.