BYTETOOLS

SHA-384 Hash Generator

Generate a SHA-384 hash of any text or file in hex or Base64. Uses the Web Crypto API, so files are hashed locally and never uploaded anywhere.

SHA-384 hash

—

What is the SHA-384 Hash Generator?

SHA-384 is a member of the SHA-2 family that produces a 384-bit digest, written as 96 hexadecimal characters. It is computed as a truncated SHA-512 with different starting values, which makes it immune to length-extension attacks.

  • SHA-384 hashing of both text and files of any type
  • Hexadecimal and Base64 output formats
  • Uppercase or lowercase hex to match any published checksum
  • Live hashing as you type, with a debounce for long text
  • Powered by the browser's native Web Crypto implementation
  • Files stay on your device — nothing is uploaded

How to use the SHA-384 Hash Generator

  1. 1

    Choose Text to hash something you type, or File to hash a document.

  2. 2

    Type or paste your text, or drop a file onto the drop zone.

  3. 3

    Pick hexadecimal or Base64 output.

  4. 4

    Toggle uppercase hex if you need to match a published checksum's style.

  5. 5

    Copy the digest and compare it with the value you were given.

About the SHA-384 Hash Generator

The ByteTools SHA-384 Hash Generator produces a 384-bit digest of any text you type or any file you drop in. Output is available as 96 hex characters or as Base64, which is the form used by subresource integrity attributes and certificate fingerprints.

SHA-384 turns up wherever a security standard asks for more strength than SHA-256 without the full width of SHA-512: TLS cipher suites, the JWT algorithms ES384 and RS384, code-signing manifests, package checksums and government cryptographic profiles all specify it, and it is faster than SHA-256 on 64-bit hardware.

Files are read straight into memory by your browser and hashed with the Web Crypto API. Nothing is uploaded, so you can safely fingerprint a private archive, a build artefact or a downloaded installer without it ever leaving your machine.

Frequently asked questions

What is SHA-384 used for?

It appears in TLS cipher suites, in JWT algorithms like RS384 and ES384, in subresource integrity attributes and in certificate fingerprints. Anywhere a specification wants a security level above SHA-256, SHA-384 is the usual answer.

How is SHA-384 different from SHA-512?

SHA-384 runs the SHA-512 algorithm with different initial hash values and then truncates the output to 384 bits. That truncation is what makes it resistant to length-extension attacks, which plain SHA-512 is not.

Is SHA-384 more secure than SHA-256?

It offers a higher theoretical security margin — 192 bits of collision resistance against 128 — and is faster than SHA-256 on 64-bit hardware. Both are unbroken, so choose based on what your protocol or standard specifies rather than on fear.

How long is a SHA-384 hash?

384 bits, which is 48 bytes. Written as hexadecimal that is 96 characters, and as Base64 it is 64 characters. Anything of a different length is not a SHA-384 digest.

Can I verify a downloaded file with this?

Yes, and that is a good use for it. Drop the file in, compare the digest against the one published by the vendor, and if a single character differs the file has been altered or corrupted in transit.

Related tools