How to use the hash generator
A cryptographic digest maps text bytes to a fixed-length hexadecimal value. Choose SHA-256, SHA-384, or SHA-512 and calculate the digest with the browser Web Crypto API. Input is encoded as UTF-8 without trimming spaces or line breaks. This is not encryption, a password storage system, a keyed HMAC calculator, or a file hashing tool.
Work directly in the input area at the top of this page and choose the settings that match your task. Run the action to see the output separately from your original input. Start with a small example whose result you can check, then process the value you actually need. Changing an input clears an older result so it cannot be mistaken for a fresh conversion.
Processing runs in your browser. This tool does not send your input to a conversion server, create an account history, or save the input in browser storage. A copied result remains subject to your device clipboard settings, while a downloaded file stays on your device until you remove it. Anyone with access to your screen or browser can still see the information you enter.
Use Copy for text output or Download for a local file. If clipboard access is unavailable, select the output and copy it manually. Clear removes the current result and any main text or file input; settings remain available for another run. Keep original files and important values until you have checked that the output works in the application where you intend to use it.
Frequently asked questions
Can a hash be reversed back into the original text?
No. A hash is one-way. Short or predictable inputs can still be found by guessing and comparing, which is why passwords need a slow, salted algorithm such as bcrypt or Argon2 rather than a plain SHA hash.
Which algorithm should I choose?
SHA-256 for file checksums and general integrity work; SHA-384 or SHA-512 where a longer digest is specified, for instance by a signing standard. SHA-512 is often faster on 64-bit hardware despite the longer output.
Why does my hash not match the one from my terminal?
Almost always a difference in what was hashed rather than in the algorithm. A trailing newline, different line endings between Windows and Unix, or a different text encoding each produce a completely different digest.