Hash Generator
Type or paste text to get its MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes. Everything runs in your browser, so your text never leaves your machine.
crypto.subtle API; MD5 uses a small built-in routine. Nothing is uploaded or logged.About the Hash Generator
The Hash Generator turns any text into MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes at once. Use it to create checksums, compare file or string fingerprints, generate cache keys, or check that two values match. The SHA family is computed with the browser's native crypto.subtle API, and MD5 runs through a small built-in routine. All hashing happens in your browser, so your text is never uploaded or logged.
How it works
- Type or paste your text into the input box. Hashes update as you type.
- Read the five hash values (MD5, SHA-1, SHA-256, SHA-384, SHA-512), each labeled with its bit length.
- Toggle Uppercase if you need the hex in capital letters.
- Click Copy on any row to copy that hash, or Copy all to grab every value at once.
Features
- Five algorithms at once: MD5, SHA-1, SHA-256, SHA-384, and SHA-512.
- Live updates as you type, with a character count.
- Lowercase or uppercase hex output with one toggle.
- Per-row Copy buttons plus a Copy all button.
- Runs fully in your browser using crypto.subtle for SHA, so text stays private.
Frequently asked questions
Is my text sent to a server?
No. Hashing runs entirely in your browser. The SHA values use the native crypto.subtle API and MD5 uses a built-in JavaScript routine. Nothing is uploaded or stored.
Why does the tool include MD5 if MD5 is not secure?
MD5 is broken for security uses such as passwords or signatures, but it is still common for checksums, cache keys, and matching values in legacy systems. It is provided for those cases, not for protecting secrets.
Which algorithm should I use?
For security, use SHA-256 or stronger. SHA-256 is a good default. Use SHA-384 or SHA-512 when you want a longer digest. Avoid MD5 and SHA-1 for anything where collisions matter, since both are considered weak.
How is the text encoded before hashing?
The text is encoded as UTF-8 bytes, then hashed. This means non-ASCII characters such as accents or emoji are handled by their UTF-8 byte sequence, which is the standard most other tools use.
Why are my hashes different from another tool?
Common reasons are a trailing newline or extra spaces in the input, a different text encoding, or uppercase versus lowercase hex. Check that the exact same bytes are being hashed and that the case setting matches.