Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesTo export an AI Builder project, open it from Websites List, select Code in the editor, then choose Export code in the files sidebar and click Export. The download is a ZIP containing a Node.js project built with React and Vite. It does not include integrated backend data, and edits made after downloading cannot be imported back to continue AI prompting.
Export the project ZIP
- Sign in and open Websites List.
- Open the project you want to export.
- In the editor’s top navigation, select Code.
- Find Export code below the files sidebar.
- Click Export and wait for the download to be generated.
- Download the ZIP and extract it on the computer where you plan to work.
The export guide describes the generated project as a Node.js app built with React and Vite. Local manual editing requires coding knowledge and Node.js installed.
As an Amazon Associate I earn from qualifying purchases.
Know what the export does—and does not—preserve
Source code is not the same as backend data
The ZIP contains frontend and logic files, while integrated backend data is managed separately. The platform’s backend documentation says there is currently no direct tool to export that data. If you need records, form submissions, or user uploads, check the available backend options and plan for those separately before leaving the service; exporting source code alone does not migrate them.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Export is a one-way handoff for AI prompting
An edited export cannot be imported back into the builder to continue prompting. Treat the ZIP as a handoff for manual development or deployment elsewhere, rather than a round trip. Keep an untouched copy of the downloaded ZIP before changing files.
#1 Best Overall
Be careful with in-platform code edits
The editor exposes most of the project codebase, but not internal files. Changes to system files can cause website errors, and saved changes cannot automatically be reverted. Preserve a separate copy before editing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a deployment route
The project is not a ready-to-upload static site. Uploading its raw code directly to shared or cloud hosting will not work; choose a route that can run Node.js or build the project into static assets.
Quick Recap
Best Value
Rank #4
| Route | What it involves | Best fit |
|---|---|---|
| Node.js Web Apps | The export guide lists this option on eligible Business or Cloud hosting plans. | A managed deployment route, if your plan is eligible. |
| VPS | Upload the project to a VPS with Node.js available and configured. | More flexibility, with more server setup and maintenance responsibility. |
| Static files on shared or cloud hosting | Run npm run build with Vite, then upload the generated static HTML, CSS, and JavaScript files as a PHP/HTML website. |
When the project can operate as static assets and you can build it locally. |
Prepare before you leave the builder
- Download and preserve the original ZIP before making changes.
- Install Node.js on the computer you will use for local development.
- Decide whether deployment will run the Node.js project or use a Vite static build.
- Make a separate plan for backend records, submissions, and uploads; they are not included in the code ZIP.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
