Guide
Why Google Splits Your Download Into Multiple ZIP Files
Export anything sizeable from Google — a Drive folder, a Google Photos library, a full Takeout archive, or a Data Transfer between accounts — and you won't get one file back. You'll get several ZIPs. Extract them one at a time and you'll often find each one only has part of a folder's contents, with the rest sitting in a different ZIP. Here's the mechanism behind that, and how ZipCombiner skips the manual reassembly for you.
The size limit you choose
When you set up a Google Takeout export (or a Drive folder download, or a Data Transfer), Google lets you pick a maximum size for each archive — typically somewhere from around 1GB up to 50GB, depending on what's offered at the time. That number isn't a suggestion: once your total export exceeds it, Google splits the whole thing into as many separate ZIP files as it takes to stay under that limit per file.
Why one folder can end up split across two ZIPs
This is the part that catches people off guard. Google doesn't pack your export folder by folder — it just keeps filling the current archive until it hits your size limit, then starts a new archive and picks up exactly where it left off. If a folder's files happen to straddle that cutoff, the folder itself gets split: the first however-many files land in one ZIP, and the rest land in the next one. A large Google Photos album is a common example — start in takeout-003.zip, finish in takeout-004.zip.
Every individual ZIP in the sequence is still a complete, valid archive — it opens and extracts just fine on its own. The problem only shows up once you compare what actually landed in your destination folder against what you expected: a folder that looks incomplete, or the same folder appearing twice because it was extracted from two different ZIPs into two different places.
What happens if you extract them one at a time
Your operating system's built-in unzip tool has no idea the archives are related. Extract each one separately and you'll typically end up with several top-level folders instead of one, split subfolders that never get reunited, and — if you extract into the same destination — a real risk of files with matching names overwriting each other instead of merging. See what missing or duplicated files after extraction actually looks like if you're troubleshooting that right now.
How ZipCombiner fixes this
- Download every ZIP in the export into the same folder, so nothing gets separated.
- Drag all of them into ZipCombiner and choose "Treat as full ZIP(s)" — the correct mode since each export ZIP is a complete, independently extractable archive.
- Extract. ZipCombiner reads every archive together and merges the contents into one folder that matches your original Drive, Photos, or Takeout structure — split folders reunited, nothing duplicated.
Frequently asked
How large can a Google Takeout or Drive export be before it gets split into multiple ZIPs?
It depends on the maximum archive size you choose when setting up the export — typically from around 1GB up to 50GB per file. Once your export exceeds that limit, Google splits it into as many ZIPs as needed.
Does each ZIP contain a complete folder, or can one folder be split across multiple ZIPs?
A folder's contents can be split across more than one ZIP. Google fills each archive to your size limit and continues in the next one — it doesn't keep a folder together just because it's one folder.
Is this the same problem as split ZIP files named zip.001, zip.002?
No. Google's export ZIPs are each complete and independently extractable. A zip.001-style split archive is one file broken into fragments that don't work alone. See what a split ZIP file actually is for the difference.
Does this happen with Google Photos and Google Data Transfer too, not just Takeout?
Yes — Photos exports, Drive folder downloads, and the Data Transfer tool for moving content between accounts all use the same size-limited archive approach.
Working specifically with a Google Takeout export? See how to combine Google Takeout ZIP files. Downloading a Drive folder instead? See how to rebuild a Google Drive folder from ZIP downloads.