Why does the result differ from `md5sum`?

Usually encoding or line-ending differences. This tool hashes UTF-8 bytes of the text; `md5sum` hashes the exact file bytes. Check for a BOM or `\r\n` vs `\n`.

Not for signatures or tamper detection (practical collisions exist). For deduplication or cache keys it is fine.

Where are SHA-3 and BLAKE2?

WebCrypto currently ships neither. This tool sticks to what browsers can compute natively (plus MD5).

Why does a command-line digest differ?

Check for an added newline, such as differences between echo and printf, then compare encoding, BOM and algorithm. This hashes UTF-8 textarea content, not original file bytes.

If SHA is unavailable, is the MD5 result invalid too?

Not necessarily. MD5 uses this site's frontend implementation, while SHA calls the browser's Web Crypto interface. Check browser support and a secure connection when SHA is unavailable.

Text hash (MD5 / SHA)

Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 locally

Computed in your browser

Enter text to calculate several digests automatically. Check trailing newlines and UTF-8 byte counts before comparing; SHA needs browser support.

Input

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.

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

Why does the result differ from `md5sum`?: Usually encoding or line-ending differences. This tool hashes UTF-8 bytes of the text; `md5sum` hashes the exact file bytes. Check for a BOM or `\r\n` vs `\n`.
Can I still use MD5?: Not for signatures or tamper detection (practical collisions exist). For deduplication or cache keys it is fine.
Where are SHA-3 and BLAKE2?: WebCrypto currently ships neither. This tool sticks to what browsers can compute natively (plus MD5).
Why does a command-line digest differ?: Check for an added newline, such as differences between echo and printf, then compare encoding, BOM and algorithm. This hashes UTF-8 textarea content, not original file bytes.
If SHA is unavailable, is the MD5 result invalid too?: Not necessarily. MD5 uses this site's frontend implementation, while SHA calls the browser's Web Crypto interface. Check browser support and a secure connection when SHA is unavailable.

Related tools

Text hash (MD5 / SHA) · Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 locally — Text hash (MD5 / SHA) — Tool illustration · dayeku.com