You can export a project from Bolt.new and import it into Bolt.diy, but the process requires manual steps because the two platforms don't sync automatically

Bolt.new and Bolt.diy are separate AI coding environments built by the same company. Projects created in Bolt.new live only in that workspace unless you export them. To move a project to Bolt.diy, you download the files from Bolt.new, then upload them to Bolt.diy as a new project. The transfer takes a few minutes and preserves your code, but you'll need to set up the project structure in Bolt.diy from scratch.

Both platforms use the same underlying technology, so code written in one usually runs in the other without changes. The main difference is that Bolt.new stores projects in the cloud under your account, while Bolt.diy works with local files on your computer. Understanding this difference explains why import isn't a single button — you're moving from cloud storage to file storage.

Key Takeaways

  • Export your Bolt.new project by downloading all files as a ZIP archive from the project menu.
  • Unzip the downloaded file on your computer to access the individual project files.
  • Open Bolt.diy and create a new project, then upload or paste your files into the workspace.
  • Test your project in Bolt.diy after import to confirm all files transferred correctly and dependencies are intact.
  • Keep your original Bolt.new project as a backup until you've confirmed the Bolt.diy version works.

Export your project from Bolt.new

Open the Bolt.new project you want to move. Look for a menu icon (usually three dots or a hamburger menu) in the top right or top left of the interface. Click it and find the option labeled "Export" or "Download project". Bolt.new will package all your project files into a single ZIP file and download it to your computer's default Downloads folder.

The ZIP file contains every file in your project: HTML, CSS, JavaScript, configuration files, and any other assets you've added. The file size depends on how many files and assets your project includes, but most projects download in seconds. Don't delete this file until you've confirmed the import worked in Bolt.diy.

Unzip the files on your computer

Locate the downloaded ZIP file in your Downloads folder or wherever your browser saves files. Right-click the file and select "Extract All" on Windows or double-click it on Mac — the operating system will unzip it automatically. A new folder with your project name will appear in the same location. Open this folder to see all the individual files inside.

Look for a file named package.json or index.html — this tells you the project structure is intact. If you see a folder inside the extracted folder with the same name as your project, open that inner folder instead. Some exports nest the files one level deep, and you want to work with the folder that contains the actual code files, not an empty wrapper.

Create a new project in Bolt.diy

Go to Bolt.diy in your web browser and start a new project. You'll see an empty workspace with a code editor on one side and a preview pane on the other. Bolt.diy will ask you to name the project — use the same name as your Bolt.new project to keep things organized, or choose a new name if you prefer.

The new project starts with a basic file structure. You can either replace these starter files with your own or add your files alongside them. Most users find it easier to delete the starter files first, then add their own code. This prevents confusion about which files are actually part of your project.

Upload or paste your files into Bolt.diy

Bolt.diy has two ways to add files: upload or paste. To upload, look for a file menu or upload button in the interface — this varies depending on the version you're using. Click it and select the files from your unzipped folder. You can usually select multiple files at once by holding Ctrl (Windows) or Cmd (Mac) while clicking each file.

If upload isn't available or you prefer to paste, open each file from your unzipped folder in a text editor (Notepad, VS Code, or any plain-text editor works). Copy the contents, then create a new file in Bolt.diy with the same name and paste the code in. This method is slower for large projects but works reliably. Make sure file names match exactly — index.html is different from Index.html on most systems.

Pay attention to the file structure. If your Bolt.new project had files organized in folders (like a src folder or assets folder), recreate that same folder structure in Bolt.diy. Incorrect folder paths will break links between files and cause your project to fail when you run it.

Check dependencies and configuration files

If your project uses external libraries or packages, look for a package.json file in your unzipped folder. This file lists all the dependencies your project needs. Upload or paste this file into Bolt.diy exactly as it appears. Bolt.diy will read the file and install the packages automatically when you run the project.

If you see a .env file or any configuration file with secrets or API keys, do not upload it to Bolt.diy. Instead, manually add those values to Bolt.diy's environment settings or configuration panel. This keeps sensitive information secure and prevents accidental exposure if you share your project later.

Test your project in Bolt.diy

Once all files are in place, click the Run or Preview button in Bolt.diy. The preview pane should display your project the same way it appeared in Bolt.new. Click through all the features and test every button, form, and interaction to make sure nothing broke during the transfer.

If something doesn't work, check the browser console for error messages. Right-click in the preview pane, select "Inspect" or "Inspect Element", then click the Console tab. Error messages will tell you which file has a problem and what line the error is on. Common issues include incorrect file paths, missing files, or dependencies that didn't install. Fix these one at a time and test again after each fix.

If your project still doesn't work after checking errors, compare the file structure in Bolt.diy to your unzipped folder on your computer. Make sure every file is present and in the correct folder. Then check that all file names match exactly, including capitalization and file extensions.

Frequently Asked Questions

Can I import a Bolt.diy project back into Bolt.new?

Yes, but the process is reversed. Download your files from Bolt.diy, then upload them to Bolt.new as a new project. Bolt.new will create a cloud-based copy of your project. Both platforms support the same code, so your project should work in either direction.

What if my project uses npm packages or a build tool?

Upload your package.json file to Bolt.diy. The platform will install the packages listed in that file automatically. If your project requires a build step (like running webpack or Vite), check whether Bolt.diy supports it — most common build tools work, but some advanced configurations may not. Test your project after import to confirm everything installed correctly.

Do I need to keep my Bolt.new project after importing to Bolt.diy?

Keep it until you've tested the Bolt.diy version thoroughly and confirmed it works exactly as expected. Once you're certain the import was successful, you can delete the Bolt.new project if you want. Keeping both versions costs nothing and gives you a backup if you need to troubleshoot later.

What if some files didn't transfer correctly?

Check the browser console in Bolt.diy for error messages that point to missing or broken files. Compare your unzipped folder to the files showing in Bolt.diy's file list. Re-upload any missing files, and make sure file names and paths match exactly. If a file is too large, try uploading it in pieces or compressing it first.

Can I import multiple Bolt.new projects at once?

No, you must import one project at a time. Export each Bolt.new project separately, then create a new Bolt.diy project for each one. This takes longer for multiple projects, but ensures each one has its own clean workspace and configuration.