SHA-256

What does SHA-256 mean?

SHA-256 is a cryptographic hash function that turns any input, whether a short password or a 200-page PDF, into a 256-bit value usually written as 64 hexadecimal characters. It belongs to the SHA-2 family published by the US National Institute of Standards and Technology, and it is one of the most widely used hashing algorithms in software, security and e-signatures.

The function has a few properties that make it useful. It is deterministic, so the same input always gives the same output. It is one-way, meaning you cannot practically reconstruct the input from the output. And it is collision-resistant: finding two different files with the same SHA-256 hash is considered computationally infeasible with current technology. A tiny change to the input produces an output that looks completely unrelated.

Here is how that plays out for a small business owner. She signs a supplier agreement and receives the final PDF along with its SHA-256 value. Months later, a colleague forwards a copy from a shared drive. She runs the file through a hashing tool, or a verification page, and compares the result. Identical strings mean identical files; any difference means the copy has been altered, even if the change is invisible on screen.

The biggest misconception is that SHA-256 is encryption. It is not. Encryption is reversible with a key and is designed to keep data secret. Hashing is not reversible and does not hide anything; the original document remains readable. SHA-256 also carries no identity information on its own. It proves that a file is unchanged, not who signed it.

In signing workflows, SHA-256 is used to create a document hash for the final file. That hash can be recorded in an audit trail, printed on a certificate of completion, or, in PKI-based digital signatures, signed with a private key to form a tamper-evident seal. Older functions such as MD5 and SHA-1 are no longer considered safe for this purpose because practical collision attacks have been demonstrated against them, which is why SHA-256 has become the common default for document integrity. You can compute it yourself with built-in commands on macOS, Windows and Linux.

Our take: SHA-256 is boring in the best way. It is well studied, free to use and supported by nearly every operating system. When a vendor mentions it, the right question is not whether they use it but whether they let you check the hash yourself.

eSignSimple computes a SHA-256 hash of each completed PDF, shows it on the certificate of completion, and offers a public /verify page where anyone can confirm that a file matches the signed original.

What is an example of SHA-256?

When the last signer completes a purchase agreement in eSignSimple, we compute the SHA-256 hash of the final PDF, a 64-character string such as 3a7bd3e2..., and store it (it also appears in the completion email). A year later the buyer's lawyer runs the file through /verify and gets a match, proving not a single byte has changed.

How does SHA-256 work, without the maths degree?

SHA-256 processes data in 512-bit blocks. It first pads the input so its length fits a whole number of blocks, including the original length at the end. It then starts from eight fixed 32-bit values and, for each block, runs 64 rounds of simple operations: additions, bit rotations and logical mixing functions that blend the block's contents into those eight values. The output of one block becomes the starting point for the next. After the last block, the eight values are joined into the final 256-bit result.

The design goal is that every input bit affects every output bit in a way that looks random. This is called the avalanche effect: flip one bit of a 50-page contract and roughly half of the 256 output bits change. That is what makes the hash useful as a fingerprint. Small edits do not produce similar hashes that could be compared to guess what changed; they produce a completely different value.

What does a SHA-256 hash look like in practice?

Hashing the three letters abc gives ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. Hashing an empty file gives e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855; if you ever see that value for a contract, the file you hashed was empty, which usually means a broken download. A 200-page PDF produces a value of exactly the same length, 64 hexadecimal characters, because the output size never depends on the input size.

When comparing two hashes by eye, check the whole string, not just the first and last few characters. Accidental near-matches between different files do not happen with SHA-256, but people do sometimes compare the wrong two values, such as the original upload hash with the final file. On an eSignSimple certificate the printed value is the original document's fingerprint; the final file's fingerprint is the one our /verify page checks.

Is SHA-256 safe against quantum computers?

For the way it is used in document integrity, current expert consensus is yes, with a comfortable margin. The best known quantum attack on hash functions, Grover's algorithm, roughly halves the effective strength for finding an input that matches a given hash, which would leave SHA-256 at around 128-bit security. That is still far beyond what any foreseeable machine could break. Quantum computers pose a much more serious threat to the public-key algorithms used in certificate-based digital signatures than to hash functions.

That distinction is practical. A recorded SHA-256 fingerprint of a signed contract should remain a reliable check for many years. Certificate-based signatures may need to migrate to new post-quantum algorithms over time, which is one reason long-term archives add fresh timestamps periodically. If you need a larger safety margin for a specific purpose, SHA-384 and SHA-512 from the same family are available, but for checking whether a PDF has changed, SHA-256 is the widely accepted standard.

SHA-256 vs MD5, SHA-1, SHA-512 and SHA-3

MD5 and SHA-1 are older functions with demonstrated practical collision attacks, meaning researchers have created two different files with the same hash. They are still sometimes used as quick checksums for accidental corruption, but should not be relied on to show a document was not deliberately altered. SHA-512 is a larger member of the SHA-2 family and is equally sound. SHA-3, standardized later by NIST, uses a different internal design and serves as a backup family should a weakness ever appear in SHA-2. None of the known results threaten SHA-256 for document integrity today.

Which terms are related?

• Digital signature: A digital signature is a cryptographic mechanism that uses public key infrastructure to prove who signed a document and that it has not changed.
• Document hash: A document hash is a fixed-length fingerprint computed from a file's contents; any change to the file produces a different hash.
• Tamper-evident seal: A tamper-evident seal is a cryptographic seal on a PDF that shows whether the document has been changed in any way after it was signed.
• Public key infrastructure (PKI): PKI (public key infrastructure) is the system of certificate authorities, digital certificates and key pairs that binds public keys to real identities.