SHA-3 · 256 bits · Text
Calculate SHA3-256 from UTF-8, Hex or Base64 text. Compare a trusted expected digest locally.
SHA3-256 calculated
0 decoded bytes · UTF-8 · input changes update automatically
Browser-local hashing. Inputs masked in Clarity.
No account. No uploads. Just your browser.
| Algorithm | What differs |
|---|---|
| SHA3-256 | SHA-3 construction standardized in FIPS 202. |
| SHA256 | SHA-2 construction standardized in FIPS 180-4; a different digest. |
SHA3-256 uses the SHA-3 standard and produces 64 hexadecimal characters. It is not SHA256 and is not Keccak-256: their padding rules differ, so identical input produces different digests.
Select SHA3-256 explicitly when your source names it. A blockchain Keccak-256 checksum must not be tested with SHA3-256. Equal output lengths do not identify an algorithm.
Type or paste text for an automatic result. UTF-8 preserves whitespace and line endings. Hex accepts pairs of digits with optional whitespace; Base64 requires the standard padded alphabet. Invalid encoding stops calculation instead of hashing a different input.
The default result is the digest of zero bytes. The abc example contains exactly 61 62 63 in hex with no newline. Adding Enter changes the bytes and therefore the result.
Paste a complete hexadecimal expected value to see Match or Mismatch. Outer whitespace and uppercase hex are accepted; incomplete digests, filenames and embedded spaces are not.
HMAC-SHA3-256 calculates a keyed hash. Enable HMAC and enter the secret in its own encoding. An empty key is a valid key and differs from turning HMAC off. Keys are never saved or included in exported reports.
The SHA3-256 file checksum tool reads raw bytes in chunks and supports batch manifests. Text mode is limited to 8 MiB decoded input; use file mode for larger data.
No input is uploaded. Only a light/dark theme preference is stored. Copy and report downloads remain on your device.
Start empty, paste UTF-8 text, or choose Hex or Base64 for encoded bytes.
SHA3-256 returns 64 lowercase hex characters. Copy digest preserves the whole output.
Paste a trusted reference, or enable HMAC only for a keyed protocol.
Use SHA3-256 when the reference explicitly names it; output length alone is insufficient.
Confirm padding and domain conventions before comparing values from another ecosystem.
Use the same raw bytes and full 64-character digest in both implementations.
SHA3-256 · 0 bytes · no HMAC. Empty input is not the same as no file selected.
SHA256 Onlinea7ffc6f8bf1ed76651c14756a061d662f580ff4de43b49fa82d80a4b80f8434aNo. Both yield 256 bits but use different constructions. Select SHA3-256 only for a reference or protocol that explicitly requires it.
No. Keccak-256 and standardized SHA3-256 use different domain separation/padding and return different digests. This tool implements SHA3-256.
No. SHAKE256 is an extendable-output function. SHA3-256 is a fixed-output hash; the names and output sizes do not make them interchangeable.
It is the digest size in bits, displayed here as 64 hexadecimal characters. It does not select UTF-8 text length or a 256-character input limit.
UTF-8 hashes literal text. Hex and standard padded Base64 decode to bytes first. abc, Hex 616263 and Base64 YWJj represent the same bytes; invalid encodings stop calculation.
Yes. Text is not trimmed. A trailing newline, carriage return, byte-order mark or extra space changes the byte sequence and usually the result.
Paste exactly 64 hexadecimal characters. Uppercase and outer whitespace are accepted. Match means equality with your reference, not proof of a trustworthy source.
Text and keys stay in browser memory, not URLs or localStorage. The tool saves only your theme preference; Clarity may use its own identifiers, as explained in Privacy. Text mode accepts up to 8 MiB of decoded bytes; use file mode for larger inputs.