Folder Structure → ZIP
Recreate a specific nested folder structure inside a .zip from a list of paths.
What is Structure to ZIP?
A structure-first archiver. Instead of zipping whatever folders you happen to have, you declare the layout you need and fill it with files — useful for scaffolding, manifest-driven rebuilds and bundles where directory names matter.
How it works
Each line of the path list becomes an archive entry. A line with `destination => source` maps an explicit file by name; a plain path is filled from a picked file with the same filename; and unmatched paths become empty placeholder files when that option is on. Parent folders are emitted as real directory entries so the tree expands correctly everywhere.
- 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 240 MB photo folder → a 52 MB .zip
JPEGs are already compressed, so the archive only saves 10–15% — but adding the folder structure and a manifest makes the upload verifiable.
A download cut off at 1.4 GB
The File Splitter cuts it into 500 MB chunks that fit the host's limit, and the File Joiner reassembles them, refusing any set with a missing part.
A release bundle with checksums
The Manifest Generator writes sha256sum-style lines next to the files, so the recipient can prove the download arrived intact.
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
What is the difference between `a/b.txt` and `a/b.txt => invoice.pdf`?
The first looks for a picked file named b.txt. The second is explicit: whatever you picked as invoice.pdf is stored at a/b.txt. Use the arrow form when the destination name differs from the source name.
Can I create empty folders?
Yes — list a folder path ending in a slash, or let a parent folder with no files be added as a directory entry. Empty placeholder files are the alternative when something downstream needs a real file to be present.
Why would I want this instead of just zipping a folder?
When the archive layout must match a spec you cannot reproduce on disk — rebuilding a deployment tree, scaffolding a starter project, or shipping assets where the paths are part of the contract.