SHA-384 Generator

SHA-384 is a member of the SHA-2 (Secure Hash Algorithm 2) family that produces a 384-bit digest, represented as 96 hexadecimal characters. It is technically SHA-512 with different initialisation vectors and the output truncated to 384 bits — the same 80-round compression function applies. SHA-384 is used in TLS 1.2 cipher suites, some government cryptography standards, and protocols that require a larger output than SHA-256 but where SHA-512's full 128-character output is not required.

Enter text or select a local file in the unified Hash Generator workspace, then click Generate hashes. SHA-384 appears alongside MD5, SHA-1, SHA-256, and SHA-512 so you can compare the digests side by side and copy or download whichever value your workflow requires.

SHA-384 is used in TLS 1.2 cipher suites (ECDHE-RSA-AES256-SHA384, TLS_RSA_WITH_AES_256_CBC_SHA384), some government and financial cryptography standards (e.g. NIST Suite B), digital signature schemes that specify 192-bit security, and subresource integrity (SRI) hashes in web pages where 384-bit output is preferred. Use the algorithm required by the receiving system or protocol specification.

SHA-384 produces 384 bits of output, normally displayed as 96 lowercase hexadecimal characters. This is longer than SHA-256 (64 chars) but shorter than SHA-512 (128 chars). The empty-string SHA-384 is 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b.

No. SHA-384 is a one-way hash function — it creates a fixed-length digest of your input and cannot be reversed to recover the original data. Encryption is designed to be reversed with the correct key. Never call a SHA-384 output encrypted data.

Yes. Select the Local file tab, choose a file, and the browser reads its bytes locally via FileReader.readAsArrayBuffer() and computes SHA-384 using the native Web Crypto API. No file bytes are uploaded to any server or stored in browser storage.

SHA-384 produces 96 hex characters (384 bits) and SHA-512 produces 128 hex characters (512 bits). Both use the same 80-round compression function with 64-bit word operations. SHA-384 uses different initialisation vectors and truncates the output to 384 bits. For most applications SHA-256 is sufficient; SHA-384 is chosen specifically when a protocol requires it or when the 128-character SHA-512 output is unwieldy.

SHA-384 produces 96 hex characters vs SHA-256's 64 hex characters, providing a larger security margin. SHA-384 uses 64-bit word operations (faster on 64-bit hardware for large inputs) while SHA-256 uses 32-bit operations. SHA-256 is more widely deployed and is the correct choice for most general-purpose integrity and authentication tasks. SHA-384 is used when a protocol specifically requires it.

Hash output depends on exact input bytes. Check for extra whitespace, line-ending differences (LF vs CRLF), Unicode encoding differences, a different file version, or whether the published checksum is SHA-256 or SHA-512 rather than SHA-384. This tool uses UTF-8 for text input.

Yes. Generate the digests, select SHA-384 in the Checksum Verification section, paste the expected hexadecimal value, and click Verify. The tool reports an exact match or mismatch after normalising whitespace and case, and updates the Verification stat in the stats strip.

Yes. SHA-384 is computed using the browser's native crypto.subtle.digest('SHA-384') Web Crypto API — the same API that powers HTTPS in your browser. No text, file, or hash value is uploaded or stored. All processing runs in browser memory only.

Type or paste the text and the SHA-384 digest appears instantly as a lowercase hex string. Processing is local, with no server round-trip.

Yes. Load the file — it is read locally — and compare the computed digest against the published checksum from a download page. A match confirms the file is intact.

SHA-384 is a strong cryptographic hash, but plain hashes are still the wrong tool for passwords — use a dedicated password hashing scheme with salt and cost factors. Use SHA-384 for integrity, signatures, and fingerprints.

SHA-384 produces a 384-bit (96 hex characters) digest. The hex form you see is two characters per byte, always the same length regardless of input size.

Yes. Hashing is deterministic — identical input bytes always produce the identical digest. Even a one-character change produces a completely different hash.

Yes, within browser memory. Because hashing runs locally there is no upload time and no file-size quota.

SHA-384 offers a larger security margin and appears in TLS cipher suites and some compliance profiles. If a spec asks for SHA-384, use it; otherwise SHA-256 is usually sufficient.

Everything runs locally in your browser with no upload, no account, and no logging. You can confirm in your browser DevTools Network tab that no request carries your data.