Guide
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.
Does hashing upload the file?
No. The browser reads the bytes and uses its built-in cryptographic digest function locally.
Opens the free tool. Your selected files stay in this browser.
Clear answers
Verify file and folder integrity with the browser’s cryptographic API without uploading the selected contents.
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.
-
01
Does hashing upload the file?
No. The browser reads the bytes and uses its built-in cryptographic digest function locally.
Browser-native cryptographic hashing
-
02
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.
Create and verify deterministic folder manifests
-
03
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.
Download output or save both manifests directly to a folder
-
04
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.
Real-life uses
Practical ways to use File Hash and Folder Checksum Calculator
These examples show where the tool can help and what still needs a deliberate human check before the result is used or shared.
Verifying a downloaded file
Compare a local SHA-256 value with a checksum published through a trustworthy independent source.
Checking a transferred folder
Create a deterministic manifest before copying an archive and verify the destination folder for missing, added, or changed files.
Recording release artifacts
Publish checksums alongside software, datasets, media, or document bundles so recipients can verify exact bytes.
Worked example
Checking a software installer after download
The vendor publishes a SHA-256 checksum on its official release page.
Before
The filename alone cannot verify the bytes
- The installer appears to have the expected name
- The trusted checksum comes from a separate official source
After
The calculated value is compared exactly
- Hash the selected installer locally
- Compare every hexadecimal character and investigate any mismatch
What you receive: a locally calculated checksum or folder-manifest report; a match proves byte equality, not that the content is safe.
Four local steps
Does a matching hash prove a file is safe?
- 01
Browser-native cryptographic hashing
Choose one file for a single checksum, or start a folder manifest from the batch integrity panel.
- 02
Create and verify deterministic folder manifests
For a file, select the trusted algorithm and optionally paste an expected checksum.
- 03
Download output or save both manifests directly to a folder
For a folder, create new JSON and .sha256 manifests or choose an existing JSON manifest to verify.
- 04
Browser-native cryptographic hashing
Review every reported difference before downloading or saving the results.
Final check
Check the result before you use it
Verification belongs in the workflow. Review the downloaded result itself rather than relying only on the preview inside the tool.
- Obtain the expected checksum or manifest from a trustworthy independent source.
- Compare the complete value, not a short prefix.
- Treat every missing, added, changed, or unreadable file as a difference requiring review.
Clear answers
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.
- 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.