What this tool calculates
SHA-512 outputs 512 bits, shown as 128 hexadecimal characters. The long result wraps visually on a narrow screen, but copying and downloading preserve the entire value. A wrapped line is not an inserted newline in the digest.
SHA-512 is not SHA-512/256 and is not interchangeable with SHA-384. A protocol that names a particular digest requires that digest; a different output length is not automatically a compatible upgrade. The file mode uses incremental hashing so a large artifact does not need to be copied into the text editor.
Use the output to fingerprint exact bytes or reproduce a required checksum. It does not encrypt the original content, identify a trusted publisher by itself, or implement a password-hardening function. When troubleshooting a mismatch, first verify algorithm and file version, then encoding and newline conventions if the source is text.
Worked example
UTF-8 · abc · SHA-512
ddaf35a193617abacc417349ae20413112e6fa4e89a97ea20a9eeee64b55d39a2192992a274fc1a836ba3c23a3feebbd454d4423643ce80e2a9ac94fa54ca49f
How to calculate and compare
- Enter the exact text in Input text, or choose Example to load
abc. Text is encoded as UTF-8; spaces and line endings are preserved. - In single-text mode, non-empty input up to 64 KiB updates after a short pause. Click Generate hash for empty input or larger text. Changing the input clears the previous result.
- To check a saved file instead, open File checksum, confirm the algorithm, and choose or drop the file. File mode reads its original bytes and starts automatically.
For line-by-line results, enable One hash per line, choose whether to include empty lines, then click Generate hash. Line mode does not calculate automatically. CRLF, LF and CR separate records and are not included in each line's digest. Duplicate lines retain their original line numbers.
Paste only the complete hexadecimal reference into Compare expected value (optional) and click Check. Letter case and surrounding pasted whitespace are ignored; internal spaces and the wrong length are rejected. Copy retains the full result. TXT and CSV exports include identifiers, algorithm names and digests, not source text or secret keys.
Limits, privacy and next steps
Text is limited to 10 MiB and line mode to 10,000 records, including empty records before filtering. Files are limited to 50 queue entries and 1 GiB each, read sequentially in 2 MiB chunks. These limits protect browser resources; they do not guarantee fast processing on every phone. Cancel if needed. Calculation takes place in the browser, while normal page and asset requests still reach the hosting service.
Keeping SHA-512, SHA-512/256 and SHA-384 separate
A field labelled SHA-512 requires the full 64-byte digest, displayed as 128 hexadecimal characters. SHA-512/256 is a distinct standardized algorithm with different initialization; it is not made by cutting this result to 64 characters. SHA-384 is also a separate function. Retain the complete algorithm label when passing a result to another developer.
For a release artifact, use file mode instead of pasting decoded document text. For a request or fixture, record how the original text became bytes, including newlines. A long digest does not compensate for hashing the wrong representation. Visual line wrapping on a phone is harmless, but a messaging system that truncates the copied value is not; verify the full length at the receiving end.
A direct check of the SHA-512/256 distinction
For abc, ordinary SHA-512 begins with the prefix below. A separate SHA-512/256 calculation gives a different 256-bit digest. The second value is a comparison fixture, not an extra algorithm offered by this page.
SHA-512 / abc / first 64 hex characters only (NOT SHA-512/256):
ddaf35a193617abacc417349ae20413112e6fa4e89a97ea20a9eeee64b55d39a
SHA-512/256 / abc:
53048e2681941ef99b2e29b76b4c7dabe4c2d0c634fc6d46e0e2f13107e7af23
Troubleshooting a long SHA-512 value
| Observed problem | Why it happens | What to do |
|---|---|---|
| Only 64 hex characters arrived | The result was truncated or another algorithm was used | Check for all 128 characters; never pad a truncated result. |
| A SHA-512/256 reference differs | That algorithm has distinct initialization | Use a SHA-512/256 implementation; this page does not provide it. |
| A wrapped digest looks like several lines | Display wrapping is not an input separator | Copy the complete value; this tool does not add wrapping newlines. |