Modify the EOCD comment of any ZIP file in place. Add build metadata, strip a leaked credential, or clear a comment for distribution. Browser-native.
Per-job file size, entry count, and batch caps for Comment Editor. 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 ZIP file and enter the new comment (or empty to remove)
We rewrite the End of Central Directory record with the new comment
Download the modified ZIP — every entry's data is byte-identical to the source
0 bytes uploaded. ZIP Comment Editor runs entirely in your browser using fflate, zip.js, and libarchive WASM. Your archive files never leave your device.
No — the EOCD comment is a free-form trailing field that no entry depends on. Every unzipper safely ignores it. We do recompute the comment length so the EOCD signature stays valid.
Standard ZIP caps the comment at 65535 bytes. If your input is longer, we truncate with a clear warning. ZIP64 extends this but not all unzippers handle the extension.
Yes — we encode the comment as UTF-8. Most modern unzippers display it correctly; very old DOS-era tools may show mojibake.
Read the global comment embedded in a ZIP's End of Central Directory record — often used by build systems for build IDs, version stamps, or signing metadata.
Open toolInspect every entry's headers — version, OS, last modified, compression method, encryption flags, extra fields. Forensic-grade ZIP intelligence, zero upload.
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