Home / Hash Checker
If a software publisher provides a checksum for a download, you can use this page to compare it with the file on your computer. A matching SHA-256 value is a useful check that the file has not changed since the reference was created.
SHA-256 is what modern software sites publish and what you should verify against — it is the preferred modern choice for checking file integrity. MD5 still shows up on older download pages and is perfectly good for catching a broken download. SHA-1 sits in between: fine for corruption checks, not for security. This page gives you all of them in one pass, computed locally — your file never gets uploaded anywhere.
A checksum is a fixed-length value calculated from a file's contents. To verify a download, obtain the expected checksum from the software publisher through a trusted channel, calculate the hash of your downloaded file, and compare the two strings exactly. If they differ, do not assume the file is safe or complete; download it again from the official source and investigate the mismatch.
MD5 and SHA-1 are older hash algorithms with known collision weaknesses, so they should not be relied on for modern security or authenticity decisions. SHA-256 is part of the SHA-2 family and is generally preferred when a publisher provides a secure checksum. A matching hash only proves the file matches the reference value; it does not prove the publisher or download source is trustworthy.
Checksum verification is useful after downloading operating-system images, installers, archives, backups and other files for which a publisher provides a digest. It can detect accidental corruption and help identify unexpected changes. Always retrieve the reference hash from the publisher's official website or another authenticated channel.
Use SHA-256 or a stronger modern algorithm when the publisher provides it. Avoid MD5 and SHA-1 for security-sensitive verification.
No. It confirms a match with the reference checksum, but the reference itself must come from a trusted source.
Hash collisions are theoretically possible. They are a known practical concern for MD5 and SHA-1, which is why modern verification commonly uses SHA-256.
When downloading an operating system image, use a checksum published by the software provider whenever one is available, and compare it with the file you downloaded. For background and related resources, see GramFile’s operating systems section. Always verify that the checksum belongs to the exact edition and version of your download.
For software downloads, prefer a SHA-256 checksum published by the software developer over MD5 or SHA-1. Compare the complete digest character for character and make sure it belongs to the exact release and file you downloaded. A mismatch can indicate a damaged, altered or simply different file.
No. A matching checksum proves only that the file matches the reference digest you supplied. If the reference came from a compromised or impersonated source, the comparison cannot establish authenticity. Obtain checksums from the publisher's trusted official channel and use reputable download sources.
Browse related file converters.