Hashes of empty input are shown until you type something.
Compute MD5, SHA-1, SHA-256, SHA-512, SHA3-256, BLAKE3 and CRC-32 for text or files of any size, all at once and in your browser. Add a secret key for HMAC, or paste a published checksum to verify a download.
Choose Text or Files, then type text (hashes update as you type) or drop one or more files.
For text, set Read input as to UTF-8 text, Hex or Base64 if your input is encoded bytes.
Pick the Output format (hex, HEX or Base64) and turn on More algorithms for SHA-224, SHA-384, SHA3-512, Keccak-256, BLAKE2, RIPEMD-160, xxHash and CRC-32C.
To verify a download, paste the expected hash into Compare with expected hash; the matching row turns green.
For a keyed hash, turn on HMAC and enter the Secret key as text or hex.
No. Files are read in chunks by a background worker in your browser and never uploaded, so there is no size limit beyond what your device can read. Each file shows its hashing speed when done.
Usually the input differs by invisible bytes. echo adds a trailing newline (use echo -n), and text copied from documents may contain different line endings or spaces. Also check that Read input as matches your data.
No. Hashes are one-way. Short or common inputs can still be found by guessing, so a plain SHA-256 is not a safe way to store passwords; use the Bcrypt, Scrypt & Argon2 tool for that, or AES Encrypt & Decrypt if you need to get the data back.
Yes. The compare box picks out every hex or Base64 token in the line and checks it against all shown algorithms, so you don't need to know which one was used.
The MD5, SHA and RIPEMD rows. Checksums (CRC), BLAKE and xxHash have no HMAC form, so they are hidden while HMAC is on. The key stays in the tab and is never saved or sent.
They are fine for spotting accidental corruption, but practical collisions exist for both, so don't rely on them where someone might forge data. Prefer SHA-256 or newer for anything security-related.