Runs entirely in your browser - no upload, no sign-up.
A SHA-384 hash generator turns text or file bytes into a fixed 384-bit fingerprint. In hexadecimal, the result is always 96 characters long. Use it to create or verify checksums when a specification calls for SHA-384. This tool performs the calculation locally with your browser's Web Crypto engine.
Keep Text selected for UTF-8 text, or switch to File for a byte-for-byte local file digest.
Type, paste, load the example, or choose a file. Text hashes update live; files are read only in your browser.
Use lower-case hex, upper-case hex, or Base64. A hexadecimal SHA-384 digest always contains 96 characters.
Copy the result, or open Compare hash and paste an expected hexadecimal checksum for a match verdict.
sha384- integrity value after Base64 encoding.Enter UTF-8 text for an instant digest, or choose a file to hash its exact bytes. You can switch between lower-case hex, upper-case hex, and Base64 without recalculating. The optional comparison field checks a pasted hexadecimal digest without making you inspect all 96 characters by eye.
Your input stays in this tab. Text and files are processed locally. SHA-384 is a one-way digest, not encryption and not a password-storage function.
No. The browser reads your input and computes the digest locally with Web Crypto. This page does not upload the text, file, or resulting hash to calculate it.
Yes. You can hash text and files, change the output encoding, copy results, and compare hexadecimal checksums without an account or usage limit.
The practical limit is your browser's available memory because Web Crypto must receive the whole file at once. Small and moderate files work well; for multi-gigabyte files, use a streaming command-line tool instead.
A SHA-384 digest is 384 bits, or 48 bytes. It is 96 characters in hexadecimal and 64 characters in standard Base64. The length stays fixed regardless of the input size.
No. SHA-384 is a one-way hash rather than encryption, so there is no decryption key. A lookup service may recognize a common input from a precomputed table, but it does not reverse the algorithm.
A trailing newline, an invisible space, different line endings, or a different character encoding changes the input bytes. Text here is encoded as UTF-8, while file mode hashes the file's bytes exactly.
No. SHA-384 is deliberately fast, which makes repeated password guesses cheap. Use a password-hashing algorithm designed to be slow and salted, such as Argon2id, scrypt, bcrypt, or PBKDF2.
Plain SHA-384 creates a public fingerprint anyone can recompute. HMAC-SHA-384 also uses a secret key, so it can authenticate a message. Do not replace HMAC with a hand-built hash of a key and message.