Split ZIP
Split a ZIP into parts by size, by number of parts, or by top-level folder. Every part is a complete, independently extractable ZIP; files are copied byte-for-byte, never recompressed. A separate byte-chunk mode (.001, .002…) is available when you need exact pieces.
Split ZIP
Split one ZIP into several smaller archives. Files are copied as-is, never recompressed.
Drop the ZIP you want to split
or choose one from your device
Files stay on your device. Nothing is uploaded.
How to use Split ZIP
- 1
Open the ZIP
Drop the archive you want to split, or choose it with the file picker.
- 2
Choose how to split
Set a maximum part size (presets or a custom value in KB, MB or GB), a number of parts, or one part per top-level folder.
- 3
Preview the parts
See which files land in which part and roughly how big each part will be, and adjust before anything is written.
- 4
Split and download
Parts are written as
name.part01.zip,name.part02.zipand so on. Each one is a complete ZIP you can open on its own.
Why use Aback ZIP's Split ZIP?
Every part is a real ZIP
Each part has its own index and opens in Windows Explorer, macOS Archive Utility, 7-Zip or any ZIP tool. The recipient doesn't need every part, or any special software, to get at the files in the one they have.
No recompression
Files are copied into the parts exactly as they are stored in the original, without being decompressed and compressed again. Splitting is quick and file data is unchanged.
Three ways to split
By maximum part size for upload or attachment limits, by number of parts for an even spread, or by top-level folder so each part has a clear purpose.
Byte chunks when you need them
A separate mode cuts the file into exact-size .001, .002 chunks. These are not ZIP files on their own and must be rejoined with Join ZIP Parts, 7-Zip or a command line before use.
Common use cases
Email attachment limits
Gmail allows 25 MB of attachments and Outlook typically 20 MB. Split a 140 MB project into parts a little under the limit and send one part per email; each can be opened as it arrives.
Chat and upload caps
Discord's free tier, many web forms and support portals cap file size well below what a project archive needs. Pick the cap as your part size and upload the parts one by one.
One part per folder
A client delivery with photos/, video/ and documents/ becomes three ZIPs, so each person downloads only the part they need.
Coursework and application portals
Learning platforms and application systems often cap uploads at 10 or 20 MB per file. Split a portfolio into parts that each meet the limit and still open normally for the reviewer.
Unreliable connections
Sending several smaller parts means a failed transfer costs one part, not the whole archive, and the recipient can start on the parts that have already arrived.
Exact reconstruction
When the recipient must end up with the identical original file, for example to match a published checksum, use byte-chunk mode and rejoin the chunks at the other end.
About Split ZIP
ZIP parts vs byte chunks
There are two very different ways to split an archive, and Aback ZIP keeps them clearly separate.
| ZIP parts (`.part01.zip`) | Byte chunks (`.zip.001`) | |
|---|---|---|
| Each piece opens on its own | Yes | No |
| Needs every piece to get any file | No | Yes |
| Part size | Approximate | Exact |
| Files cut across pieces | Never | Yes |
| After rejoining | Not needed; extract each part | Identical to the original file, byte for byte |
Byte chunks are pieces of a file, not ZIP archives. Renaming archive.zip.001 to .zip won't make it open. Rejoin all chunks first.
Why part sizes are approximate
Each ZIP part carries its own file headers, its own index and an end record, and files are never cut in half. The splitter fills each part with whole files until the next one would go over your target, so most parts finish a little under it. A single file bigger than the target can't be divided, so it gets a part of its own that is larger than the target. The preview shows the actual plan before you split.
Rejoining byte chunks
Use Join ZIP Parts in the browser, open the .001 file in 7-Zip, or join them on the command line:
# macOS / Linux
cat archive.zip.001 archive.zip.002 archive.zip.003 > archive.zip
# Windows (Command Prompt)
copy /b archive.zip.001 + archive.zip.002 + archive.zip.003 archive.zipWhat is kept and what changes
| Item | Result | Notes |
|---|---|---|
| File contents | Preserved | Compressed data is copied as is, without recompression. |
| Folder paths and names | Preserved | |
| Modification times | Preserved | |
| Encryption | Preserved | Encrypted entries stay encrypted with their original password. |
| Archive file | Rebuilt | Each part is a new ZIP with its own index. The parts together hold equivalent contents, not a byte-identical copy of the original. |
| Byte-chunk mode | Preserved | Joining all chunks in order gives back the original file exactly. |
Limitations
- Files are never cut in ZIP-part mode, so a single file larger than the target size ends up in its own, larger part. If every piece must be under a hard limit, use byte chunks instead, which are not independently openable.
- Part sizes are estimates because each part includes its own headers and index; set the target slightly below a strict limit.
- The archive is processed in browser memory. There is no fixed limit, but multi-gigabyte archives may fail on phones and low-memory devices.
- Byte chunks (
.001,.002…) are not ZIP files until every chunk is rejoined in order.
Processing happens locally in your browser. Your files are not uploaded, and closing the tab discards everything.
Related tools
Split ZIP: frequently asked questions
No. The archive is read and split in a Web Worker in your browser, and the parts are created on your device. Nothing is sent to a server and no account is needed.
Yes, in the default mode. Every .partNN.zip file is a complete ZIP with its own index, so it extracts in Windows Explorer, macOS Archive Utility, 7-Zip and other tools without the other parts. Only byte-chunk mode produces pieces that need to be rejoined.
Aim comfortably under your provider's limit, because email encoding adds overhead and part sizes are approximate: around 20 MB for Gmail (25 MB limit) and 15 to 18 MB for Outlook (typically 20 MB). The limit usually covers all attachments in one message, so send one part per email.
A ZIP part can't contain half a file. If one file inside the archive is larger than your target, it is placed in its own part, which is therefore larger than the target. Choose a bigger part size, or use byte-chunk mode if every piece must be under a strict limit.
ZIP parts don't need rejoining: extract each one into the same folder and you have all the files. To get a single archive again, combine them with Merge ZIP. Byte chunks must be rejoined with Join ZIP Parts, 7-Zip, cat or copy /b before they can be opened.
archive.part01.zip is a complete ZIP containing some of the files. archive.zip.001 is the first slice of the original file's bytes and is useless on its own. Aback ZIP names them differently so the two are never confused.
No. Files are copied into the parts exactly as they were compressed in the original archive, so their contents are unchanged. The part files themselves are new archives, so they are not byte-identical to slices of the original.
Yes. Encrypted files are copied into the parts still encrypted, with the same password as before. You don't need to enter the password to split, but the recipient needs it to open the files.