SHA-384 Hash Generator

How to use this SHA-384 hash generator

Enter any text, then select Generate hash. For example, entering abc returns its SHA-384 digest.

Use Copy or Export to reuse the generated value. This tool processes text in your browser.

About SHA-384

SHA-384 is a SHA-2 family hash function. It creates a fixed 384-bit digest, written as 96 hexadecimal characters.

Use the algorithm required by your protocol or application, especially when interoperating with an existing system.

What SHA-384 produces

SHA-384 maps any text to a fixed 384-bit digest shown here as 96 hexadecimal characters. The same UTF-8 text produces the same digest. A one-character change normally produces a very different value. Hashing is one-way transformation, not encryption, so no key exists that restores the original text.

How the calculation works

The browser encodes entered text and processes it in algorithm-sized blocks. Padding records the message boundary, then repeated compression steps update an internal state. The final state becomes the digest. Digest length stays fixed whether input is one character or many pages, so a digest is an identifier or integrity check rather than a compressed copy of the message.

Worked example

Enter abc. The complete SHA-384 result is cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7. This example uses the three lowercase ASCII characters with no spaces or line break. ABC, abc , and text ending with a newline are different byte sequences and therefore have different digests.

Assumptions, security, and limitations

SHA-384 belongs to the SHA-2 family specified by NIST FIPS 180-4. Use it when a protocol requires its 384-bit output or security profile; a larger digest does not make an otherwise unauthenticated checksum trusted.

A matching digest can help confirm that two byte sequences are identical, but it does not prove who created a file or message. An attacker who can replace content may also replace an untrusted checksum. Use a digital signature or keyed MAC when authenticity matters. This text tool does not hash uploaded files and does not interpret a hexadecimal digest as input bytes.

Calculation runs in this browser. Input is not submitted to Awesome Tools, but browser extensions, device monitoring, clipboard history, exported files, and shared-device access remain outside this page's control. Verify critical results with the exact algorithm and byte encoding required by your protocol.

Common mistakes

• Comparing text that differs by an invisible trailing newline, Unicode normalization, or character encoding
• Treating an unkeyed digest as proof of authenticity or using a fast general-purpose hash for password storage
• Choosing an algorithm because its output is longer without checking the protocol's required algorithm and security guidance

SHA-384 FAQ

Can two inputs have the same result?

Yes in principle because unlimited inputs map to fixed-length output. Security depends on how hard it is to find useful collisions or preimages, not on collisions being mathematically impossible.

Why does another tool return a different value?

Check encoding, capitalization, spaces, line endings, algorithm name, and output format.

Authoritative sources and related tools

Read NIST's FIPS 180-4 Secure Hash Standard and SP 800-131A transition guidance.

• SHA-256 Hash Generator
• SHA-512 Hash Generator
• HMAC-SHA-256 Hash Generator