Verify MD5, SHA-1, SHA-256, SHA-384, SHA-512, or CRC32 checksums locally without uploading the selected file.
Selected text and files are processed locally. Hashes and checksums detect matching bytes; they do not prove that a file is trustworthy unless the expected digest came from a trusted source.
Hash multiple local files and optionally match checksums by filename.
| File | Algorithm | Digest | Result |
|---|
connects text/file digests, checksum verification and HMAC workflows. Hashes compare exact bytes; HMAC additionally depends on a shared secret key.
Fast hashes such as SHA-256, SHA-1 and MD5 are not password-storage schemes. Production password storage should use a purpose-built slow password hashing/KDF design with salts and reviewed parameters; legacy algorithms remain here only for compatibility and checksum workflows.
Use the tool above first. These notes explain how to interpret, verify and bound the result without displacing the primary workflow.
A checksum only matches when the same algorithm is used on the same bytes. SHA-256, SHA-512, SHA-1, MD5 and CRC32 produce different digest lengths and properties, so the expected value must identify the algorithm used by the publisher or source.
If the locally computed digest matches a trusted expected digest, the file bytes match the value represented by that digest. This is useful for download integrity and detecting accidental modification.
Integrity is not the same as authenticity. A malicious file and a maliciously supplied checksum can match perfectly. Obtain expected hashes from a channel you trust, and use digital signatures when publisher identity must be authenticated.
For multiple downloads, pair each expected digest with the correct filename and algorithm before comparing. Whitespace, uppercase/lowercase hexadecimal formatting and filename prefixes should be normalized carefully without changing the digest itself.
Browser-local hashing avoids uploading the file contents, but very large files still consume local memory, CPU time and battery. Keep the tab open until hashing completes and use an operating-system or streaming hash utility when files exceed what the browser handles comfortably.
WebToolArc