Hash text online
Compute a SHA-256, SHA-1, or MD5 digest of any text — to verify a download's integrity, compare two values, or generate a stable key — all locally.
Open the tool, then paste the sample input below. Everything runs locally in your browser.
The problem
You need a hash: to confirm a file or string matches a published checksum, to compare two values without storing them, or to derive a stable cache key. Computing it locally gives you the digest without installing a CLI or sending the text anywhere.
Sample input
hello
Expected output
SHA-256: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
MD5: 5d41402abc4b2a76b9719d911017c592
Hashing is one-way: the same input always gives the same digest, but you cannot reverse the digest back to the text. SHA-256 is preferred; MD5 is shown for legacy checksums only.
How to do it
- Paste the text to hash.
- Choose the algorithm, such as SHA-256.
- Compute the digest.
- Compare it to an expected checksum if you have one.
- Copy the digest.
Common mistakes
- Using MD5 or SHA-1 for security instead of integrity-only checks.
- Hashing with a trailing newline that changes the digest.
- Comparing digests in different cases or with spaces.
- Expecting to reverse a hash back to the input.
- Treating a fast hash as safe for storing passwords.
Related tools
Related guides
FAQ
How do I hash text?
Paste the text, choose an algorithm such as SHA-256, and compute. The tool returns the hex digest, which is the same every time for the same input.
Can I reverse a hash to get the text back?
No. Hashing is one-way. You can only recompute the hash of a candidate input and compare, not invert the digest.
Should I use MD5?
Only for non-security checksums against legacy systems. MD5 and SHA-1 are broken for security; use SHA-256 when integrity matters.
Why does my hash not match the published one?
Often a trailing newline or different character encoding changed the input. Hash the exact bytes, and compare digests case-insensitively in hex.
Is my text uploaded?
No. Hashing runs locally in your browser. Your text is not sent to a server.
Hashing runs locally in your browser. Your text is not uploaded.
Hash and encode text, scan for secrets, decode tokens and inspect certificates — grouped in one place.