Encoding & Security

File SHA-256

Calculate a local file’s SHA-256 without uploading it.

Read the guide

Run the tool

The file is processed in your browser. This tool does not upload the file to JVR Software.

More information

Back to the tool

What it is and when to use it

File SHA-256 measures the exact bytes of a selected file and gives you a reproducible fingerprint. It is useful for comparing downloaded releases, checking whether a file changed during a transfer, deciding whether two copies are byte-identical, and recording the fingerprint of an archive before storage.

How it works

The browser reads the selected file into memory and uses Web Crypto to compute a SHA-256 digest. The output is 64 hexadecimal characters. Names, filesystem timestamps and folder locations have no effect. Content stored inside the file, including metadata that forms part of its bytes, affects the result.

How to use it

  1. Select the exact file you received or expect to distribute.
  2. Compute its fingerprint and obtain the expected SHA-256 from the publisher or another trusted record.
  3. Compare all characters manually or paste both into Checksum Verify.

Worked example

Suppose a release provides package.zip and publishes a SHA-256 value for that exact ZIP. Select the ZIP you downloaded, with its bytes intact. Hashing the extracted folder contents or making a fresh ZIP of the same files gives a different object to compare.

Reading the result

A digest match is strong evidence that the bytes are identical to the file represented by the reference. A mismatch can come from the wrong version, a partial download or any byte change. Download again from the legitimate publisher if the first copy looks incomplete, and compare against the correct release entry.

Common mistakes and limits

Large files can use substantial browser memory because this implementation reads the bytes together. For multi-gigabyte images, use a local file hashing utility instead. Obtain the reference via a trustworthy channel, since a file and digest from the same untrusted source can agree while still being unsafe.

Further reading