File Checksum
Choose a file and an algorithm.
About this tool
The digest is computed in this browser. The file is not uploaded.
The text hash tool remains for pasted text. This page is for a file.
How to use it
- Open this page and provide the input it asks for.
- Set the options that are visible, then use Hash file.
- Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.
Limitations
- The text hash tool remains for pasted text. This page is for a file.
File bytes, SHA-2 or CRC-32
What is hashed
The page reads the file you pick and hashes those bytes. It does not decode them as text. The menu’s default is SHA-256. SHA-384, SHA-512, and CRC-32 are the other choices. The SHA choices go through Web Crypto and are printed as the algorithm name, a space, and lowercase hex. CRC-32 uses the same residue function as the text checksum page and is printed as eight hex digits without an algorithm prefix. MD5 and SHA-1 are not on this menu. If you still need those for a legacy text paste, the hash page has them, with warnings, and it hashes UTF-8 of a paste rather than a file.
Those three SHA-2 digests are cryptographic hashes. On this page they fingerprint a file so you can compare a download with a published digest. They do not conceal the file. They authenticate it only when someone you trust published the digest on a channel the attacker does not control. A digest sitting in the same folder as the file does not prove the file is genuine. CRC-32 is not in that class. It detects many accidental changes and it is easy to forge. Use the CRC choice to match an old CRC or to notice accidental damage. Keep it off any decision you would call a security check. The page offers it because files still carry that kind of checksum, not because it is sound for authentication.
Paste versus file
A text CRC or a text SHA of a paste can disagree with this page on the “same” document. The file may include a BOM, CRLF, or bytes that are not shown as characters. This page hashes the bytes on disk as the browser read them. The text tools hash UTF-8 of what you pasted. When the publisher said “SHA-256 of the file,” use this page. When they said “SHA-256 of the string,” use the hash page.
What the hex does not claim
A matching digest is not a virus scan, and the container can still be corrupt. There is no HMAC, because no key is involved. It does not upload the file. A missing file or a digest failure shows an error rather than a partial hex string. Choose CRC-32 only for the legacy or accidental-change case. Choose SHA-256 when you are checking a modern fingerprint. Neither choice wraps the file so that a stranger cannot read it.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

