Hash Generator
Compute MD5, SHA-1, SHA-256, and SHA-512 hashes of any text in your browser. Lowercase or uppercase hex, with one-click copy.
Processed locally in your browser — nothing is uploaded.
Hash Generator
0 characters
MD5
Digest appears here…
SHA-1
Digest appears here…
SHA-256
Digest appears here…
SHA-512
Digest appears here…
MD5 and SHA-1 are broken for security purposes — use them for checksums and cache keys only, and prefer SHA-256 or SHA-512 for anything security-sensitive.
About Hash Generator
Type or paste text and get its MD5, SHA-1, SHA-256, and SHA-512 digests instantly. The SHA family uses the browser's native Web Crypto implementation; MD5 (which Web Crypto dropped) is computed by a built-in RFC 1321 implementation. Hashing runs over the UTF-8 bytes of your text, so results match `echo -n "text" | md5sum` and friends.
Common uses
- Verify a checksum published alongside a download
- Generate a cache key or ETag value for testing
- Compare two blobs of text without eyeballing them
Example
Input
abc
Output
MD5: 900150983cd24fb0d6963f7d28e17f72
Limitations
- MD5 and SHA-1 are cryptographically broken — never use them for passwords or signatures
- This hashes text (UTF-8); hashing arbitrary binary files isn't supported
Frequently asked questions
Is the text I hash sent to a server?
No. Digests are computed in your browser — the SHA family through the native Web Crypto API and MD5 in JavaScript — so the input never leaves your device.
Can I reverse a hash to get the original text back?
No. Hashes are one-way functions with no decryption key. Attackers can still recover short or common inputs by hashing guesses and comparing (rainbow tables), which is why passwords must be salted and hashed with a dedicated algorithm, not plain MD5 or SHA-256.
Why doesn't my hash match the md5sum output on my machine?
Almost always a trailing newline: plain echo appends \n, which changes the digest. This tool hashes exactly the UTF-8 bytes of your text, so it matches echo -n "text" | md5sum, and pasted invisible whitespace will also change the result.
Why is MD5 considered broken?
Practical collision attacks — two different inputs producing the same digest — have existed since 2004 and now run in seconds, and SHA-1 fell in 2017. Both remain fine for non-security uses like cache keys and duplicate detection, but use SHA-256 or SHA-512 for anything an attacker could tamper with.
Why does every input produce a hash of the same length?
Each algorithm has a fixed digest size regardless of input length: MD5 is 128 bits (32 hex characters), SHA-1 is 160, SHA-256 is 256 (64 hex), and SHA-512 is 512 (128 hex). A one-letter input and a novel both map to the same-sized digest.