Chunked Uploads for Big Sites​

Summary: Chunked uploads help Antimanual Builder Pro process large ZIP sites reliably. Learn how uploads are split, reassembled, and imported in the background with progress tracking, protected storage, and improved stability for memory-limited servers during complex migrations.

Security and Access Controls

Chunked upload is built with restrictive access rules. Import routes require the correct user capabilities, and each job is tied to the user who created it. Imported markup is sanitized using a script-free allowlist, and event-handler attributes are stripped to reduce risk during save and render operations.

This means the feature is intended for controlled site administration, not open-ended file execution. It is designed to be safer than a generic file import tool while still supporting complex migration workflows.

Best Practices

To improve reliability, use chunked uploads whenever the archive is large or the server has limited resources. If an upload fails, check the file size, browser connection, and server limits before trying again. When possible, keep the project focused on pages and assets that are actually needed for the migration.

• Use chunked upload for big or media-heavy sites.
• Keep source projects tidy before exporting.
• Review previews to validate imported pages.
• Confirm storage and cleanup after completion.

For larger migrations, the combination of chunked upload, background processing, and organized asset storage provides a practical and dependable import path. It helps Antimanual Builder Pro handle demanding projects without sacrificing control or visibility.

• Prepare a clean ZIP archive.
• Upload the project in chunks.
• Review the generated page plan.
• Monitor background progress and previews.
• Confirm results before publishing.

Security and Access Controls

Chunked upload is built with restrictive access rules. Import routes require the correct user capabilities, and each job is tied to the user who created it. Imported markup is sanitized using a script-free allowlist, and event-handler attributes are stripped to reduce risk during save and render operations.

This means the feature is intended for controlled site administration, not open-ended file execution. It is designed to be safer than a generic file import tool while still supporting complex migration workflows.

Best Practices

To improve reliability, use chunked uploads whenever the archive is large or the server has limited resources. If an upload fails, check the file size, browser connection, and server limits before trying again. When possible, keep the project focused on pages and assets that are actually needed for the migration.

• Use chunked upload for big or media-heavy sites.
• Keep source projects tidy before exporting.
• Review previews to validate imported pages.
• Confirm storage and cleanup after completion.

For larger migrations, the combination of chunked upload, background processing, and organized asset storage provides a practical and dependable import path. It helps Antimanual Builder Pro handle demanding projects without sacrificing control or visibility.

• Prepare a clean ZIP archive.
• Upload the project in chunks.
• Review the generated page plan.
• Monitor background progress and previews.
• Confirm results before publishing.

Security and Access Controls

Chunked upload is built with restrictive access rules. Import routes require the correct user capabilities, and each job is tied to the user who created it. Imported markup is sanitized using a script-free allowlist, and event-handler attributes are stripped to reduce risk during save and render operations.

This means the feature is intended for controlled site administration, not open-ended file execution. It is designed to be safer than a generic file import tool while still supporting complex migration workflows.

Best Practices

To improve reliability, use chunked uploads whenever the archive is large or the server has limited resources. If an upload fails, check the file size, browser connection, and server limits before trying again. When possible, keep the project focused on pages and assets that are actually needed for the migration.

• Use chunked upload for big or media-heavy sites.
• Keep source projects tidy before exporting.
• Review previews to validate imported pages.
• Confirm storage and cleanup after completion.

For larger migrations, the combination of chunked upload, background processing, and organized asset storage provides a practical and dependable import path. It helps Antimanual Builder Pro handle demanding projects without sacrificing control or visibility.

Chunked uploads for big sites allow Antimanual Builder Pro to handle large ZIP archives more reliably, even on servers with limited PHP memory or strict request timeouts. Instead of sending an entire file in one request, the plugin splits the archive into smaller parts, uploads them progressively, and reassembles them on the server before import continues.

This approach is designed for stability. It reduces failed uploads, improves progress visibility, and helps ensure that large migrations can continue without forcing the browser or server to process everything at once. For bigger projects, chunked upload is the recommended workflow.

How Chunked Uploads Work

