NullKit

Files · Free browser tool

File Hash and Folder Checksum Calculator

Calculate SHA-1, SHA-256, SHA-384, or SHA-512 for a file locally, or create and verify a SHA-256 manifest for an entire folder.

Runs on this device No file upload Free to use

Private workspace

Verify file and folder integrity with the browser’s cryptographic API without uploading the selected contents.

Local processing

Ready.

Batch integrity

Folder manifests

Create or verify a SHA-256 manifest for a folder without uploading its files.

Up to 1,000 files, 2 GiB total, 250 MiB per file, and 20 folder levels. Cancellation takes effect between files.

Choose a file to begin

Verify file and folder integrity with the browser’s cryptographic API without uploading the selected contents.

What this tool does

A focused job, with a visible boundary.

Verify file and folder integrity with the browser’s cryptographic API without uploading the selected contents.

01

Browser-native cryptographic hashing

02

Create and verify deterministic folder manifests

03

Download output or save both manifests directly to a folder

Know the limits

Local does not mean unlimited.

Browser processing protects the file from an upload workflow, but the browser, device, output format, and selected settings still matter.

  • A matching checksum verifies bytes, not whether a file is safe or trustworthy.
  • The expected checksum or manifest must come from a trustworthy independent source.
  • Folder processing is limited to 1,000 files, 2 GiB total, 250 MiB per file, and 20 folder levels.

Four local steps

How to use file hash.

  1. 01

    Choose one file for a single checksum, or start a folder manifest from the batch integrity panel.

  2. 02

    For a file, select the trusted algorithm and optionally paste an expected checksum.

  3. 03

    For a folder, create new JSON and .sha256 manifests or choose an existing JSON manifest to verify.

  4. 04

    Review every reported difference before downloading or saving the results.

Clear answers

File hash questions.

Does hashing upload the file?

No. The browser reads the bytes and uses its built-in cryptographic digest function locally.

Does a matching hash prove a file is safe?

No. It proves the bytes match the expected checksum. If the expected value or original file is malicious, the hashes can still match.

Which algorithm should I use?

Use the algorithm published by the trusted source. SHA-256 is the most common default for modern file-integrity checks.

Can I verify a whole folder later?

Yes. Save the generated JSON manifest, then choose it and the folder again to find changed, missing, added, or unreadable files.