SHA384 File Hash Calculator
Compute the SHA-384 checksum of any file directly in your browser. Drop a file to verify integrity instantly — no upload, no server, complete privacy. Output is a 96-character hex string.
Related Hash Tools
Frequently Asked Questions
How do I verify a SHA384 file checksum?
Is my file sent to any server?
How do I check SHA384 on the command line?
sha384sum filename. macOS: shasum -a 384 filename. Windows: certutil -hashfile filename SHA384. PowerShell: Get-FileHash filename -Algorithm SHA384.When would I need to verify a SHA-384 checksum?
About SHA384 File Hash Calculator
The YoSin Tools SHA-384 file hash calculator computes the SHA-384 checksum of any file entirely within your browser. SHA-384 produces a 384-bit (96 hex character) digest. It uses the same internal computation as SHA-512 — the fast 64-bit SHA-2 core — with different initialization values and a truncated 384-bit output, making it efficient on 64-bit hardware.
SHA-384 File Checksums in the Wild
SHA-384 checksums are less common than SHA-256 but appear in several specific contexts: TLS cipher suites using the AES-256-GCM-SHA384 configuration, NSA Suite B compliant software distributions, some certificate authority intermediate certificate chains, and FIPS 140-2/3 compliant cryptographic modules. When verifying a file with a 96-character hexadecimal checksum, SHA-384 is the algorithm to use.
Performance Characteristics
Because SHA-384 uses the SHA-512 core, it performs identically to SHA-512 on all platforms — the only difference is output truncation. On 64-bit hardware, this makes SHA-384 faster than SHA-256 for the same 384-bit security level. On 32-bit systems, SHA-256 has better performance.
Comparing Digest Lengths
SHA-384 produces 96 hex characters, compared to 64 for SHA-256, 128 for SHA-512, and 40 for SHA-1. When comparing a downloaded file's hash against a published checksum, count the characters to determine which algorithm was used: 32=MD5, 40=SHA-1, 56=SHA-224, 64=SHA-256, 96=SHA-384, 128=SHA-512.
Privacy
All processing is local. No file data is transmitted to any server, logged, or retained. This tool is safe to use with sensitive or proprietary files.