File SHA-256 checksum

File SHA-256 checksum: uses and practical guidance

A SHA-256 checksum represents file bytes as a string of sixty-four hexadecimal digits. It helps determine whether a copy matches a reference computed over the same content. Filename, extension and filesystem date do not enter the calculation, so renaming alone preserves the checksum. Changing bytes, even through one line ending or metadata stored inside the file, normally produces a different checksum. The tool reads bytes without opening the file as a document or interpreting its format. This distinction makes checksum comparison useful even when two files look similar in their ordinary viewers.

The reference matters as much as the calculation. Matching a checksum published by a trusted source checks integrity relative to that reference. It does not independently identify the author or certify safety. A harmful file also has a valid SHA-256 checksum. This page does not query malware databases, verify digital signatures or replace the originating service's download-authentication procedures. Compare the entire string instead of only its first characters, and confirm that the reference belongs to the same file and version. A mismatch establishes different bytes rather than explaining which change occurred or whether it was intentional.

Text files require attention to exact bytes. Editors may store the same visible text with different encodings, initial markers or line endings. The abc example contains three bytes and no trailing newline. If an editor appends one, the checksum correctly changes. Resaving an image or PDF can likewise change metadata or compression while preserving a similar appearance. The text SHA-256 tool and this file tool can match only when file bytes correspond exactly to the encoding used by the text operation. Retain the original file when exact comparisons are needed instead of assuming a resaved copy preserves its checksum.

Calculation runs in the browser and requires HTTPS or a secure local environment with cryptography available. Files up to one hundred MiB, or 104,857,600 bytes, are supported. The browser loads content into memory for this operation, so use smaller files on devices with limited resources. An empty file is valid and has a defined checksum too. Wait for calculation to finish before copying or downloading the string. Retain the filename and source reference alongside it to avoid comparing the wrong versions later. Selecting another file or resetting removes the old result from the active download controls rather than keeping a stale checksum ready for accidental reuse.