IronZIP File and Archive Size Limits
IronZIP creates, reads, and extracts ZIP archives, and it fully supports the ZIP64 standard. That means you are not capped by the classic 4GB file size or 65,535-entry limits of the original ZIP format.
ZIP64 Theoretical Limits
ZIP64 is the extended ZIP format that lifts the legacy ceilings. IronZIP enables it automatically, so the only hard limits you hit are the ones defined by the spec itself:
- Maximum file size per entry: ~18 exabytes (2⁶⁴ bytes)
- Maximum archive size: ~18 exabytes
- Maximum number of entries: more than 4 billion files per archive
- Maximum file name length: ~64K characters
Practical Considerations
The numbers above are theoretical. What you can actually process depends on the host environment:
- System memory: Large file operations can be memory-intensive, so available RAM matters.
- File system type: FAT32 caps individual files at 4GB. Use NTFS or exFAT for anything larger.
- Application architecture: Run as a 64-bit process when handling multi-GB data.
- Disk I/O performance: Read and write speeds drive how long creation and extraction take.
Recommendations
For smooth performance on large ZIP operations:
- Run your application as a 64-bit process.
- Stream files where possible to keep memory pressure low.
- Skip FAT32 drives when files are near or above 4GB.
- Monitor memory usage and test under your expected file loads.
IronZIP works on both Windows and Linux and targets .NET 6, 7, 8, and .NET Framework.

