Quick access

Saved in this browser. Sign in to keep it on all your devices.

Hash Generator

MD5, SHA-1, SHA-256, SHA-512, SHA-3, Keccak-256 and CRC32 for text or files of any size. Paste a checksum to check a download.

Private — files never leave your device
Quick pick:
Empty input has a hash too — shown below.

Your text ends with a line break, which changes the hash.

✓ Match — . The data is identical.

✗ No match yet — add the file above.

A -bit hash fits . If you used the right algorithm, the data is different.

No algorithm here gives a -bit hash. Check you copied all of it.

That doesn't look like a hash. Paste hex (0–9, a–f) or Base64.

Hashes

Pick at least one algorithm above.

Files

Which one to use

  • SHA-256 — the default for checksums, Git, TLS and most downloads.
  • SHA-512 / SHA-3 — longer or newer, equally safe choices.
  • MD5, SHA-1, CRC32 — only to match old checksums. Collisions can be made on purpose.
  • Keccak-256 — Ethereum's hash. It is not the same as SHA3-256.

Check a file from the command line

Windows (PowerShell)
Get-FileHash file.iso -Algorithm SHA256
macOS
shasum -a 256 file.iso
Linux
sha256sum file.iso

Passwords and signatures

A plain hash is too fast to protect passwords. Store them with the Bcrypt Generator. To prove a message came from someone who knows a secret key, use the HMAC Generator. To encode rather than hash, use Base64.

Version 1.1 Updated What's new

Release notes

  1. v1.1 Latest
    • Added an in-depth guide below the tool, written from what the tool actually does.

About the Hash Generator

A hash function turns any input into a fixed-length fingerprint. The same input always gives the same hash, and even a one-letter change gives a completely different one. That makes hashes ideal for checking that a file arrived intact.

How to use it

  1. 1 Type text, or switch to Files and drop one or more files.
  2. 2 Pick the algorithms you need, such as SHA-256.
  3. 3 Paste the published checksum into the compare box to see if it matches, or copy the hash.

Frequently asked questions

Can a hash be reversed?

No. Hashes are one-way. Short or common inputs can be guessed with lookup tables, which is why passwords need slow, salted hashes like bcrypt.

Which hash should I use?

SHA-256 is the standard choice for integrity checks. SHA-512 and SHA-3 are equally safe. MD5 and SHA-1 are broken for security and should only be used to match old checksums.

How do I verify a downloaded file?

Drop the file into the Files tab and paste the checksum from the download page into the compare box. It tells you which algorithm matched, or that the file is different.

Are my files uploaded?

No. Files are read in small pieces inside your browser, so even multi-gigabyte ISO images can be hashed without leaving your device.

Why does my hash differ from the command line?

Usually because of a line break. Commands like echo add a newline to the end of the text, which changes the hash. The tool warns you when your text ends with one. Also check that both sides use the same algorithm.

Is SHA3-256 the same as Keccak-256?

No. Ethereum uses the original Keccak, which pads its input differently from the final SHA-3 standard, so the two give different hashes for the same input.

What is CRC32 for?

CRC32 is a fast checksum used in ZIP files, PNG images and network packets to catch accidental damage. It is easy to forge, so never use it for security.

Verify a checksum on Windows, macOS and Linux

:: Windows Command Prompt
certutil -hashfile ubuntu.iso SHA256

# Windows PowerShell
Get-FileHash ubuntu.iso -Algorithm SHA256

# macOS
shasum -a 256 ubuntu.iso

# Linux
sha256sum ubuntu.iso
sha256sum -c SHA256SUMS   # checks every file listed

Compare the full value, not just the first and last few characters. Case does not matter: ABC123 and abc123 are the same hex value.

Hash lengths at a glance

  • CRC32: 32 bits, 8 hex characters.
  • MD5: 128 bits, 32 hex characters.
  • SHA-1: 160 bits, 40 hex characters.
  • SHA-256 and SHA3-256: 256 bits, 64 hex characters.
  • SHA-512: 512 bits, 128 hex characters.

The length of a published checksum tells you which algorithm to pick. A 64-character value is almost always SHA-256.

Known hashes to test your code

The text hello, in lowercase with no newline, always gives these values:

MD5     5d41402abc4b2a76b9719d911017c592
SHA-256 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

On the command line, use echo -n hello | sha256sum. Without -n, echo adds a newline and you get a completely different hash.

Hashing is not encryption

Encryption is meant to be undone by someone with the key. A hash cannot be undone by anyone, which is the point. So a hash is right for checking files and for storing passwords (with a slow algorithm such as bcrypt or Argon2), but wrong for anything you need to read back later, such as a stored API key or a message. For a hash that proves who sent a message, use an HMAC with a shared secret.