| User type | Action | |-----------|--------| | | Download fewer files at once. Contact site admin. | | Site owner (non-technical) | Ask hosting support to increase PHP limits. Or switch to a plugin that pre-generates ZIPs. | | Developer | Replace ZipOnTheFly with ZipStream-PHP, pre-generated cron ZIPs, or cloud signed URLs. | | Agency / enterprise | Implement a dedicated download server (e.g., using Nginx’s X-Accel or Apache’s X-SendFile ) for large static ZIPs. |
If you control the server, increase the memory limit for the script handling the ZIP generation.
Creating a ZIP without compression (store mode) is faster and uses less memory. In PHP, you can change: total size of requested files is too large for ziponthefly
: For .NET applications, check the maxRequestLength and executionTimeout values. App-Specific Settings :
When you encounter the "Total size of requested files is too large for ZipOnTheFly" error, it means that the total size of the files you're trying to compress exceeds the maximum allowed limit set by ZipOnTheFly. This limit is in place to prevent users from compressing extremely large files that could cause performance issues or crashes. | User type | Action | |-----------|--------| |
If you are a developer or admin seeing this error on your own platform, you may need to adjust your configuration.
When you encounter this limitation, you can use several workarounds to get your files successfully. 1. Download Files in Smaller Batches Or switch to a plugin that pre-generates ZIPs
The error is not a bug—it is a protective mechanism. It tells you that your server’s real-time compression resources are insufficient for the current request. While you can increase memory and time limits temporarily, the robust, professional solution is to abandon ZipOnTheFly for large downloads in favor of pre-generated ZIP files or direct cloud-based delivery.
When the total size of the selected files is too high, it hits a roadblock. Common Causes for the Error
Bonus tip: For web servers with “zip on the fly” plugins (like cPanel’s), the limit often exists to prevent memory overload. Splitting respects both server resources and file size restrictions.