SHA-512 Generator
Generate a 512-bit SHA-512 digest — 128 hexadecimal characters. Built on 64-bit words, so it is frequently faster than SHA-256 on modern hardware despite producing twice the output.
{{ textCount }}
{{ textError }}
{{ r.value }}
{{ legacyNames }} {{ legacyNames.indexOf(' and ') === -1 ? 'is' : 'are' }} selected. Practical collisions are public for both, so treat the result as a checksum for spotting accidental corruption — not as evidence that a file is authentic.
Drop files here to hash them
Up to 100 files · any size · read in 4 MB chunks, never uploaded
Files are read, not uploaded. Each one is streamed through the hash function in chunks straight from disk, so a multi-gigabyte image never lands in memory and never leaves your device.
{{ f.error }}
{{ r.value }}
The key never leaves this page. It is not sent to a server, not saved to local storage, and not written into the exported files.
{{ hmacError }}
{{ hmacResult }}
HMAC is not a hash with the key glued on the front. It runs the key through the hash
twice with two different pads, which is what makes it resistant to the length-extension
attacks that break a naïve hash(key + message).
Drop the file you want to check
Hashed in your browser · never uploaded
{{ lengthProblem || vError }}
Hash matches
The {{ vResult.label }} digest of {{ vFile.name }} is identical to the hash you supplied, so this is the file that checksum describes. Letter case and surrounding whitespace were ignored.
Both {{ vResult.computed }}
Hash does not match
This file is not the one that checksum describes. Either the download is incomplete or corrupted, or the file has been altered. Downloading it again is the first thing to try.
Computed {{ vResult.cHead }}{{ vResult.cChar }}{{ vResult.cTail }}
Expected {{ vResult.eHead }}{{ vResult.eChar }}{{ vResult.eTail }}
First difference at character {{ vResult.diffAt + 1 }}.
Paste a hash into both boxes to compare them.
Hashes match
Both are the same {{ cmpResult.len }}-character value, so they identify identical content.
Ignored while comparing: letter case, spaces, line breaks, and any
sha256:-style prefix.
Both {{ cmpResult.a }}
Length {{ cmpResult.len }} — consistent with {{ cmpResult.guess }}.
Hashes are different
These are different lengths — {{ cmpResult.a.length }} and {{ cmpResult.b.length }} characters — so they are digests from two different algorithms, and comparing them tells you nothing about the content.
These two digests differ, so they describe different content.
Hash A {{ cmpResult.aHead }}{{ cmpResult.aChar }}{{ cmpResult.aTail }}
Hash B {{ cmpResult.bHead }}{{ cmpResult.bChar }}{{ cmpResult.bTail }}
First difference at character {{ cmpResult.diffAt + 1 }}.
Text, files and secret keys are hashed in your browser. Nothing you enter is ever uploaded to a server.
About SHA-512
SHA-512 produces 512 bits, written as 128 hexadecimal characters. It belongs to the same SHA-2 family as SHA-256 but works on 64-bit words and 1024-bit blocks rather than 32-bit words and 512-bit blocks.
Longer is not meaningfully more secure
A collision search against SHA-256 already needs on the order of 2128 operations, which is not a number that becomes reachable with better hardware. Doubling the digest does not make a realistic attack harder, because there was no realistic attack. Choose SHA-512 when a specification demands a particular digest size, or for speed — not for extra safety margin.
Why it can be faster than SHA-256
It moves 1024 bits per block using 64-bit arithmetic, so a 64-bit CPU processes more data per operation despite doing more rounds. On 32-bit hardware, where each 64-bit operation has to be emulated with two 32-bit ones, the comparison reverses sharply.
SHA-512/224 and SHA-512/256
Separate FIPS-standardised variants: SHA-512 with different initial values, truncated to 224 or 256 bits. They combine 64-bit speed with a shorter digest and, because of the truncation, immunity to length extension. They are not offered here because they are rarely requested and are easily mistaken for plain SHA-256 — the digests differ, so confusing them causes a mismatch that is hard to diagnose.
See also the SHA-256 generator.
Frequently asked questions
What does SHA-512 produce?
512 bits, written as 128 hexadecimal characters.
Is a longer hash more secure?
Only up to a point. SHA-256 already puts a collision search far beyond reach, so SHA-512 does not make a realistic attack meaningfully harder. Its longer output matters when a specification demands a particular digest size.
Why can SHA-512 be faster than SHA-256?
It processes 1024-bit blocks using 64-bit arithmetic, so on a 64-bit CPU it moves more data per operation. On 32-bit hardware the position reverses.
What is SHA-512/256?
A distinct variant: SHA-512 with different initial values, truncated to 256 bits. It gets 64-bit speed with a 256-bit output. It is not offered here because it is rarely requested and is easy to confuse with plain SHA-256.