Troubleshooting AI Hosting uploads

If a prepared ZIP won't upload to AI Hosting, check the error shown on the upload screen. Many errors can be fixed by giving the message to your AI tool and exporting a corrected website package.

For the normal process, see how to upload a website. If you're editing a saved version, see how to update your website and upload a new version.

The ZIP is too large

The ZIP itself must be no larger than 100 MB. Its extracted contents must also fit within 100 MB, with no more than 1,000 files and 20 MB per file. A ZIP under 100 MB can still fail because it expands beyond a limit.

Storage allowance or package limit reached

Your Package storage allowance covers all saved packages and their assets at their extracted size. You can keep up to 20 packages. A scheduled downgrade can also restrict another upload.

Review your saved packages and remove an unused version if appropriate. After setup, the active package must be taken offline or replaced by another active package before it can be removed. During the setup wizard, Remove package can remove the uploaded package directly. If that package is active, removing it takes your website offline. Removing a package keeps its saved messages.

Missing index.html or webfactory.json

Both files must be at the top level of your website files. The ZIP can contain them directly, or use one enclosing folder containing the entire website. AI Hosting removes that single enclosing folder during upload; extra nested folders can leave the required files at the wrong level. A missing or invalid webfactory.json usually means the package needs preparing again. The manifest must describe the supported pages or single-page routing and forms.

Unsupported files, paths or assets

AI Hosting needs the compiled static website, rather than a source project containing dependencies. Server-side code, encrypted ZIPs, symbolic links and special files are unsupported. File names must use simple letters, numbers, dots, dashes and underscores; spaces and hidden project folders can cause validation errors.

Missing images, styles or scripts must be included in the export. Some asset-path errors require relative URLs. Give the exact error to your AI tool so it can correct the affected file.

Forms or embedded content rejected

Forms must be prepared for AI Hosting and declared in webfactory.json. File attachments in forms aren't supported. Embedded pages, base tags and automatic HTML page redirects can also cause validation errors. The preparation prompt helps your AI tool produce a compatible export.

Uploaded, but couldn't be set active

The upload can succeed even when automatic activation fails. The package is still saved. Check Website packages and follow how to choose your live website; avoid uploading the same ZIP again just to activate it.

Recover from a rejected ZIP

Use these steps when the error requires changes to the exported website.

Step 1

Read the error on the upload screen and copy its exact wording.

Step 2

Open the AI conversation used to prepare this website. Give your AI tool the error and ask it to correct the export while preserving your website.

Step 3

In AI Hosting, open Add new website package and select Run the preparation prompt. Copy the prompt and run it in that AI conversation.

Step 4

Export one corrected ZIP containing index.html, webfactory.json and all required assets at the correct paths.

Step 5

Return to the upload screen, enter a Package name and choose the corrected ZIP. Clear Make this package active after upload so you can preview the corrected version before publishing.

Step 6

Select Upload package. Check the result and preview the saved website before making it active.

Still unable to upload?

Contact our support team with the error message, package name and the point where the upload stops. If the package is saved but the website still shows an older version, check which package is active before trying another upload.