Generate SHA-384 cryptographic hashes from text or file input using the WebCrypto API.
A SHA-384 hash is a 96-character hexadecimal string that changes beyond recognition when even one byte of the input changes. This tool produces that digest for any text you paste or file you pick, computing it in the browser with the WebCrypto API, so nothing you hash is uploaded anywhere. The most common misunderstanding: the digest covers exactly the bytes you enter, so an extra newline, a trailing space, or a different line ending yields a completely different hash, and no hash of any size can be reversed back into the original text.
A concrete input and expected output from the current implementation.
Input
abc
Expected output
cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7
This is the standard test vector for SHA-384 defined in FIPS 180-4: the digest of the three ASCII bytes 0x61 0x62 0x63. Append a newline after the letters and the result changes completely, so the hash is only meaningful for the exact byte sequence you hashed.
Pasted text is encoded as UTF-8 bytes before hashing, so the result depends on the exact characters and whitespace you typed. The WebCrypto digest operation returns 48 bytes for SHA-384, which the tool renders as 96 hexadecimal characters. The same input always produces the same digest, and a single changed byte produces an unrelated one.
The digest length never changes: SHA-384 always returns 384 bits, or 96 hex characters, whether the input is a single byte or a large file. The value is a fingerprint of the exact bytes processed, so it works as a checksum to confirm a file matches a reference digest, or to test whether two copies are byte-identical.
No. SHA-384 is a one-way function: computing the digest from the input is fast, but nothing can recover the input from the digest. For a short, guessable value such as a password, someone can hash likely candidates and compare, which is why raw hashes are not a substitute for a slow password-hashing scheme like bcrypt or Argon2.
Because the input to the hash is the exact sequence of bytes, and whitespace is a byte like any other: 'abc' and 'abc ' hash differently because the byte sequences differ. When reproducing a published checksum, confirm you are hashing byte-for-byte the same content, including line endings and a trailing newline.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.