OnlineConverTools
Sign in

Hash Generator

MD5, SHA-1, SHA-2, SHA-3, BLAKE2, BLAKE3, RIPEMD-160, CRC32, and xxHash — for text or files, which are read in pieces

Everything is computed in your browser: nothing is uploaded. The tool sets no file size cap: large files are read in pieces.

Algorithms
Common
SHA-2 and SHA-3
Other
Checksums

About Hash Generator

Hash Generator computes 17 hashes and checksums (MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, Keccak-256, BLAKE2b-512, BLAKE3, RIPEMD-160, CRC32, CRC32C, xxHash64, XXH3-64, and XXH128) for typed text or for files. Text is hashed as UTF-8 while you type. Files are read in 8 MiB pieces in your browser, several files in one run, and the tool sets no size cap. Paste a published checksum to see which checked algorithm matches, add an HMAC key to sign data, and save file results as checksums.txt. Web Workers in your own tab compute every hash.

Example

The word hello (5 bytes, no line break), typed in Text mode:

Text

hello

Hashes

MD5      5d41402abc4b2a76b9719d911017c592
SHA-1    aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
SHA-256  2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
CRC32    3610a686

How to generate or check a hash

  1. 1Choose "Text" or "Files", then check the algorithms you need: MD5, SHA-1, SHA-256, SHA-512, and CRC32 are checked at first, and "Select all" checks every one.
  2. 2Type or paste text and the results appear as you type; for files, drop or choose them, then click the button that starts with Hash and counts the files you added.
  3. 3To verify a download, paste its published checksum into "Expected hash, to verify (optional)": the matching value turns green.
  4. 4"Copy" copies one value; in Files mode, "Copy all" copies every checksum line and "Download" saves them as checksums.txt.

Formats and limits

Algorithms
17: MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, Keccak-256, BLAKE2b-512, BLAKE3, RIPEMD-160, CRC32, CRC32C, xxHash64, XXH3-64, XXH128
Output format
Hex lowercase, hex uppercase, or Base64 on screen; checksums.txt always uses lowercase hex
File size
The tool sets no cap: files are streamed in 8 MiB pieces
Web Crypto path
SHA-1, SHA-256, SHA-384, and SHA-512 use your browser's native code for files up to 700 MiB on a computer and 100 MiB on phones and tablets; everything else goes through hash-wasm
HMAC
Offered for MD5, SHA-1, the SHA-2 and SHA3 variants, BLAKE2b-512, and RIPEMD-160; the others are skipped while a key is set

Where your file is processed

Hashing runs in Web Workers inside your browser tab: your files and text are not sent to us, and the HMAC key stays in the page. If you turn on a translation in the language menu, Google receives the page's visible text, which includes the hash values shown. When the red box shows an error (a cancel excepted), we receive that error, the tool's name, and your browser's name and version.

Frequently asked questions

Which hash should I use: MD5, SHA-1, or SHA-256?

Use the one the publisher lists, since a checksum can only be compared with the same algorithm. For new uses pick SHA-256: practical collisions are known for MD5 and SHA-1, not for SHA-256. MD5 and CRC32 still catch accidental corruption of a copy.

Is there a file size limit?

No. The tool sets no cap: files are read in 8 MiB pieces in your browser. Files up to 700 MiB (100 MiB on phones and tablets) are also loaded whole once, so SHA-1 and SHA-256/384/512 can use the faster Web Crypto. Speed depends on your device.

How do I verify a downloaded file?

Choose "Files", add the file, and paste the publisher's checksum, in hex or Base64, into "Expected hash, to verify (optional)". After hashing, the matching algorithm turns green if it is checked; if none matches, the tool names the algorithms that give a hash of that length.

Can sha256sum -c check the checksums.txt file?

Yes for its SHA256 lines, and md5sum -c reads the MD5 lines. Each command checks only its own algorithm, so lines for CRC32, xxHash, BLAKE3, Keccak-256, or an HMAC are for reading. Check only SHA-256 to get a file that sha256sum -c reads completely.

What does the HMAC key do?

With a key, each eligible algorithm computes an HMAC, such as HMAC-SHA256, the keyed hash used to sign API requests and webhooks. Keccak-256, BLAKE3, CRC32, CRC32C, and the xxHash family are not offered with a key and are skipped until you clear it.

Why does my text give a different hash elsewhere?

A hidden difference in the bytes is the usual cause: the box hashes exactly its UTF-8 text, so a trailing newline, Windows line endings, or another encoding elsewhere change the result. Compare the byte count shown above the results.

Tips and tricks

  • ✓Avoid MD5 and SHA-1 for anything security-sensitive — they are fine as checksums against accidental corruption, not against tampering. Use SHA-256 or better.
  • ✓CRC32 and xxHash are checksums built for speed, not security: good for spotting corrupted copies, useless against deliberate changes.
  • ✓Before hashing a large file, uncheck the algorithms you do not need: each one checked adds work for the browser.

Related tools