Chunked Upload Storage

Summary: Chunked upload storage lets Antimanual Builder Pro handle large ZIP imports safely by storing file parts temporarily, reassembling them on the server, and cleaning up after completion. This improves reliability, reduces timeouts, and keeps incomplete import data protected during migration workflows.

Chunked upload storage is the temporary area Antimanual Builder Pro uses while large ZIP projects are being transferred and assembled. It allows the plugin to process uploads in smaller parts, which improves reliability on servers with limited memory or strict request timeouts. For large imports, this storage is a core part of the upload workflow.

How Chunked Upload Storage Works

When you start a ZIP import, the archive is split into chunks instead of being sent in a single request. Each part is uploaded separately and stored in a protected temporary folder until all segments arrive. The system then reassembles the archive on the server and continues with analysis, asset handling, and page creation.

This approach reduces the risk of upload failures caused by memory limits, browser interruptions, or timeout errors. It also gives the importer more control over progress, especially when handling larger projects or sites with many assets.

• Large ZIP files are divided into smaller upload parts.
• Chunks are stored temporarily in a protected import folder.
• The archive is reassembled before import processing begins.
• Temporary data is cleaned up after the job finishes.

Why the Temporary Folder Is Protected

The chunk storage folder is intentionally restricted and is not treated as normal site content. This helps prevent accidental exposure of incomplete import data while the system is still assembling the final project. It also keeps temporary upload fragments isolated from the rest of your WordPress media and builder files.

Once the archive is fully processed, the temporary chunk data is removed. Imported assets are then stored separately in the Antimanual Builder uploads directory, where they are organized for later use and easier maintenance.

When Chunked Upload Storage Is Used

Chunked storage is used automatically during large ZIP imports and other memory-sensitive upload workflows. It is especially helpful on shared hosting, low-resource environments, or servers with conservative PHP limits. In these cases, a single large request may fail, while chunked transfer completes successfully.

It is also valuable when importing projects that contain many files, images, or page assets. By streaming the upload in parts, the plugin avoids forcing the browser and server to handle the entire archive at once.

Benefits for Large Imports

Chunked upload storage is designed to improve stability and visibility throughout the import process. Instead of a single long-running request, the plugin can track progress more reliably and resume server-side work after the upload is complete.

• Reduces failed uploads on large archives.
• Helps avoid PHP memory and timeout issues.
• Improves progress tracking during upload and assembly.
• Supports a more dependable migration workflow for big sites.

For best results, use chunked uploads whenever the project is large or the server environment is constrained. This is the recommended workflow for big imports.

Storage Lifecycle: Upload, Assemble, Clean Up

The chunked upload process follows a predictable lifecycle. First, the archive is split and transferred in smaller segments. Next, the plugin stores those segments temporarily until the full file is available. After assembly, the importer processes the completed archive and proceeds with page or project creation.

At the end of the job, temporary chunk files are removed. This keeps the site tidy, prevents stale upload fragments from accumulating, and ensures the temporary folder only serves its intended purpose during active imports.

Practical Best Practices

You do not usually need to manage chunk storage manually, but a few operational habits can help large imports succeed more consistently. Keeping source projects organized and validating the archive before upload can reduce errors during transfer and assembly.

• Use chunked uploads for big or media-heavy projects.
• Check browser connectivity before retrying a failed upload.
• Review server limits if large imports stall or time out.
• Keep the source ZIP focused on only the files you need.

If you are also reviewing generated pages during import, per-page previews can help you confirm output as the job progresses. For storage and cleanup behavior across imported assets, see the broader file handling guidance.

Summary

Chunked upload storage enables Antimanual Builder Pro to handle large ZIP imports more safely and reliably. By storing file fragments in a protected temporary location, reassembling them on the server, and removing them after completion, the plugin supports stable imports without exposing incomplete data.