File to SHA-384.
Drop a file and read its SHA-384 digest at once, in your browser. SHA-384 is SHA-512 cut to 384 bits, the 192-bit security level TLS suites and Subresource Integrity use; the file is read on your machine and never uploaded.
File to SHA-384.
Need the UI around it? With Pro, your AI agent builds the form, the result card and the rest of the page from a prompt.
Get ProHow it works
4 steps, no account. It runs in your browser and nothing is uploaded.
Drop a file
Drop it onto the pane or choose it with the button; anything up to 1 GB is read in your browser.
Read the digest
The SHA-384 digest appears at once, as hex, Base64 or Base64url; switch to SHA-1, SHA-256, SHA-384 and SHA-512 in the bar.
Verify against a published checksum
Paste the digest the publisher lists and the tool says whether the file matches.
Copy or download
Copy the digest, or download it as a line a checksum tool can read.
Related tools
More hash generators. Every one free, in the browser.
Pricing
Build it with Pro
The tool is free. Pro adds 6,000+ blocks, premium templates and the MCP server, so your AI editor builds the product around it.
4.9/5 out of 5 · 150+ reviewsfrom 150+ founders and developers.
- Secure checkout via Stripe
- Code lives in your repo
- Keep what you've shipped if you cancel
- License terms
Questions and answers
Before you trust the result: what to know about the format, the limits, your data and the tools next to it.
SHA-384 is SHA-512 with different starting values and the output cut to 384 bits (48 bytes, 96 hex characters). Published with the rest of SHA-2 in 2001, it is the hash behind the TLS cipher suites that end in _SHA384 and one of the three allowed in Subresource Integrity.
Yes: 192-bit collision resistance, the level NSA's Commercial National Security Algorithm suite requires for top secret, and no known attack. Because the 512-bit state is truncated, a digest cannot be extended to a longer message, which SHA-256 and SHA-512 digests can.
On a 64-bit CPU it is usually faster than SHA-256 for long inputs, since SHA-512 works on 64-bit words and processes 128 bytes per block against SHA-256's 64. With Intel and ARM SHA-256 instructions in play, SHA-256 pulls ahead. Either way, a gigabyte takes about a second.
Choose SHA-384 when a policy names it (CNSA, FIPS profiles, a TLS suite) or when you want the length-extension immunity without reaching for SHA-3. Choose SHA-256 for everything else: it is what the tooling, the lockfiles and the APIs around you expect.
Nothing leaves your browser. The file is read on your machine and hashed there, by the browser's Web Crypto API or a WebAssembly build of SHA-384 loaded on first use; the page makes no request with its bytes. You can load the page, go offline and keep hashing.
Drop the file onto the pane or choose it with the button. It is read into memory and hashed at once, with no size steps and no upload progress because there is no upload. Files up to 1 GB work; a 100 MB file takes well under a second on SHA-384.
Paste the digest the publisher gave you into the Verify field, in hex of either case, with or without spaces, colons or a 0x prefix, or in Base64. The tool says whether it matches the file you dropped. A match means the bytes are exactly the ones that were published.
Hex by default, 96 characters; Base64 and Base64url are one click away and re-encode the same 48 bytes. The download button saves a line in the `digest filename` form that sha256sum-style tools read.
Yes: turn on HMAC and enter the secret, and the file is signed with HMAC-SHA-384 rather than hashed, the same construction a server uses to sign an upload or a webhook payload.
No. The "File to SHA-384" tool is free and opens without a sign-in, an account or an install.
Nothing. The "File to SHA-384" tool holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.
The toolbar switches to SHA-1, SHA-256, and SHA-512 without leaving the page. Each one reads the same input, so you can compare digests side by side.
SHA-384 runs on the browser's own Web Crypto API, so there is nothing to download and it is the fastest path.
Yes: the SHA-384 hash generator page has the same algorithms and options and opens on the text box. This page opens on the file pane.
Not on its own. SHA-384 is built to be fast, and fast hashes are cheap for an attacker to guess against. Passwords need a salted, deliberately slow hash: use Argon2id, Argon2d, and bcrypt from the hash generators, which draw a fresh random salt each time.
Closest to the "File to SHA-384" tool: SHA-384 hash generator, SHA3-384 hash generator, Keccak-384 hash generator, BLAKE2b hash generator. Each opens on its own page, free and in the browser.
The "File to SHA-384" tool is one of 64 in its group. The group's page, /tools/hash, lists them all.
The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.
4.9 out of 5 from 150+ developers
Build the product around it
Every block, template and icon, installed by your AI agent in your theme. The tools stay free.
Get Pro





