Text hash (MD5 / SHA)
Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 locally
Enter text to calculate several digests automatically. Check trailing newlines and UTF-8 byte counts before comparing; SHA needs browser support.
| MD5 | ||
|---|---|---|
| SHA-1 | ||
| SHA-256 | ||
| SHA-384 | ||
| SHA-512 |
Example
Input
abc
Example result
SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
Do not append a newline. This example contains three UTF-8 bytes.
Technical details & limits
Matching digests require the same algorithm and identical bytes, including spaces, newlines, BOM and Unicode composition. SHA uses Web Crypto and requires HTTPS or localhost. MD5 and SHA-1 have collision weaknesses. Unsalted fast hashes are unsuitable for password storage; HMAC is not implemented here.
About this tool
Compute MD5, SHA-1, SHA-256, SHA-384 and SHA-512 digests of UTF-8 text, with the byte count shown. Check text integrity and implementation test vectors locally, without reverse lookup.
Use cases
- Verify a downloaded file against the published hash.
- Produce a SHA-256 digest for signing an API request.
- Confirm two rows in different systems really are the same content by comparing hashes.
How to use
- Paste the text you want hashed.
- MD5 and the SHA family are computed together; there is nothing to pick.
- Copy a digest with the button on its row.
Input & output
- Input
- Any UTF-8 text.
- Output
- Five hex-encoded digests, one per algorithm, each copyable.
Notes
MD5 and SHA-1 are no longer safe for signatures or integrity against motivated adversaries. Ordinary use — dedupe, cache keys — is still fine. Never store raw passwords: use bcrypt or argon2 with a salt.
FAQ
- How long are SHA-256 and MD5 digests in hexadecimal?
- A SHA-256 digest contains 256 bits and 64 hexadecimal characters, while MD5 contains 128 bits and 32 hexadecimal characters. The different lengths come from the algorithms, not from the length of the original text. This tool hashes UTF-8 bytes, so spaces, newlines, and different Unicode representations can change the digest. Compare exact input bytes and the selected algorithm when checking a result from another system.
- Why does adding a newline change a text hash?
- A text hash processes the full input byte sequence, so adding a newline changes the data being hashed. LF normally occupies 1 byte, while CRLF occupies 2. Align encoding, line endings, and surrounding whitespace before comparing digests from different sources. Text that looks identical in an editor can still contain different bytes, and the hash does not know which formatting differences a reader considers unimportant.
- Why does online SHA-256 calculation require a secure browser context?
- This tool's SHA algorithms use Web Crypto, which generally requires HTTPS or a trusted localhost context. SHA-256 produces 64 hexadecimal characters, while SHA-512 produces 128. If SHA output is unavailable, check browser support and the connection context before changing the input. MD5 follows a separate implementation path, so its availability does not establish that the browser interface needed for the SHA calculations is also available.
Related tools
Base64 encode / decode
CRC-32