Choose a file or text input
File SHA-256 calculates a fingerprint over the exact bytes of the selected file. The text SHA-256 generator uses the UTF-8 bytes of entered text, including spaces and line breaks. Both display 64 hexadecimal characters, but their inputs are not interchangeable: opening a file and pasting its contents can change encoding or line endings.
A file name is not part of the fingerprint. Copies with different names and identical bytes produce the same output. Resaving a document can change internal bytes even when its pages appear unchanged. Decide whether your task needs verification of an exact copy or comparison of visible content before choosing an operation.
Prepare an integrity comparison
Obtain the reference fingerprint through the appropriate source channel and keep track of which version it describes. Select the copy you want to verify and wait for the result. Compare all 64 digits rather than checking only the beginning and end. Copy or download the fingerprint to avoid errors introduced by manual transcription.
A different result means bytes do not match that reference. It does not explain what changed or why. Another version, a different encoding or an incomplete download can account for the difference. First confirm that the file and reference are the correct pair before attributing a mismatch to any specific cause or event.
Understand what a fingerprint does not establish
A match checks the copy against your chosen reference. It does not independently establish who created the file, whether it is current or whether its contents are appropriate for your task. A reference from an unverified source needs the same origin review as the file itself before it can support a provenance claim.
The tool does not open the contents as a document, consult a malware database or run an antivirus scan. It does not encrypt files or create passwords. Do not use a fingerprint as a substitute for a digital signature or security analysis. Describe its result precisely as a byte comparison with an identified reference.
Investigate mismatches and retain useful evidence
The file tool accepts up to 100 MiB and requires HTTPS or a secure local origin. Calculation uses browser memory, so a smaller copy helps test the flow when your device struggles. Contents are processed locally and the source file stays unchanged.
For practice, create a UTF-8 file containing abc with no final line break and compare its fingerprint with the same text input. Add a line break to the file and observe the changed result. For a real mismatch, record file, size, reference and version rather than assuming equivalence from the name. Keep those notes with the output to repeat the check on the same copy.
The same bytes produce the same fingerprint
Download sha256-abc.txt and select it in File SHA-256. The sample contains three UTF-8 bytes without a final line break. Hash the text abc in the text SHA-256 generator too, without spaces or line breaks.
abc
Both fingerprints are ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. The file name is not included in the calculation.
Create another copy with a final line break and observe a different fingerprint. This checks the effect of exact bytes; it does not evaluate malware, authorship or whether the file is current.