Set every entry's date/time to a single UTC value. Essential for reproducible builds, deterministic CI, and bit-identical artifact comparisons.
Per-job file size, entry count, and batch caps for Timestamp Normaliser. 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 |
This tool requires the Pro plan or higher.
Drop your ZIP and pick a target ISO date (default: 1980-01-01, the ZIP epoch)
We rewrite every entry's MS-DOS date/time field to the chosen value
Download the normalised ZIP — bit-stable across machines and rebuilds
0 bytes uploaded. Archive Timestamp Normaliser runs entirely in your browser using fflate, zip.js, and libarchive WASM. Your archive files never leave your device.
It's the ZIP epoch — the earliest representable date in MS-DOS timestamps. Many reproducible-build pipelines (Bazel, Nix, Maven Reproducible Build) standardise on this so checksums match across machines.
No — only the metadata. The compressed payload of every entry stays bit-identical. Two normalised ZIPs from the same source files will have the same SHA-256.
Unix-style 64-bit timestamps in extra field 0x5455 are also rewritten. NTFS 0x000a timestamps are preserved as-is by default; check the Pro option to also normalise those.
Strip path-traversal sequences, fix Windows-reserved characters, normalise to UTF-8, and remove NUL bytes. Essential before extracting untrusted ZIPs.
Open toolInspect every entry's headers — version, OS, last modified, compression method, encryption flags, extra fields. Forensic-grade ZIP intelligence, zero upload.
Open toolCompute 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.
Open tool