The documented digest is calculated over an empty byte sequence. It is not the digest of a space, a newline, a byte with value zero, or the word empty. A new text file can contain a byte-order mark or an automatically inserted newline; check its byte length.
Choose Try empty file to calculate this result locally and compare it against the published value. This is an example file, not a verification of your own file.
Reproduce it independently
On macOS or Linux, the command below passes no bytes to shasum. To check a saved file instead, run shasum -a 256 followed by its local path. The result must have 64 hex characters.
printf '' | shasum -a 256
Why an empty file still has a digest
SHA-256 includes padding and the original message length as part of its definition. Even an input with no data bytes therefore produces a full 256-bit result. The algorithm is specified in NIST FIPS 180-4.
Do not trim or decode a real file before hashing it. The file workbench reads its exact bytes; the expected-digest field only ignores outer whitespace and letter case. A checksum match needs a trusted expected value to be useful.
It is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855. This is the digest of zero bytes, not of the word empty.
Is no file selected equivalent to a zero-byte file?
No. No selection means nothing has been read. Try empty file creates a local zero-byte example and compares its result.
Why does an empty text editor document produce a different digest?
It may contain a byte-order mark or a final newline. Check the saved byte length rather than whether the editor looks blank.
Does the byte 00 count as empty?
No. A zero-valued byte is one byte. Empty input has length zero and contains no bytes of any value.
How do I reproduce the result from a shell?
Use printf '' | shasum -a 256 on a system with shasum. Unlike echo, printf with an empty format adds no newline.
Why does SHA256 produce output for zero bytes?
The hash algorithm includes padding and an encoded input length. The defined digest exists even when the original message is empty.
Can a batch contain empty and nonempty files?
Yes. Each selected file is hashed separately. A zero-byte file is valid; match manifest entries by exact filename as for other files.
Does an empty file match prove my download succeeded?
No. A supposed installer that is zero bytes is probably not the intended artifact. Compare its expected size and a checksum from the trusted publisher.