Account

What new tool do you want?

Developer Tools

Hash Generator (MD5, SHA-1, SHA-256, SHA-512)

Generate MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512 and CRC32 checksums of any text, instantly and privately in your browser.

How to use

  1. 1Type or paste your text.
  2. 2All hashes are calculated as you type — copy the one you need.

How it's calculated

Text is encoded as UTF-8, then hashed with each algorithm as specified in RFC 1321 (MD5) and FIPS 180-4 (SHA family).

Frequently asked questions

Is MD5 still safe?

Not for security. MD5 and SHA-1 have practical collision attacks. Use SHA-256 or better for integrity, and a slow hash like bcrypt or Argon2 for passwords.

Can a hash be reversed?

No — hashes are one-way. Short or common inputs can be guessed from lookup tables, though, which is why passwords need salts.

Why does my hash differ from another tool?

Check for trailing spaces or new lines and the text encoding. We hash exactly the UTF-8 bytes of what's in the box.

A worked example you can verify anywhere

Hashing the string "abc" produces md5 900150983cd24fb0d6963f7d28e17f72 and sha256 ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad — these are the standard published test vectors for MD5 and SHA-256, so you can check this tool's output against `echo -n abc | md5sum` or `echo -n abc | shasum -a 256` on any machine and get an identical result, which is exactly what a correct hash implementation guarantees: the same input always produces the same output everywhere, with no dependency on this tool specifically.

Why MD5 and SHA-1 still appear despite being 'broken'

MD5 and SHA-1 being cryptographically broken means it's computationally feasible to construct two different inputs that produce the same hash (a collision) — a real problem if you're relying on the hash to prove authenticity or resist a deliberate attacker. They remain here because they're still what legacy systems, older APIs, and some checksum-verification workflows expect, and for simply detecting accidental corruption (not deliberate tampering) they still work fine — a corrupted download doesn't happen to construct a matching MD5 collision by accident. The FAQ's guidance is the practical rule: SHA-256 or better for anything resembling security, and dedicated slow hashes like bcrypt or Argon2 (not any hash on this list) for passwords specifically.

Why trailing whitespace is the most common support question

A hash function has zero tolerance for input differences — hashing "abc" and "abc\n" (with a trailing newline) produces completely unrelated-looking outputs, because even one extra byte changes everything downstream. This is the single most common reason someone's hash doesn't match a colleague's or a published checksum: one of the two inputs has an invisible trailing newline or space that the other doesn't, often introduced by how a text editor saved the file or how a terminal command captured the string. The tool hashes exactly the UTF-8 bytes present in the input box — no normalization, no trimming — which is correct behavior, but it's worth deliberately checking for stray whitespace when a hash mismatch seems inexplicable.

Uppercase applies to every line, including the checksum

Uppercase hex starts off, so every digest is lowercase until I turn it on. The switch changes all of them together, including CRC32, which is listed after the hash algorithms. SHA-256 is the line marked as the main result. The others are still there. An empty box is hashed as empty text rather than rejected, and a trailing space changes the result, because the characters are taken exactly as they sit in the box. There is no separate encode or decode here. I only get the digests, and I can copy any of them.

Related tools

More: Developer Tools