Total Size Of Requested Files Is Too Large For Ziponthefly Review

For power users, provide direct FTP credentials to a folder. They can use a desktop FTP client (FileZilla, Cyberduck) to download whole folders natively—no web ZIP required.

Allow the script more time to finish.

Title: Feature Request: Support for Larger Archives / Handling of Size Limits total size of requested files is too large for ziponthefly

Rating: ⭐⭐⭐

Pros: "ZipOnTheFly" is an efficient and easy-to-integrate tool for standard archiving tasks. The streaming capability works flawlessly for smaller batches, and the API is intuitive. It saves a significant amount of time compared to writing custom archiving logic. For power users, provide direct FTP credentials to a folder

Cons: The library struggles with large datasets. When attempting to compress a directory totaling over [Insert Size, e.g., 2GB/4GB], the process aborts with the error: "total size of requested files is too large for ziponthefly."

Comments: While the tool is excellent for day-to-day file management, the file size limitation is a significant bottleneck for enterprise-level backups or data packaging. The error message is clear, but it would be helpful if the documentation explicitly stated the hard size limits upfront to aid in architecture planning. If you control the server, increase the memory

Ideally, future updates could implement chunking or a true streaming mode that writes directly to disk to circumvent memory constraints, allowing for larger archive creation.

If you control the server, increase the memory limit for the script handling the ZIP generation.

⚠️ Warning: Increasing memory only helps up to a point. A single request using 2GB of RAM is inefficient and may crash the server.