​Upload a ZIP Project

Summary: Learn how to upload a ZIP project in Antimanual Builder Pro to import multiple editable pages, resolve internal links, and process large archives with chunked uploads and background jobs for reliable migrations.

Use ZIP project import in Antimanual Builder Pro to convert a static multi-page site into editable WordPress pages. Upload a ZIP archive, let the plugin analyze the project structure, and create pages with internal links and assets resolved. For large projects, the import can also run in chunks and background jobs for better reliability.

What ZIP Project Import Does

ZIP project import is designed for importing an entire static site rather than a single file. It is especially useful when your project contains multiple HTML pages, shared assets, and cross-links between sections. Antimanual Builder Pro reads the archive, identifies the page structure, and creates builder pages that you can edit after import.

This feature is part of the Pro import engine and is not available in the free plugin alone. If Pro is inactive, the HTML Import screen remains locked. ZIP import becomes available only when the free Antimanual Builder plugin is installed and the Pro license is active.

• Imports a static site from a ZIP archive.
• Creates multiple pages in a single import job.
• Resolves internal links and referenced assets where possible.
• Supports large uploads with chunked transfer and background processing.

Before You Upload the ZIP Project

Before starting, confirm that your WordPress site meets the requirements for Antimanual Builder Pro. The free plugin must be installed, your user account must have permission to edit pages and upload files, and the Pro license must be active. If you plan to use AI-assisted page planning, you also need the companion Antimanual plugin configured with an AI provider.

For best results, prepare a clean ZIP archive that contains the site files in a logical structure. The importer works locally by default and stores generated assets under the WordPress uploads directory. Large archives may be split into chunks during upload to reduce memory issues on constrained servers.

• Install and activate the free Antimanual Builder plugin.
• Activate Antimanual Builder Pro and complete license activation.
• Ensure your account can edit pages and upload files.
• Optionally configure an AI provider for page planning.

How the ZIP Import Process Works

When you upload a ZIP project, the plugin first analyzes the archive and determines which files should become pages. For smaller projects, this may be fully deterministic. For larger projects, Pro can optionally ask your configured AI provider to suggest a page plan, including titles and slugs. If AI planning is unavailable or not appropriate for the project size, the importer falls back to file analysis automatically.

Once the page plan is ready, the importer processes each page, resolves assets, and creates editable builder content. Background jobs handle long-running imports and provide live progress updates. Per-page previews are available during processing so you can verify the results before continuing.

• Upload the ZIP archive.
• Analyze the project structure.
• Generate or confirm the page plan.
• Import pages, links, and assets.
• Review previews and completion status.

Large ZIP Files and Background Imports

Large ZIP projects are handled differently from small archives to improve stability. Antimanual Builder Pro supports chunked, streamed uploads with a progress bar, which helps on servers with low PHP memory limits. After the upload is assembled, the import can continue as a background job rather than a single blocking request.

This approach reduces timeouts and makes it easier to import larger sites. It also allows the system to create pages progressively and show the current import state. If you are migrating a site with many files, this is the recommended workflow.

• Chunked uploads reduce failures on limited servers.
• Background jobs avoid long request timeouts.
• Progress indicators help track large imports.
• Per-page previews help validate output as it is generated.

Security and Data Handling

ZIP import is built with restrictive import rules. The importer does not provide arbitrary code execution features, and imported markup is sanitized using a script-free allowlist. Event-handler attributes are stripped during processing to reduce risk. In addition, import routes require the appropriate user capability, an active Pro license, and ownership of the running background job.

The Pro import feature also works locally by default. It does not contact external services on its own unless you explicitly trigger AI page planning. When that happens, only bounded summaries of the project files are sent to your configured AI provider. The ZIP archive itself is not sent for single-file workflows, and AI is optional for imports.

The Advantages and Disadvantages of Developing a Custom WordPress Theme

Where Imported Files Are Stored

Imported assets are organized under the WordPress uploads directory. Generated and imported files are stored in the Antimanual Builder uploads folder, while chunked upload data is assembled in a protected import-chunks folder. Temporary chunk storage is cleaned up after the import completes.

This structure helps keep imported media and project files separated from other site content. It also supports cleaner troubleshooting if you need to inspect how a project was processed.

Best Practices for ZIP Project Imports

To improve import quality, keep the archive organized and avoid unnecessary files. Use clear page naming in the source project where possible, and verify internal links before exporting the ZIP. If the project is large, consider importing during a low-traffic maintenance window so the background job can run without interruption.

• Use a clean export with only necessary assets.
• Check that page links are relative and consistent.
• Review generated slugs and titles after import.
• Test responsive output across devices.

If you are migrating an existing site, compare the imported pages against the original structure before publishing. This helps ensure navigation, media, and design defaults are preserved as intended.