Start with a checksum you trust
Get the expected checksum from the software publisher, a signed release page, or another channel you already trust. A value copied from an unrelated comment or mirror cannot establish that the original download was authentic.
1. Match the provider's algorithm exactly
A SHA-256 value cannot be compared with a SHA-512 value for the same file. Read the label next to the published checksum, then use that same algorithm. The strings have different expected lengths.
Use SHA-256 when the source publishes SHA-256; it is a common modern checksum format.
Copy the entire hexadecimal value, not a shortened display or a filename beside it.
Keep the download and the source page together until the comparison is complete.
2. Calculate and compare without uploading the file
With File Hash Generator, select the matching SHA algorithm, paste the expected value if you have one, and choose the downloaded file. The tool reads supported files in the current browser tab and reports whether the calculated and expected values match.
A simple SHA-256 workflow
- 1. Find the publisher's SHA-256 checksum for the exact release you downloaded.
- 2. Select SHA-256 and paste the complete expected value.
- 3. Add the downloaded file and read the match result before you open or install it.
3. Treat a mismatch as a stop sign
Values match
The file's bytes match that expected value. Continue with the provider's other instructions, such as code-signing or installation guidance.
Values do not match
Do not try to edit or rename the file to make it fit. Recheck the release and algorithm, then download a fresh copy from the trusted source.
A matching hash does not prove that a file is safe
It only proves agreement with the expected checksum. If the publisher itself distributed a malicious or unwanted file, its genuine checksum can still match. Use normal software-source, device-security, and organisational review practices as well.
Common questions
Can I compare only part of a checksum?
No. A shortened value is useful for display but cannot give the same assurance as comparing the entire published value. Copy the full hexadecimal checksum.
Does changing a filename change its hash?
No. A file hash is calculated from its bytes, not its visible name. Any content change normally produces a different result.
Why does a checksum tool not include MD5?
MD5 has known collision weaknesses. Use the modern algorithm published by the file provider; this tool offers SHA-256, SHA-384, and SHA-512.
Are my files uploaded for hashing?
No. File Hash Generator reads supported files locally in the browser. Check its stated limits before choosing a file.
Keep the original download until you have confirmed the result. If the values differ, remove the untrusted copy using your usual device process and obtain a new copy from the verified source.