Fit a set of files inside a per-ZIP size limit
Admin ·
Use ZIP Splitter when each attachment must fit on its own. An individual ZIP needs room for its compressed data, filenames and archive records. Start with a known example to see how the limit affects which entries travel together.
Try a 300-byte ZIP limit
Choose Load example. It selects the fieldwork sample and sets Maximum bytes per ZIP to 300. Select Split ZIP archive.
The result lists part-001.zip at 266 bytes and part-002.zip at 166 bytes. The first contains empty/ and briefing/route.txt. The second contains data/café.csv. The 320-byte data/sample.bin needs at least 464 bytes for its own ZIP and appears in Entries above the maximum.
Increase the limit and compare the plans
Set Maximum bytes per ZIP to 500 and split again. The first part grows to 410 bytes. The binary sample now fits as a separate 464-byte ZIP.
Review the new actual sizes and confirm the skipped entries list has cleared before downloading. Compare the part size with your destination's limit in bytes.
| Maximum | Sizes of the two parts | Members left out |
|---|---|---|
| 300 bytes | 266 and 166 bytes | data/sample.bin |
| 500 bytes | 410 and 464 bytes | None |
Open one part by itself
Download part-002.zip at the 500-byte limit. Open it in ZIP File Extractor and check that it contains data/sample.bin with 320 bytes. The part can be opened on its own because it has a complete ZIP directory.
If a member cannot fit alone and the destination's limit is fixed, select a smaller version of that file or send that member separately using a different channel.
Common questions
Will the splitter recompress my files to force a fit?
It verifies the members and reuses their ZIP compression. The largest possible input that fits depends on the existing compressed size and the path's archive records.
Can I split a single entry between two parts?
The splitter assigns whole entries so each part can be extracted on its own. An entry that needs more space than the limit appears in the oversized list.