File checksum & hash

Client

Drop a file or choose one from disk. The page reads bytes only in your tab and prints CRC-32, MD5, SHA-1, SHA-256, SHA-384, and SHA-512—useful for verifying installers, images, and release bundles without sending data to a server.

File

?

Reads the file once in your browser, then computes CRC-32, MD5, and SHA family digests. Nothing is uploaded—suitable for release artifacts and download verification.

MD5 and SHA-1 are legacy; prefer SHA-256 or SHA-512 for integrity checks when peers agree on the algorithm.

or pick a file below

or drag and drop here · max ~80 MB

Common use cases

  • Compare a download against a published SHA-256 or SHA-512 on a release page.
  • Double-check that two copies of a file are identical when cloud sync paths differ.
  • Generate a quick MD5 or CRC when a legacy pipeline still references those digests.

Common mistakes to avoid

  • Expecting the same digest from different tools with different normalization

    Line endings and Unicode normalization can change bytes. Always compare digests on the exact file bytes you intend to ship.

FAQ

Is my file uploaded?

No. The file is processed with FileReader and crypto APIs in your browser.

More tools

Related utilities you can open in another tab—mostly client-side.