Large Import Handling​

Summary: Learn how Large Import Handling in Antimanual Builder Pro processes large ZIP imports with chunked uploads, background jobs, and previews. This guide explains when to use it, why it improves reliability, and how it helps migrate multi-page sites safely on limited servers.

Large Import Handling in Antimanual Builder Pro is designed to keep big migrations reliable, even when you are moving a multi-page site, a heavy ZIP archive, or a project with many shared assets. Instead of sending everything through one long request, the plugin uses chunked uploads, protected storage, and background processing to reduce timeouts and memory-related failures.

This workflow is especially useful on servers with limited PHP memory or strict execution limits. It also gives you visibility during the import, including live progress updates and per-page previews, so you can confirm the result before you move on to final edits.

How Large Import Handling Works

Large imports are processed in stages rather than all at once. Files are uploaded in chunks, assembled in a protected import directory, and then handled by a background job. This approach is more stable for substantial archives because it reduces the chance of a single request failing midway through the process.

• Chunked uploads break large ZIP files into smaller transfer units.
• Background jobs continue processing without keeping the browser locked on one request.
• Per-page previews let you review results as the import advances.
• Asset handling keeps imported files organized in the uploads directory.

When to Use Large Import Handling

Use this workflow when your project contains multiple pages, shared media, or navigation that should be preserved across the imported site. It is the preferred path for full-site migrations and structured archives, especially when the content is too large for a simple one-page HTML import.

For example, a static marketing site with separate pages for home, services, blog, and contact is a strong candidate for ZIP project import. A single landing page exported from another system may still be better suited to HTML file import.

Typical Large ZIP Import Workflow

• Open the Antimanual Builder import screen in the WordPress admin.
• Upload the ZIP project using the large-file import flow.
• Let the plugin analyze the archive and identify page content.
• Review the suggested page plan if AI planning is available.
• Watch background progress while pages are created and assets are collected.
• Check per-page previews and continue with manual refinement.

If AI planning is unavailable, the plugin falls back to deterministic analysis automatically. That means your import can still proceed without requiring AI assistance.

Why Chunked Uploads Improve Reliability

Large ZIP files often fail when a server must process the entire archive in one request. Chunked uploads reduce this risk by streaming the file in smaller parts and assembling it on the server side. This is particularly important on memory-limited environments where a single large upload can exceed PHP limits or trigger a timeout.

During this stage, the upload data is stored in a protected import-chunks folder and cleaned up after the job completes. Imported assets are stored separately in the Antimanual Builder uploads directory, keeping project files organized and easier to manage.

Background Jobs and Progress Tracking

Instead of waiting for one long browser request to finish, the import runs as a background job. This makes the process more resilient and gives you live status updates while pages are being created. For large projects, this is one of the most important safeguards because it keeps the workflow responsive.

Progress tracking is also useful for quality control. If a page needs attention, you can identify it early through its preview and continue the migration with a clear view of what has already been processed. How to Install the Docy Core Plugin for the Docy WordPress Theme

Best Practices for Large Imports

• Use ZIP import for multi-page sites and structured archives.
• Confirm that the free Antimanual Builder plugin is installed and active before starting Pro imports.
• Check that your WordPress and PHP versions meet the plugin requirements.
• Review previews before making major design changes.
• Keep the archive organized so internal links and shared assets can be resolved more accurately.

Security and Storage Considerations

Large imports are processed locally by the plugin and do not rely on external services to upload or store your project files. Import routes are protected by permission checks, and jobs are tied to the user who created them. This helps ensure that only authorized users can run and manage import tasks.

Imported and generated assets are stored under wp-content/uploads/antimanual-builder/, while chunked uploads use the protected ambld-import-chunks directory. The import pipeline also sanitizes markup during save and render operations to reduce risk from unsafe content.

Summary

Large Import Handling gives Antimanual Builder Pro the stability needed for substantial site migrations. With chunked uploads, background jobs, and page-by-page previews, you can move large projects more safely and with better control. It is the right approach whenever your import goes beyond a simple single-page transfer.