Generated and Imported Assets

Summary: Learn where Antimanual Builder Pro stores generated and imported assets, how temporary chunk uploads are handled, and which security controls protect imports. This guide explains asset locations, cleanup behavior, and practical best practices for managing imported files across simple and large site workflows.

Generated and imported assets in Antimanual Builder Pro are stored in a structured WordPress uploads-based workflow that keeps imported media, project files, and temporary chunk data organized. This section explains where assets live, how they are handled during import, and why the system is designed to support safer, cleaner page building.

Where Generated and Imported Assets Are Stored

Antimanual Builder Pro stores generated and imported assets under the WordPress uploads directory, specifically in the Antimanual Builder folder structure. The main asset location is:

wp-content/uploads/antimanual-builder/

This location keeps builder-managed files separate from theme files and other site content. As a result, imported pages, media references, and generated project files remain easier to track during troubleshooting, migration, or cleanup.

For large imports, chunked upload data is assembled in a protected temporary directory:

wp-content/uploads/ambld-import-chunks/

This folder is restricted from direct web access and is cleaned up after the import completes.

How Asset Storage Supports Import Workflows

Asset storage is designed to support both manual editing and import-based workflows. Whether you create a page from scratch, migrate a single HTML file, or import a larger ZIP project, the builder uses the same organized storage model.

• Imported assets are separated from standard WordPress uploads.
• Temporary chunk files are handled in a protected location.
• Cleanup after import reduces storage clutter.
• Consistent file organization simplifies debugging and maintenance.

For teams managing repeated sections or shared components, this structure also helps preserve imported resources in a predictable location. is especially relevant when you want to reuse a saved section across multiple pages.

What Happens During Large Imports

When you import a large site, Antimanual Builder Pro may stream the upload in chunks rather than processing the entire archive in one request. This reduces timeout risk on slower servers and makes large imports more reliable.

During this process, the system assembles temporary data in the protected chunk directory, then moves the processed assets into the main Antimanual Builder uploads folder. Background jobs and per-page previews help you monitor progress while the import continues.

• Chunked uploads are used for large archives.
• Progress is handled in the background.
• Per-page previews can show results as files are processed.
• Temporary chunks are removed after completion.

If you are preparing a site migration, provides the operational context for handling larger imports without overloading the server.

Security Controls for Imported Assets

Asset handling in Antimanual Builder Pro is built around controlled import processing rather than arbitrary file execution. The plugin applies security checks during save and render operations to reduce the risk of unsafe markup being stored or displayed.

Import routes require authorized access, and jobs are tied to the user who started them. In addition, imported markup is sanitized using a script-free allowlist, and event-handler attributes are stripped before the content is saved or rendered.

• Only authorized users can run import tasks.
• Import endpoints require capability checks.
• Active Pro license validation is required for import routes.
• Sanitization runs at save and render time.

For a broader explanation of how content is filtered and stored, The Advantages and Disadvantages of Developing a Custom WordPress Theme is the best companion section to review.

Best Practices for Managing Imported Assets

To keep imported assets manageable, use small test imports before processing a large archive. This helps confirm that images, structure, and references resolve correctly on your server.

• Start with a small HTML file or limited ZIP project.
• Check whether source assets are organized before import.
• Use clear file and page naming in the source project.
• Review imported media paths after the build completes.
• Remove unused temporary files if a test import is discarded.

If your workflow includes migrating existing pages, decide early whether to replace the original page or keep a copy. That choice affects testing, rollback, and redirects after launch.

Common Questions About Asset Storage

Are imported assets stored in the media library? Imported and generated assets are stored in the Antimanual Builder uploads structure. Depending on the import type, some files may also be referenced by the page content or related builder output.

Can chunk storage be accessed directly? No. The temporary import-chunks folder is protected from direct web access and is intended only for internal processing during import.

Do imported files remain forever? The main assets remain available for the site, but temporary chunked upload data is removed after the import finishes.

For users who are deciding between different migration methods, offers a useful comparison of how one-page imports are handled.

Summary

Generated and imported assets in Antimanual Builder Pro are stored in a structured uploads-based system that supports safe processing, easier maintenance, and cleaner migrations. Main assets stay organized under the Antimanual Builder folder, temporary chunk data is protected, and built-in sanitization helps ensure imported content is handled securely.