Hash Identifier
Identify the algorithm behind a hash by its format — MD5, SHA family, bcrypt, crypt formats, JWTs, UUIDs, AWS keys and more — plus a hex ↔ base64 converter. All detection is local.
Identify hashes
Hex ↔ Base64 converter
How it works
- Hash algorithms are identified by shape: the character set (hex, base64, or crypt-style) and the digest length. A 32-character hex string is 128 bits — the signature of MD5 and its relatives; 64 hex characters is 256 bits, typical of SHA-256.
- Prefixes pin things down further:
$2a$/$2b$/$2y$is bcrypt,$1$is MD5 crypt,$5$/$6$are SHA-256 / SHA-512 crypt,eyJ…is a JWT,AKIA…is an AWS access key. - Many digests share a length, so the tool reports ambiguity honestly: 32 hex chars could be MD5, NTLM, LM, or MD4 — you cannot tell from the format alone.
- The converter treats hex and base64 as byte encodings of the same underlying value, so you can switch between them losslessly.
About Hash Identifier
When you inherit a database dump, a config file, or a legacy auth table, the first question is usually "what hashed this?" The answer is almost always recoverable from the format: standardized prefixes and canonical digest lengths make modern schemes self-describing. This tool answers that question instantly and, just as importantly, tells you when the answer is ambiguous — because a length match is a necessary but not sufficient clue.
Identification is a starting point, not a verdict. If you only have a ciphertext digest (for example a 64-char hex string) there is no way to know whether it was produced by SHA-256, SHA3-256, or BLAKE2s without the original input; and a "MD5" label says nothing about whether the value is unsalted, salted, or doubled. Use the result to guide your next step — checking salting, iteration counts, or password-recovery tooling — rather than to conclude anything definitive.