ZIP64 explained: large archives beyond 4 GB
What ZIP64 is, why archives need it past 4 GB, and how browsers handle very large ZIP files.
The original ZIP format was designed when files were measured in kilobytes. It used 32-bit numbers for sizes and offsets, which limits a classic ZIP to 4 GB and 65,535 entries. ZIP64 is an extension that uses 64-bit numbers so archives can grow far beyond those limits.
The classic limits
In a classic ZIP file, sizes, offsets, and entry counts are stored as 32-bit unsigned integers. The practical consequences:
- A single file inside the archive can be at most 4 GB.
- The archive itself cannot exceed about 4 GB.
- The archive cannot contain more than 65,535 entries.
How ZIP64 works
ZIP64 does not change the base format. It adds extra fields and records that carry 64-bit values, plus a ZIP64 end of central directory record and a locator that points to it. Readers that understand ZIP64 use the 64-bit values; readers that do not can still find the classic structures and often refuse the archive gracefully.
When do you need ZIP64?
You need ZIP64 when a single entry exceeds 4 GB, the total archive exceeds 4 GB, or the entry count exceeds 65,535. Video projects, database dumps, and large backup collections commonly hit these limits.
ZIP64 in the browser
Browsers are JavaScript environments, and JavaScript numbers are safe only up to 9,007,199,254,740,991, which is still far above 4 GB. Archive code must read 64-bit fields without overflowing into unsafe integers. Aback ZIP parses ZIP64 fields where present and reports them in the ZIP Viewer.
Frequently asked questions
Are ZIP64 files compatible with old software?
Older archive tools may not understand ZIP64 and can refuse the file or misreport sizes. Modern tools handle ZIP64 without any user action.
Does Aback ZIP support ZIP64?
Aback ZIP reads ZIP64 metadata and handles large values safely. Practical limits are set by the memory available in your browser.