Skip to developer tool
DEVELOPER TOOLKIT SECURITY & ENCODING

Checksum & Hash Calculator

Check whether a downloaded file matches an expected digest, or hash a UTF-8 string for a reproducible comparison. Files are read locally using the browser's cryptographic digest implementation.

Local processing · No account required · Copy and export

Open workspace Read the guide
BUILT FOR THE DETAILS
  1. 01Add your input
  2. 02Inspect & adjust
  3. 03Use your result
Browse developer tools

Workspace

PixelOkay · Developer tools
Computed hash appears here.

SHA-1 is provided only for compatibility, not modern security. Large files use device memory.

How to use Checksum & Hash Calculator

  1. Choose the SHA algorithm that matches the published checksum. Select text or file input and provide the content.
  2. Optionally paste the expected hexadecimal digest. Choose lower- or uppercase display; letter case does not affect comparison.
  3. Calculate the checksum, inspect the match status and save or copy the resulting digest.

When to use this tool

Compare a downloaded file with a publisher-provided SHA checksum, or verify that two local copies have identical bytes. A matching checksum is only as trustworthy as the source of the expected value.

A checksum compares bytes, not filenames

A different newline, byte-order mark or encoding produces different input bytes and therefore a different digest. Text input is encoded as UTF-8. File input hashes the original bytes. SHA-256 outputs 64 hexadecimal characters; SHA-512 outputs 128. Matching hashes help detect changes, but only a trustworthy expected checksum gives the comparison useful provenance.

Worked example

Input text: abc
Algorithm: SHA-256
Digest: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

Limits and output checks

Web Crypto requires HTTPS or a suitable local context. Files are read into memory rather than streamed. SHA-1 is retained for compatibility and should not be selected for new security-sensitive designs. A fast digest is not a password-storage algorithm or a digital signature.

Reference: Web Crypto digest API.

Frequently asked questions

Why is the expected checksum rejected?

Use a hexadecimal digest for the selected algorithm. Remove a filename or label from a checksum-file line before pasting; spaces within the digest are ignored.

Does uppercase output change the checksum?

No. Upper- and lowercase hexadecimal characters represent the same bytes. The comparison ignores letter case.

Why does hashing text differ from hashing a text file?

The file may contain an extra newline, a byte-order mark or another encoding. File mode hashes its exact bytes; text mode hashes the entered UTF-8 text.

Compare with a digest for the same algorithm

Select an algorithm and supply the expected hexadecimal digest without its filename or label. Compare the result with the intended source of that digest.

Scope of this workflow

Matching bytes do not by themselves establish who supplied a file. The operation reads the file into memory rather than streaming arbitrary-size inputs.

SHA Hash Generator — Text & Files, Hex or Base64 · All developer tools · Privacy policy · Contact PixelOkay