File SHA-256 checker
Calculate a file fingerprint locally and compare it with a reference hash.
Compare the file with the right reference.
SHA-256 converts the selected bytes into a 256-bit digest, displayed as 64 hexadecimal characters. This checker calculates that value in browser memory. If you provide a reference, it validates the format and compares the complete value without distinguishing uppercase from lowercase.
Use the checker in this order
- Obtain the reference hash through the trusted publisher’s official release documentation for the exact file.
- Choose the file you want to compare. You do not need to open or run it.
- Paste the reference value, if available, and calculate. Investigate a mismatch before installation.
Make the comparison meaningful
A reference for a ZIP archive cannot be compared directly with a file extracted from it. Different versions, CPU variants, languages or formats may produce different hashes. An adversary who supplies both a file and its matching hash can still supply malicious software. File identity and trust in the source are separate questions.
Memory and file limits
The browser API reads the whole file into memory. This tool therefore limits selection to 100 MiB, equal to 104,857,600 bytes. That is a product memory limit, not a cryptographic limit. Use a trusted local hashing utility for a larger file, a confidential document or an environment where browser memory is constrained.
Does a match mean virus-free?
No. The tool does not scan, execute, unpack or validate a digital signature. A match is a file-content comparison against the value you supplied. It does not establish that the source or software is trustworthy.
Can I hash an empty file?
Yes. A zero-byte file has a valid SHA-256 digest. Selecting no file is different and produces an input error.
Why is a reference rejected?
Paste only the 64 hexadecimal characters. Remove a filename, algorithm label or command-output prefix. Leading and trailing whitespace is ignored; an incomplete value is rejected.
Read what a matching file hash actually proves ↗
Method reference: MDN SubtleCrypto.digest documentation. Tool method reviewed October 27, 2026.