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.
Per-job file size, entry count, and batch caps for Comment Extractor. 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 archive
We scan backwards for the EOCD signature and read the comment field
Get the full UTF-8 comment as plain text — useful for build provenance and audit
0 bytes uploaded. Archive Comment Extractor runs entirely in your browser using fflate, zip.js, and libarchive WASM. Your archive files never leave your device.
Usually a build ID, version string, or developer note. Some IDEs (IntelliJ, Eclipse) embed plugin metadata. Maven uses comments to record build timestamps. Docker layer ZIPs sometimes carry the layer SHA.
Not in standard ZIP — the EOCD comment length field is 16 bits (max 65535). ZIP64 archives can extend this, but real-world comments are typically a few hundred bytes.
Yes — each central directory entry has its own optional comment. Use the Archive Metadata Extractor for per-entry comments; this tool reads only the global archive comment.
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.
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