When you upload a ZIP project, Antimanual Builder Pro divides the archive into smaller segments. Each segment is sent separately and stored in a protected temporary location until all parts are received. After assembly, the importer can analyze the project structure, resolve assets, and create pages from the completed archive.

This method is especially useful on shared hosting or other environments where a single large request might fail. By streaming the upload in pieces, the system avoids exhausting memory and gives you a clearer view of progress.

• Large ZIP files are uploaded in smaller parts.
• A progress bar shows upload and processing status.
• Chunks are assembled before import begins.
• Temporary chunk storage is cleaned up after completion.

Why It Matters for Large Imports

Traditional file uploads can fail when the archive is too large or the server cuts off the request early. Chunked uploads reduce that risk by keeping each transfer small and manageable. This makes the import process more resilient and better suited to multi-page websites, design systems, and content-heavy migrations.

In many cases, the upload phase is followed by a background job. That means the site can keep processing the import without leaving the browser stuck on one long request. The result is a smoother experience and better recovery behavior if the connection is interrupted.

Background Import Jobs and Progress Tracking

After the archive is assembled, Antimanual Builder Pro continues with a background job that analyzes the project and creates pages. This avoids a single blocking operation and allows the system to report live progress while the import runs.

For larger sites, this is particularly valuable because it lets you review page-level progress as content is created. You can also use per-page previews to confirm that the import is producing the expected layout and structure.

• Live progress updates during import.
• Per-page previews while processing continues.
• Reduced timeout risk on slower servers.
• More reliable handling of large archives.

Where Uploaded Files Are Stored

Imported and generated assets are stored under the WordPress uploads directory in the Antimanual Builder folders. Chunked upload data is assembled in a protected temporary location, and that storage is removed after the import finishes. This keeps the workflow separate from normal site content and reduces accidental exposure.

For reference, the main storage locations are organized and restricted by design. This helps preserve site cleanliness while keeping imported assets manageable during and after migration.

• Primary assets: wp-content/uploads/antimanual-builder/
• Temporary chunks: protected import-chunks storage
• Cleanup: temporary chunk data is removed after processing

Requirements Before You Start

Chunked uploads are available only when the required base setup is in place. Before starting a large import, confirm that the free Antimanual Builder plugin is installed and active, your Pro license is active, and your WordPress and PHP versions meet the supported minimums.

• Antimanual Builder free plugin, version 0.7.0 or later.
• Active Antimanual Builder Pro license.
• WordPress 6.0 or later.
• PHP 7.4 or later.

If your import uses AI-assisted planning, make sure the companion configuration is also complete before uploading the archive. Otherwise, the importer will use deterministic file analysis to continue the workflow.

Recommended Workflow for Large Sites

For the best results, keep your archive organized and avoid including unnecessary files. Clear page names and a consistent folder structure make it easier for the importer to identify page candidates and resolve related assets correctly.

• Prepare a clean ZIP archive.
• Upload the project in chunks.
• Review the generated page plan.
• Monitor background progress and previews.
• Confirm results before publishing.

Security and Access Controls

Chunked upload is built with restrictive access rules. Import routes require the correct user capabilities, and each job is tied to the user who created it. Imported markup is sanitized using a script-free allowlist, and event-handler attributes are stripped to reduce risk during save and render operations.

This means the feature is intended for controlled site administration, not open-ended file execution. It is designed to be safer than a generic file import tool while still supporting complex migration workflows.

Best Practices

To improve reliability, use chunked uploads whenever the archive is large or the server has limited resources. If an upload fails, check the file size, browser connection, and server limits before trying again. When possible, keep the project focused on pages and assets that are actually needed for the migration.

• Use chunked upload for big or media-heavy sites.
• Keep source projects tidy before exporting.
• Review previews to validate imported pages.
• Confirm storage and cleanup after completion.

For larger migrations, the combination of chunked upload, background processing, and organized asset storage provides a practical and dependable import path. It helps Antimanual Builder Pro handle demanding projects without sacrificing control or visibility.