MD5, SHA-1, SHA-256, SHA-512
Tool guide
You paste arbitrary text — a string, a JSON payload, an API key, a webhook body — and get back the hexadecimal digest of the algorithm you picked: MD5, SHA-1, SHA-256 or SHA-512. The maths runs in crypto-js loaded into the page, so the string never leaves your tab. Handy when you need to match a checksum printed in someone's docs, sign a payment-gateway request, or reproduce a digest another service returned. See also: decode a JWT header and payload, generate a UUID v4 identifier, build a strong password.
Almost always the input differs in a way you cannot see. Check for a trailing newline or space you pasted along with the text, check the letter case, and check the encoding: this page hashes the string as UTF-8, while an older PHP script may have read it as windows-1251. Any of those changes every byte of the result, so compare the inputs, not just the digests.
No. The page has a single «Text» textarea and no file picker, so there is no way to checksum an ISO or an archive here. Use certutil -hashfile on Windows, sha256sum on Linux and macOS, or Get-FileHash in PowerShell. Pasting binary content into a text box will not give you the file's real digest.
You cannot. A hash function is one-way and has no inverse. The sites advertising "MD5 decryption" are looking your value up in precomputed dictionaries, which only works for short, common strings. If you need the original data back, what you want is encryption, not hashing.
Not where collision resistance matters — practical collisions have been published for both, so they must not sign documents or verify update packages. They are still fine as fast identifiers: cache keys, deduplication, or talking to a legacy API that insists on MD5. For anything security-related, choose SHA-256.
No, and this is the classic mistake. Fast hashes like SHA-256 can be brute-forced at billions of guesses per second on a GPU. Passwords need deliberately slow, salted functions: Argon2id, bcrypt or scrypt, or password_hash() and password_verify() in PHP. This tool is for checksums, not for an accounts table.
Yes. The string is encoded as UTF-8 before hashing, so accented letters, Cyrillic and emoji all work. Keep in mind that the same words in another encoding hash differently — «Привет» is twelve bytes in UTF-8 and six in windows-1251 — so confirm the other system's encoding before you compare results.
No. The hashing runs in JavaScript inside your tab using crypto-js, and the page makes no request carrying the contents of the field. The library itself is fetched from the cdnjs.cloudflare.com CDN, so you need a connection the first time you open the page, but your input is not part of that request.
Before: Text: hello world · Algorithm: SHA-256
After: b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
Before: Text: hello world · Algorithm: MD5
After: 5eb63bbbe01eeed093cb22bb8f5acdc3
Before: Text: (empty) · Algorithm: SHA-1
After: da39a3ee5e6b4b0d3255bfef95601890afd80709
Your rating and feedback help decide what to improve next.