Keccak-384 produces a 384-bit digest (96 hexadecimal characters) and is part of the original Keccak family before the SHA-3 standardization.
This tool runs completely client-side. Your inputs never leave your device, ensuring privacy when hashing local identifiers, configuration data, or test vectors.
Output differences
Keccak-384 is distinct from SHA3-384. Although they share the same sponge construction, the padding rules differ. A string hashed with Keccak-384 will not match the same string hashed with SHA3-384.
Always verify your protocol requirements to ensure you are using the correct variant.
Batch processing
The tool supports hashing multiple inputs simultaneously. By checking “Batch by newline”, each line of your input will be hashed individually, producing a matching list of 96-character digests.
Enable “Trim lines” to automatically strip invisible leading or trailing whitespace from each line before hashing, preventing subtle mismatch errors.
Input sensitivity
A single changed byte alters the entire hash digest. Differences in capitalization, punctuation, or Unicode representation will result in completely different outputs.
You can enable “Normalize Unicode” to ensure that characters with multiple valid encodings (like accented letters) are unified before the hash is computed.