Archive Manifest Generator
Generate a manifest.txt listing every file with its size and checksum, ready to bundle with a release.
What is Manifest?
A release-manifest builder. It writes a text file listing every file with its size and hash, in the same shape as sha256sum output so existing verification scripts parse it.
How it works
SHA-256 comes from the browser's WebCrypto digest; MD5 and CRC-32 are implemented locally because no platform crypto API exposes them. The manifest is generated from the bytes actually read, and can be delivered on its own or inside a bundle that also contains every file.
- Add your files. Drop files (or a whole folder) onto the drop zone. Browsers hand the contents straight to the page, so nothing is uploaded.
- Choose the options. Pick the format, compression, naming rule or split size. Any change re-computes the preview immediately.
- Download the result. Run the tool and grab the archive, the extracted files or the report. Multi-file results come back as a single .zip.
Examples
A signed-off release bundle
Ten assets plus manifest.txt in one .zip; recipients run sha256sum -c manifest.txt after unzipping and get a pass for every file.
Proving a download arrived intact
Publish the manifest next to the download; anyone can recompute the hashes locally and compare, without trusting the transfer.
Common mistakes
Expecting ZIP to shrink photos, video or audio
Those formats are already compressed; deflate typically saves single digits on them. ZIP is at its best on text, JSON, CSV, logs and source code.
Treating ZipCrypto as real encryption
Traditional ZIP encryption is legacy and breakable. It stops casual snooping only — for secrets, encrypt the contents with AES-256 first.
Renaming extensions to convert a file
Changing .png to .jpg does not change the bytes inside. Some programs will refuse the file, or display garbage. Use a real converter when the format must change.
Splitting without keeping the suffixes
The parts carry .001, .002 … suffixes on purpose: the joiner orders them by number and fails loudly when one is missing, instead of producing a corrupt file.
Frequently asked questions
Which algorithm should I choose?
SHA-256 unless something upstream demands otherwise — it is the modern default and matches sha256sum. MD5 and CRC-32 are offered for compatibility with older release pages and for fast corruption checks.
What exactly is written in the manifest?
A short comment header with the algorithm, file count, total bytes and generation time, then one line per file: <hash> <size> <path>. The three fields are space-separated like the standard Unix tools.
Is MD5 here trustworthy?
It is a correct implementation of RFC 1321 and fine for spotting accidental corruption. MD5 is no longer collision-resistant, so do not use it to prove that a file was not deliberately modified.