Hash Generator & Checksum Checker

Compute the checksum of text or a file, then paste the checksum from the download page to confirm the file is intact. Files are not uploaded anywhere.

Source

Text is hashed as UTF-8, exactly as typed.

Algorithms
Output format

Paste a checksum in hex or Base64. The algorithm is recognized from its length.

How to use it

  1. Choose Text and type or paste, or choose File and drop a file on the box (ISO, APK, ZIP, anything).
  2. Tick the algorithms you need. Text checksums update as you type; large files show progress while they are read.
  3. Pick lowercase hex, uppercase hex or Base64, then press Copy on the row you need.
  4. To verify a download, paste the publisher's checksum into Compare with checksum. The algorithm is recognized from its length.

What a checksum is for

A hash function turns data of any size into a fixed-length string of bytes called a digest or checksum. The same data always gives the same checksum, and changing a single character gives a completely different one. The SHA-256 of the text abc is ba7816bf…f20015ad; for abd it is a52d159f…298449c9.

That is why download pages list a checksum next to ISO images, installers and APKs. After downloading, compute the checksum of your copy here and paste the published value into the compare field. If they match, your file is identical, bit for bit, to the one the publisher released: nothing was cut off or corrupted on the way.

A checksum is only as trustworthy as the page it came from. If the download server is compromised, an attacker can swap the file and the checksum on the same page. Ubuntu and Debian sign their checksum lists (SHA256SUMS) with a GPG key to close that gap.

Digest lengths

AlgorithmStandardBitsBytesHex charactersBase64 characters
MD5RFC 1321 (1992)128163224
SHA-1FIPS 180-4160204028
SHA-256FIPS 180-4256326444
SHA-384FIPS 180-4384489664
SHA-512FIPS 180-45126412888

The compare field uses these lengths to tell the algorithms apart: 64 hex characters can only be SHA-256, 40 can only be SHA-1.

MD5 and SHA-1 are broken for security

For security purposes, MD5 and SHA-1 are broken: it is possible to deliberately craft two different files with the same hash (a collision). RFC 6151 (March 2011) says MD5 is no longer acceptable where collision resistance is required, such as digital signatures. The first SHA-1 collision was announced by CWI Amsterdam and Google on 23 February 2017, and NIST has set 31 December 2030 as the date by which SHA-1 must be phased out.

Both still catch accidental damage, such as a download that stopped early. To be sure a file was not swapped on purpose, use SHA-256 or longer.

Not for storing passwords

None of these five algorithms is suitable for storing passwords, SHA-512 included. They are all designed to be fast, and a single graphics card can compute billions of them per second to guess the passwords in a leaked database. Passwords need a function that is slow on purpose and uses a salt: Argon2id, scrypt or bcrypt. OWASP lists Argon2id as the first choice.

How this tool works

Text is encoded as UTF-8, exactly as typed. The SHA algorithms run in the browser's built-in Web Crypto. Web Crypto has no MD5, so MD5 is computed by this site's own JavaScript, tested against the official examples in RFC 1321. Files are read in 8 MB pieces. MD5 is updated piece by piece, so file size is not limited by memory. Web Crypto needs the whole file in memory for SHA, so a file of several GB can fail on a phone with little RAM.

Questions

Why does my result differ from the echo command in a terminal?
A command such as echo "text" | sha256sum adds a newline at the end, and that newline is hashed too. Use printf '%s' "text" | sha256sum or echo -n. This tool hashes exactly what is in the box, including any spaces and line breaks you typed yourself.
How do I verify a downloaded ISO or APK?
Choose File, pick the downloaded file, then paste the checksum from the publisher's site into the compare field. Lines such as hash file-name.iso and SHA256 (file-name.iso) = hash are understood too. Without a browser, the commands are sha256sum file.iso on Linux, shasum -a 256 file.iso on macOS and certutil -hashfile file.iso SHA256 on Windows.
Is my file or text uploaded?
No. The browser reads and hashes the file on your own device, which is also why large files don't have to wait for an upload.
How large a file can it handle?
MD5 is computed piece by piece, so size is practically unlimited. SHA needs the whole file in memory, and the browser may use up to twice the file size while computing it. A 1 GB file is usually fine on a computer; on a phone, SHA for a file that size can fail for lack of RAM, and the tool will tell you.
Do uppercase and lowercase letters matter?
Not in hex: BA7816BF and ba7816bf are the same number, and the compare field treats them as equal. Base64 is case-sensitive, so copy it exactly.
Is it still OK to use MD5?
For detecting a corrupted or truncated file, yes. For anything security-related, such as signatures, certificates or passwords, no. Choose SHA-256 when the publisher offers it.