Compute SHA-256 (or MD5, SHA-1) for every entry inside a ZIP and export the manifest as CSV or .sha256sums. Tamper-evident, audit-ready, browser-native.
Per-job file size, entry count, and batch caps for Checksum Generator. Limits apply to every Archive tool in JAD Apps; upgrade for larger uploads and bigger batches.
| Tier | Max archive size | Max entries / archive | Max files per batch |
|---|---|---|---|
| Free | 47.7 MB | 500 | 1 |
| Pro | 476.8 MB | 50,000 | 20 |
| Developer | 1.86 GB | 50,000 | 20 |
Drop your archive
We extract each entry and run Web Crypto's digest() over its bytes
Download a CSV manifest plus a .sha256sums file usable with the sha256sum -c command
0 bytes uploaded. Per-File Checksum Generator runs entirely in your browser using fflate, zip.js, and libarchive WASM. Your archive files never leave your device.
CRC32 detects accidental corruption. SHA-256 detects deliberate tampering — it's cryptographically infeasible to produce a different file with the same SHA-256. For tamper detection always use SHA-256 (or stronger).
Yes — extract the archive and run sha256sum -c your-manifest.sha256sums on Linux/macOS, or use Get-FileHash | Compare on Windows. Mismatched files are flagged immediately.
Web Crypto's SHA-256 runs in WASM with hardware acceleration where available. A 1 GB archive typically takes 10–30 seconds, dominated by archive decompression rather than hashing.
Verify every entry in a ZIP against its stored CRC32 checksum to detect corruption, partial downloads, or tampering. Browser-native, zero upload.
Open toolSHA-256 every entry inside an archive and group identical files. Spot duplicate logos, libraries, or .DS_Store waste. Reports total bytes recoverable.
Open toolInspect any digital signature attached to a ZIP — PKCS#7 signatures, JAR signing, APK v1/v2 signatures. Browser-native, zero upload, forensic-grade output.
Open tool