SHA-512 Hash Generator

What this tool does

SHA-512 Hash Generator produces the 512-bit SHA-512 and 384-bit SHA-384 digests from FIPS 180-4 for text, hex or Base64 input and files of any size. Files are streamed with progress, every line of a list can be hashed separately, and results can be verified or exported as a checksum file.

SHA-512 is the largest member of the SHA-2 family, producing a 512-bit digest written as 128 hex characters. It operates on 64-bit words and 1024-bit blocks, which gives a larger security margin than SHA-256 and often better speed on 64-bit processors. It appears in Linux password hashing schemes ($6$ in /etc/shadow), in Ed25519 signatures internally, in package registries such as npm, whose integrity fields use sha512-<Base64>, and in many vendor checksum lists.

This tool calculates SHA-512 and SHA-384 exactly as FIPS 180-4 defines them. SHA-384 is SHA-512 computed with different initial values and truncated to 384 bits, the common choice for Subresource Integrity and TLS cipher suites. Text is converted to UTF-8 unless you provide hex or Base64 bytes. Files are streamed in 4 MB chunks with progress, lists can be hashed line by line, and the Base64 output format lets you build npm-style and SRI integrity strings directly. Everything is computed on your device.

How to use SHA-512 Hash Generator

1. Choose Text or Files as the input source.
2. Enter text, or drop one or more files.
3. Select SHA-512 or SHA-384 as the Algorithm.
4. Pick the Output format: hex for checksum lists, Base64 for integrity attributes.
5. Optionally paste a reference value into “Compare with expected hash”.
6. Copy the hash or download the checksum file.

Tips for better results

• An npm package-lock integrity value is “sha512-” followed by the Base64 SHA-512 of the package tarball.
• For Subresource Integrity, SHA-384 in Base64 is the value most CDNs publish.
• SHA-512/256 is a separate standard variant with its own initial values; it is not simply the first half of SHA-512.
• Long hex strings are easy to misread; rely on the Match badge rather than comparing by eye.

Common use cases

• Verifying downloads from projects that publish SHA512SUMS files.
• Generating integrity attributes for script and stylesheet tags.
• Checking an npm, Yarn or pnpm integrity value against a tarball.
• Creating strong content fingerprints for archives and backups.

Common mistakes to avoid

• Truncating SHA-512 output by hand and calling it SHA-512/256; the real variant uses different constants.
• Assuming SHA-512 alone is a good password hash. The Unix $6$ scheme adds a salt and 5,000 or more rounds for that reason.
• Mixing up hex and Base64 when pasting into an integrity attribute, which must be Base64.