01
Choose the byte representation
UTF-8 hashes the entered characters. Hex and Base64 decode into bytes first: the text 6162 and Hex 6162 are different inputs.
- Whitespace is data in UTF-8; it is rejected in Hex and Base64.
Hash & Crypto Helpers
Hash generatorExact bytes, comparable digests
Choose input encoding and one or more algorithms; verify a reference digest with its own algorithm and encoding.
Hash generator
Input text or encoded bytes
Digests
Text and salt stay in your browser.
Options
Hex and Base64 reject whitespace. Salt concatenation is not HMAC. MD5 and SHA-1 are legacy algorithms.
Maximum: 1,000,000 input UTF-16 units; 1,000,000 data + salt bytes; 4,096 salt UTF-16 units.
Compare an expected digest
Enter an expected digest and compare.
Enter data or run manually to hash an empty string.
Report excludes original input and salt content.
Hash generator helps when a backend digest differs from a test fixture: compare several algorithms against one exact byte sequence instead of changing inputs between tools.
Use this MD5 hash generator for legacy compatibility, the SHA-256 hash generator for a specified SHA-2 digest, or the SHA-512 generator when your integration requires it. A digest does not authenticate its source.
Why use this Hash generator?
Separate algorithm choice from the bytes being hashed.
Compare 13 digests together
Select the exact variants your system expects. Each result belongs to the same decoded input and salt settings, so a change in length reflects the algorithm rather than a different pasted sample.
See where the salt goes
Prefix means UTF-8 salt bytes followed by input bytes; suffix reverses that order. The same visible salt in a different position normally changes every digest.
Avoid mismatches before comparing
02
Select variants and salt order
SHA-256 and automatic calculation are selected initially. Automatic mode waits 350 ms after changes; turn it off to run manually.
- Empty input is valid. Initial load and Clear stay idle; deleting to empty or changing options can automatically compute zero bytes.
03
Match the reference format
Select the expected digest's algorithm and its Hex or Base64 encoding. Compare only against a current result; changing input or options makes old results stale.
- The comparison algorithm must be among the computed algorithms.
Control the digest contract
SHA-2, SHA-3 and BLAKE
Choose MD5, SHA-1, SHA-224/256/384/512, SHA3-224/256/384/512, BLAKE2b-512, BLAKE2s-256 or BLAKE3-256. Similar bit lengths do not make algorithms interchangeable.
Encoded bytes as input
Strict decoding keeps malformed representations from becoming unexpected data. Hex needs complete byte pairs; standard Base64 accepts omitted padding only when its unused bits are canonical.
Explicit reference comparison
The expected value has its own encoding selector. Hex letter case does not change bytes, while Base64 letter case does; a matching digest is evidence only relative to the chosen reference.
A report without the source text
Copy individual digests or download a report containing algorithms, encodings, byte counts and salt position. Original text and salt content are excluded from the report.
Byte rules and limits
- Nothing is silently normalized
- The tool preserves BOM, whitespace and CRLF in the input it receives. It does not normalize Unicode. Unpaired UTF-16 surrogates are rejected instead of replaced. Browser paste and text fields may normalize line endings before calculation; use Hex or Base64 for exact bytes.
- Bounded input
- Input is limited to 1,000,000 UTF-16 code units and the decoded data plus active salt to 1,000,000 bytes. Salt is UTF-8 text, capped at 4,096 UTF-16 code units.
- Salt concatenation has a narrow purpose
- No salt ignores the salt field. Prefix and suffix concatenate bytes without separators. This is not HMAC, keyed BLAKE, password hashing, encryption or file hashing.
- Current results only
- Input or calculation errors and changed settings invalidate export and comparison. An invalid expected digest does not invalidate computed digests or their export. Computation runs locally in a worker; a task taking over 10 seconds times out. Reduce the input or selected algorithms and retry.
Hash generator questions
Is my data uploaded anywhere?
No. Hash generator computes input and salt locally in your browser. The downloadable report contains digests and settings, not the original text or salt.
Which algorithms are supported?
There are 13 variants, including the four supported SHA-2 sizes, four SHA-3 sizes, MD5, SHA-1 and three fixed-length BLAKE variants. BLAKE3 output is fixed at 256 bits.
Which algorithm should I use?
Match the algorithm named by your protocol or reference value. SHA-256 is the default. MD5 and SHA-1 are retained for legacy comparisons and should not be used for security decisions.
What is the HMAC key for?
An HMAC key participates in a defined message-authentication construction. This page has only byte-prefix or byte-suffix salt concatenation; it does not produce HMAC or prove who created a message.
What is the difference between a hash and encryption?
Encryption is reversible with a key; hashing produces a digest without a decryption operation. Predictable inputs can still be guessed and checked, so a hash does not make a short secret confidential.
Still have a question?
Try the Hash generator
Use Hash generator with a known test string, then change one byte and compare the resulting digests.
Text and salt are processed locally.