Where Files Are Stored

Summary: Antimanual Builder stores imported and generated files inside WordPress uploads in dedicated folders. Learn where primary assets, temporary chunk uploads, and migration data are kept, why the structure matters, and how it helps administrators manage imports, troubleshoot projects, and maintain a cleaner site.

Imported and generated files in Antimanual Builder are stored inside the WordPress uploads directory, but they are separated from normal media and site content. This keeps migrations, AI-generated pages, and chunked uploads organized in dedicated folders so they are easier to manage, inspect, and clean up after an import completes.

Primary Storage Location

The main storage path for generated and imported assets is the Antimanual Builder folder inside uploads. In most installations, this follows the pattern wp-content/uploads/antimanual-builder/. Files placed here may include imported images, project assets, and other content collected during page creation or migration.

Because this location sits under the standard WordPress uploads structure, it works with familiar hosting and backup workflows while still keeping builder content separate from regular uploads. How to Fix the "Parent Theme Missing" Error After Installing Docy Theme

• WordPress uploads directory: the root storage area used by the plugin.
• Antimanual Builder folder: the primary destination for imported and generated assets.
• Separated storage: keeps builder files isolated from other site uploads.

Where Chunked Uploads Go

Large imports use chunked uploads so files can be transferred in smaller parts. These chunks are assembled in a protected temporary folder during the import process and are removed when the job finishes. This reduces timeout risk and helps the system handle larger archives more reliably.

The temporary chunk folder is intentionally restricted so it is not treated as normal site content. This design helps protect incomplete import data while the system rebuilds the final page or project structure.

• Chunked data is stored temporarily during upload and assembly.
• The folder is protected to reduce accidental exposure.
• Temporary files are cleaned up after the import completes.

Why This Storage Structure Matters

Keeping imported files in dedicated folders improves maintenance and troubleshooting. If you need to review how a project was processed, the separated storage layout makes it easier to locate related assets without searching through the entire uploads directory. It also helps preserve a cleaner media library for day-to-day site management.

This arrangement is especially useful for sites that perform repeated imports or manage larger archives. By isolating builder files, Antimanual Builder reduces the chance of conflicts with unrelated media, while still keeping all required assets available for rendering pages correctly.

• Cleaner organization for migrations and ongoing edits.
• Easier troubleshooting when reviewing imported content.
• Reduced clutter in the general WordPress media area.

What You May Find in These Folders

Depending on the type of import, the Antimanual Builder folders may contain referenced images, collected project assets, and other generated resources needed to reconstruct a page. For ZIP imports, the system also uses intermediate data while it analyzes the archive and prepares the final builder output.

In general, you should treat these folders as application-managed storage. Files are placed there automatically by the plugin, and temporary data is removed when no longer needed. If you are auditing storage after a migration, start by reviewing the main uploads path and then check the protected chunk directory if the import is still in progress.

Best Practices for Administrators

If you manage a site with Antimanual Builder, the safest approach is to let the plugin control its own storage. Avoid moving or renaming the dedicated folders unless you are following a supported maintenance procedure. Doing so may interrupt imports or make existing assets harder to resolve.

• Leave plugin-managed folders in their default locations.
• Check imports after completion to confirm assets were created correctly.
• Use the protected chunk folder only as temporary working storage.
• Review storage paths when troubleshooting migration issues.

Summary

Antimanual Builder stores imported and generated files under the WordPress uploads directory in dedicated folders, with temporary chunk data handled separately during large uploads. This structure keeps the workflow organized, limits exposure of in-progress files, and supports cleaner long-term management of builder content.