Tech & Network / Everyday tools
Check the bytes of a file on your device. Paste a trusted expected hash to see whether it matches.
The working, clearly explained
The browser’s Web Crypto implementation computes SHA-256 over the original bytes, with no text conversion. Files stay local. A 64 MiB limit bounds memory use because the file is read into memory. A matching checksum only proves equality with the supplied hash; it does not prove safety or authenticity. Obtain the expected hash through a trusted channel.
An empty file hashes to e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
Changing even one byte normally changes the checksum. Renaming a file alone does not.
One file, at most 64 MiB (67,108,864 bytes). Use a trusted desktop hashing utility for larger files.
No. Processing occurs in a local worker. Clear cancels work and removes the selection and result. Nothing is automatically persisted.
No. Hash equality is not a malware scan, a signature check or a guarantee that the expected hash is trustworthy.