Chain JAD Archive tools to handle real-world workflows: reproducible builds, encrypted backups, GDPR-friendly data sharing, forensic audits, email splitting, and archive cleanup. Every step runs in your browser.
Make your build outputs bit-identical across machines and pipelines. Critical for supply-chain attestation, build caching, and bytewise diff detection.
Package your build output preserving the exact tree structure.
Reset every entry to 1980-01-01 (the ZIP epoch) — a standard for reproducible builds.
Emit a SHA-256 manifest your CI/CD pipeline can verify against later runs.
Compare two builds at the entry level to confirm reproducibility.
Pack sensitive data into AES-256 encrypted ZIPs that work across Windows, macOS, and Linux. No cloud, no third-party tooling — keys never leave your device.
Encrypt your files with WinZip-compatible AES-256. Use a password manager.
Generate SHA-256 manifests so you can prove the backup is intact.
Split the archive into FAT32-friendly parts for USB drive backups.
Verify your password is correct before relying on the archive.
Strip metadata, sanitise filenames, and encrypt before sharing personal data via email or third-party transfer. Avoid metadata leakage and sensitive paths.
Strip path-traversal sequences and platform-reserved characters.
Remove timestamps that could leak working hours or activity patterns.
Encrypt before emailing — share the password through a separate channel.
Audit any global comment for accidental sensitive content.
Inspect a suspicious archive without extracting. Identify format, scan metadata, detect encryption, find duplicates, and verify integrity before any data hits disk.
Identify the archive's true format from magic bytes — extensions can lie.
View the file tree without extracting any data.
Pull every header field — origin OS, version, timestamps, flags, comments.
Identify ZipCrypto vs AES variants — ZipCrypto is broken and should be flagged.
CRC32 check every entry to detect tampering or transmission damage.
Send a large archive over a 25 MB Gmail or 33 MB Outlook attachment limit by splitting into self-contained parts. No third-party transfer service needed.
Build the source ZIP with the optimal speed/size trade-off.
Split into 25 MB parts — each part is a complete, valid ZIP that opens independently.
Provide a SHA-256 manifest so the recipient can verify each part was received intact.
Inherit a messy ZIP? Strip the GitHub-release wrapper folder, remove macOS Finder cruft, prune empty directories, and re-pack at optimal compression.
Drop the project-1.2.3/ wrapper that GitHub release ZIPs always add.
Clean up path-traversal and reserved-character entries.
Remove zero-content directory entries from macOS Finder ZIPs.
Re-compress at level 6 for the final shipping artifact.