You can export your work from Bolt.new and import it into Bolt.diy, but the process depends on what you built

Bolt.new and Bolt.diy are both AI-powered code editors, but they are separate platforms with different underlying systems. Bolt.new is made by StackBlitz and runs projects in the browser. Bolt.diy is a self-hosted alternative that you run on your own computer or server. Moving a project between them is not automatic — you need to export the code from Bolt.new first, then set it up in Bolt.diy as a new project.

The simplest projects move cleanly. A static website, a React app, or a Node.js backend will usually work in both places once you copy the files over. Projects that rely on Bolt.new's specific features — like its built-in preview server or certain integrations — may need adjustments before they run in Bolt.diy.

Key Takeaways

  • Export your project from Bolt.new by downloading the files as a ZIP or cloning the repository if it is connected to GitHub.
  • Bolt.diy runs on your own machine, so you need to have Node.js installed and understand how to navigate your file system.
  • Most web projects move without changes, but projects using Bolt.new-specific features may need you to adjust configuration files or dependencies.
  • If your project uses environment variables or API keys, you will need to set those up again in Bolt.diy's environment file.

Export your project from Bolt.new

Open your project in Bolt.new and look for the menu icon (three horizontal lines) in the top left corner. Click it and select Export or read — the exact wording depends on which version of Bolt.new you are using. This downloads all your project files as a single ZIP file to your computer.

If your Bolt.new project is connected to a GitHub repository, you can clone that repository instead. This is faster if you have Git installed on your computer, and it preserves the version history. Open a terminal, navigate to the folder where you want to work, and run git clone [your-repository-url]. Replace the bracketed part with the actual URL from your GitHub project.

Extract the ZIP file to a folder on your computer if you downloaded it. You should now have a folder containing your project files — typically including package.json, src, public, and other standard web project folders.

Install Bolt.diy on your computer

Bolt.diy runs locally, which means it needs to be installed on the machine where you want to work. Start by installing Node.js if you do not have it already. Go to nodejs.org, read the LTS (Long Term Support) version, and follow the installer. This gives you Node.js and npm, the package manager you will need.

Next, clone or read Bolt.diy itself. The official repository is on GitHub at bolt-diy. Open a terminal, navigate to the folder where you want to keep Bolt.diy, and run git clone https://github.com/stackblitz-labs/bolt.diy.git. Then navigate into that folder with cd bolt.diy and run npm install to read all the dependencies Bolt.diy needs to run.

Once installation finishes, start Bolt.diy by running npm run dev. This opens a local server, usually at http://localhost:5173 or a similar address. Your terminal will show you the exact URL. Open that address in your web browser, and you will see the Bolt.diy interface.

Create a new project in Bolt.diy and add your files

In Bolt.diy, click the button to create a new project or open an existing folder. Choose the option to open a folder from your computer, then navigate to the folder containing your exported Bolt.new project. Bolt.diy will load all the files and display them in the file tree on the left side.

If you prefer to start fresh, create a new empty project in Bolt.diy, then manually copy your files into the project folder. Open your file explorer, navigate to where Bolt.diy stores projects on your computer, and paste your exported files there. Refresh Bolt.diy in your browser, and the files will appear.

Check dependencies and configuration files

Look at the package.json file in your project. This file lists all the packages your project depends on. In Bolt.diy, open a terminal within the interface (or open your system terminal in the project folder) and run npm install. This downloads all the packages listed in package.json so your project can run.

If your project uses environment variables — API keys, database URLs, or other secrets — you will need to set those up again. Look for a file named .env or .env.local. If it exists, open it and check what variables are defined. Create or update this file in your Bolt.diy project with the same variable names and values. Never commit this file to GitHub, as it contains sensitive information.

Some projects may have a vite.config.js or webpack.config.js file that tells the build tool how to run your code. These usually work the same in Bolt.diy as they did in Bolt.new, but if you see errors when you try to run the project, check these files for any Bolt.new-specific settings that need to be removed or changed.

Start the development server and test your project

In Bolt.diy, look for a button labeled Run or Start, or open the terminal and run npm run dev or npm start depending on what your package.json defines. The development server will start, and you should see a preview of your project in the right panel of Bolt.diy.

Test your project thoroughly. Click through all the pages, try all the buttons, and check the browser console for errors. If something does not work, the error message will usually tell you what is wrong. Common issues include missing dependencies (fix by running npm install again), incorrect file paths, or environment variables that are not set.

If your project uses a database or external API, make sure those services are running and that your connection strings are correct. Bolt.diy cannot access services that only work inside Bolt.new's environment, so you may need to set up your own local database or use a cloud service instead.

Push your project to GitHub for backup and collaboration

Once your project is working in Bolt.diy, push it to GitHub so you have a backup and can work on it from other machines. If your project folder is not already a Git repository, open a terminal in that folder and run git init. Then run git add . to stage all files, git commit -m "Initial commit" to create your first commit, and git remote add origin [your-github-url] to connect to your GitHub repository.

Finally, run git push -u origin main to upload your code to GitHub. From now on, you can pull changes from GitHub into Bolt.diy whenever you want to sync, and push changes back up to keep your repository current.

Frequently Asked Questions

What if my Bolt.new project uses features that do not exist in Bolt.diy?

Bolt.new has some built-in features like when ready preview and certain integrations that Bolt.diy may not have. If your project relies on these, you may need to find alternatives or adjust how your code works. Most standard web projects will run fine, but check the Bolt.diy documentation for what is supported.

Do I need to keep Bolt.new running while I work in Bolt.diy?

No. Once you export your project, you can close Bolt.new completely. Bolt.diy is independent and does not need Bolt.new to be open. You can work entirely in Bolt.diy on your own computer.

Can I move a project back from Bolt.diy to Bolt.new?

Yes. Export your files from Bolt.diy the same way you would any folder on your computer, then upload them to Bolt.new by creating a new project and importing the files. The process is the same in reverse.

What if I get an error when I try to run the project in Bolt.diy?

Read the error message carefully — it usually tells you what is wrong. Common fixes include running npm install again, checking that Node.js is installed, making sure environment variables are set, and verifying that file paths are correct. If the error mentions a missing package, that package name is usually in the error message.

Do I need to pay for Bolt.diy?

Bolt.diy is open source and free to use. You run it on your own computer, so there are no subscription fees. You only need to have Node.js installed, which is also free.