simpletool.io

SHA384 Hash Generator

Compute SHA-384 digests in the browser.

SHA-384 runs in your browser via Web Crypto. No uploads.

SHA-384 · 384-bit digest · SHA-512 truncated, recommended for TLS 1.3 high-security suites

Text input

SHA-384 hash
—

0 chars · lowercase hex

File input

Hash any file up to 500 MB. Processed locally — the file never uploads.

Similar tools

Base64 Encoder/Decoder

Encode and decode Base64 text and files, URL-safe variant included.

URL Encoder/Decoder

Percent-encode and decode URLs or just components.

HTML Encoder/Decoder

Escape and unescape HTML entities in any string.

What is a SHA-384 Hash Generator?

SHA-384 is a member of the SHA-2 family that produces a 384-bit (48-byte) digest. Internally it uses the SHA-512 compression function with a different initialisation vector, then truncates the result to 384 bits. In hex the output is 96 characters. SHA-384 has historically been the hash of choice for high-assurance systems that want the defence-in-depth of a SHA-512-class algorithm without carrying a full 512-bit field everywhere.

Real-world uses. The CNSA Suite (the US NSA's 192-bit security standard for classified national-security systems) specifies SHA-384 alongside AES-256 and P-384 elliptic curves. Apple and some government certificate authorities issue SHA-384-signed certificates. TLS 1.3 cipher suites include several SHA-384 variants (e.g. TLS_AES_256_GCM_SHA384) used when the peer chooses the strongest available suite. Some implementations of X.509, IKE, and DNSSEC permit SHA-384.

Performance: because SHA-384 is based on SHA-512, it has the same 64-bit-CPU performance edge over SHA-256 for bulk data. On 32-bit hardware SHA-256 wins; on 64-bit hardware SHA-384 is typically 20–40% faster than SHA-256. The extra width costs no CPU time.

Use SHA-384 when a specification mandates it or when you're building a CNSA-compliant system. For general new work, SHA-256 is a lighter, more widely-supported default.

This tool uses the native Web Crypto API (crypto.subtle.digest("SHA-384")), so it matches the bytes produced by sha384sum, openssl dgst -sha384, and Python's hashlib.sha384. Text is UTF-8 encoded before hashing; files are processed directly from ArrayBuffer with no upload.

How to generate a SHA-384 hash

  1. Paste text or pick a file (up to 500 MB).
  2. Pick hex or Base64 output.
  3. Copy for verification or storage.

Features

  • Native Web Crypto — fastest method in a browser.
  • 96 hex chars (48 bytes) or 64 Base64 chars per digest.
  • Text and file hashing, no upload.

Frequently asked questions

When should I use SHA-384?
When a standard or peer system requires it (CNSA Suite, certain TLS 1.3 cipher suites, some government-issued certificates). For new work without those requirements, SHA-256 is a fine default.
Is SHA-384 faster than SHA-256?
On 64-bit CPUs, yes — it's based on SHA-512 which works with 64-bit words natively. On 32-bit hardware SHA-256 is faster. Benchmark your specific workload if performance matters.
Is SHA-384 the same as SHA-256 with more bits?
No. SHA-384 is SHA-512 truncated to 384 bits — it uses a completely different internal state size (64-bit words vs SHA-256's 32-bit words). Don't mix them up.
How long is a SHA-384 hash?
384 bits, which is 48 bytes, 96 hexadecimal characters, or 64 Base64 characters with padding.