Identify a hash

Guess MD5, SHA-256, bcrypt, Argon2 and other hashes from the shape of the string.

Runs in your browser. Your input is not uploaded.

Correctness last checked 2026-11-13. How we verify

This is a guess from the length and the prefix. It does not check that the value is a real digest of anything.

What it does, how to use it, and questions

What it does

Hash strings have recognisable shapes. MD5 is 32 hex characters, SHA-256 is 64, bcrypt starts with $2b$, and Argon2 starts with $argon2id$. This tool matches the shape and links to the tool that can work with it.

It is a guess. A 32-character hex string is usually MD5, and it can also be a truncated longer digest. Nothing here recovers the original input.

How to use it

  1. Paste one hash.
  2. Read the guess and the reason.
  3. Open the linked tool if you want to compute or check that kind of hash.

Example

Input
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
Output
SHA-256

Things to watch for

  • Hex length is not proof. SHA-256 and HMAC-SHA256 and SHA3-256 are all 64 hex characters.
  • Base64 digests are labelled as Base64 with an unknown algorithm. The length is not enough to tell SHA-256 from something else.
  • Unix $6$ and $5$ crypt hashes are named and not generated here.

Questions

Can this crack the hash?
No. It only reads the format. It does not search for an input that produces the digest.
How do I tell bcrypt from SHA-256?
bcrypt starts with $2a$, $2b$ or $2y$ and contains a cost. SHA-256 is 64 hex characters with no $.
Why might 32 hex characters not be MD5?
Someone may have cut a longer digest down to 32 characters. The usual answer is still MD5.
What about a sha256= prefix?
Strip the prefix and try again, or use the webhook signature tool if it came from a webhook header.