Hash generator: SHA-256, SHA-1 and MD5
About Hash Generator
The hash generator turns text into a hex digest with SHA-256, SHA-1 or MD5. The result matches what a server, a checksum tool or a database would produce for the same UTF-8 input.
Use it to verify a checksum, reproduce a hash your backend generated, build a cache key, or compare two values. Runs in your browser in plain JavaScript. Nothing is uploaded, so it is safe for sensitive strings.
How it works
SHA-256: the modern default
SHA-256 gives a 64-character (256-bit) hex digest. It is the current standard for integrity checks, content addressing and signatures, with no known practical collision or preimage attacks. Use it when the hash needs to be trusted.
SHA-1 and MD5: legacy and checksums
SHA-1 (40 hex characters) and MD5 (32) are cryptographically broken, because attackers can create collisions. Never use them for security. They still work for non-adversarial checksums, ETags, matching hashes from legacy systems, or deduplicating data.
UTF-8 bytes in, hex out
Text is encoded to UTF-8 before hashing, so emoji, accents and non-Latin scripts match what most servers and languages produce. Output is lowercase hex by default. Turn on Uppercase hex if the system you compare against uses uppercase.
Deterministic and one-way
The same input always gives the same digest, and changing one character gives a completely different one. There is no way back from a hash to the original text, which is why hashes are used to verify data, not to store it.
Frequently asked questions
How do I generate a SHA-256 hash online?
Paste your text, leave the algorithm on SHA-256 and copy the 64-character hex digest. It is computed from the UTF-8 bytes of your text, so it matches sha256 output from OpenSSL, Node, Python's hashlib and most databases.
Is MD5 secure?
No. Collisions (two inputs with the same MD5 hash) are cheap to produce, so never use it for passwords, signatures or anything an attacker could exploit. It is still fine as a fast checksum against accidental corruption or for matching a legacy value.
Can a hash be reversed back to the original text?
No. Hashing is one-way, and the digest holds no copy of the input. People sometimes 'crack' short or common strings by hashing many guesses and comparing, but no formula inverts a hash. To store data you need to read back, encrypt it instead.
Is my text uploaded when I hash it here?
No. Every digest is computed in your browser and nothing is sent, logged or stored. The tool also works offline.
Why does my hash differ from another tool's?
Usually an encoding or case difference. Make sure both tools hash the same UTF-8 bytes, since a trailing newline or a different encoding changes the result. Check whether the other tool outputs uppercase hex, and toggle Uppercase hex here to match.
Learn more
Sources & last verified
We checked this tool's behavior and the claims on this page against the specifications below on . The tool runs in your browser, so the output you see is exactly what the engine produced.
Found a wrong result or an outdated claim? Report an error and we will check it again.