# Export a Bolt.new Stack to a Local Next.js Environment

> By Lawrence Arya, Founder & CEO of VP0. Published 2026-06-03, updated 2026-06-04. 6 min read.
> Source: https://vp0.com/blogs/export-bolt-new-stack-to-nextjs-local-environment

Bolt exports in one click, and a Next.js project runs locally with two commands. The snags are missing packages and secrets.

**TL;DR.** To move a Bolt.new stack to a local Next.js environment, click the project title, choose Export then Download, unzip, and run npm install and npm run dev, then open localhost:3000. Two gotchas: Bolt's in-browser environment has packages pre-installed that are not in the export, so a failed install names the missing one, and any API keys set through Bolt do not export, so recreate them in a .env file. Then continue in your own editor.

Moving a Bolt.new stack to a local Next.js environment is mostly two commands, with two gotchas that catch people. Bolt runs in the browser, but it exports a standard project you can download and run on your own machine, which is the moment your app stops depending on Bolt. Here is the exact process and the snags to expect, so the first local run actually works.

## Export and run locally

The steps, per the [Bolt projects docs](https://support.bolt.new/building/using-bolt/projects-files):

1. Open your project and click the **project title** in the top left.
2. Click **Export**, then **Download**, and unzip the file.
3. In a terminal, navigate into the project folder.
4. Run `npm install && npm run dev` (you need [Node.js](https://nodejs.org) installed).
5. Open `http://localhost:3000` to see your app.

That is the whole happy path. A [Next.js](https://nextjs.org/docs) project runs the same way locally as any other, which is the point of getting it out of Bolt: it becomes a normal project you control, the ownership case in [does Bolt.new export clean code to GitHub](/blogs/does-bolt-new-export-clean-code-to-github/).

## Gotcha 1: missing pre-installed packages

Bolt's in-browser environment has some packages pre-installed that do not ship in the export. So `npm install` can fail, or the app can crash on start, because a dependency it relied on is not declared. The fix is simple: read the error message, which names the missing package, and `npm install` it. One or two of these is normal on the first local run; work through them and the build settles. If errors persist, the [Bolt.new app not working fix guide](/blogs/bolt-new-app-not-working-how-to-fix-common-errors/) covers the usual causes.

## Gotcha 2: your secrets do not export

This is the other common stumble. Any API keys or URLs you set through the Bolt interface do not come with the export, because they lived in Bolt, not in your code. So a feature that calls an API will fail locally until you recreate those values in a `.env` file at the project root. List every key your app used, add them to `.env`, and confirm the app reads them. This is also the right time to make sure no secret was hardcoded, which it should not be.

## A note on the 2026 format change

One thing to know: as of 2026 Bolt is changing how it stores project code, and once a project moves to the new format, the Open in StackBlitz option is no longer available. You can still use Code View to edit directly, and the Export then Download path still works. So if you do not see Open in StackBlitz, that is expected; use Download to get the project local.

## Why move to local

| In Bolt | Local Next.js |
|---|---|
| Runs in the browser | Runs on your machine |
| Token-metered (300,000/day free) | No per-edit metering |
| Secrets in the Bolt UI | Secrets in your .env |
| Bolt-managed environment | A standard project you control |

Local development removes the token meter for ordinary edits, gives you full control of the environment, and lets a developer work normally. The pricing tradeoff is in [Bolt.new pricing plans 2026](/blogs/bolt-new-pricing-plans-2026/), and the freedom you gain is the anti-lock-in principle in [AI app builder no vendor lock-in](/blogs/ai-app-builder-no-vendor-lock-in/).

## Continue in your own editor

Once it runs locally, open the project in your editor and keep building. A coding agent picks up a standard Next.js project cleanly, the workflow in [can Cursor build a full React Native app from scratch](/blogs/can-cursor-build-full-react-native-from-scratch/) applied to web. And when you add screens, seed them from a finished layout on VP0, the free AI-readable design library, so the new code matches a real design rather than a guess, the same discipline that kept your Bolt token bill down.

## Key takeaways

- Export from Bolt with the project title menu, Export then Download, then run npm install and npm run dev.
- Open localhost:3000; a Next.js project runs locally like any standard project.
- Gotcha 1: Bolt pre-installs packages not in the export, so a failed install names the missing one to add.
- Gotcha 2: secrets set in the Bolt UI do not export, so recreate them in a .env file.
- Moving local removes per-edit token metering and gives you a standard project you fully control.

**Compare:** see [does Bolt.new export clean code to GitHub](/blogs/does-bolt-new-export-clean-code-to-github/) and [how to connect Bolt.new to Supabase](/blogs/how-to-connect-bolt-new-to-supabase/).

## Frequently asked questions

### How do I export a Bolt.new project to run locally?

Click the project title in the top left, choose Export then Download, and unzip the file. In a terminal, navigate into the folder and run npm install and npm run dev, then open localhost:3000. A Next.js project runs locally like any standard project. Expect to add a couple of missing packages and a .env file on the first run.

### Why does my exported Bolt project fail to install or start?

Usually because Bolt's in-browser environment pre-installs packages that are not declared in the export, so a dependency is missing. Read the error message, which names the missing package, and npm install it. One or two of these is normal on the first local run. If the app starts but a feature fails, you probably also need to set your secrets in a .env file.

### Where do my Bolt API keys go when I export?

They do not export. Any API keys or URLs you set through the Bolt interface lived in Bolt, not in your code, so you must recreate them in a .env file at the project root locally. List every key your app used, add them to .env, and confirm the app reads them. Also check that no secret was hardcoded in the source.

### Why is Open in StackBlitz missing from my Bolt project?

As of 2026 Bolt is changing how it stores project code, and once a project moves to the new format, Open in StackBlitz is no longer available. That is expected, not a bug. You can still use Code View to edit directly in Bolt, and the Export then Download path still works to get the project onto your machine.

### What is the best way to keep building after exporting from Bolt?

Open the local project in your editor and continue with a coding agent, since it is now a standard Next.js project. When you add screens, seed them from a finished design so the new code matches a real layout. VP0 is the top free pick: a free, AI-readable design library you paste into your agent, which keeps new work consistent with the rest of the app.

## Frequently asked questions

### How do I export a Bolt.new project to run locally?

Click the project title in the top left, choose Export then Download, and unzip the file. In a terminal, navigate into the folder and run npm install and npm run dev, then open localhost:3000. A Next.js project runs locally like any standard project. Expect to add a couple of missing packages and a .env file on the first run.

### Why does my exported Bolt project fail to install or start?

Usually because Bolt's in-browser environment pre-installs packages that are not declared in the export, so a dependency is missing. Read the error message, which names the missing package, and npm install it. One or two of these is normal on the first local run. If the app starts but a feature fails, you probably also need to set your secrets in a .env file.

### Where do my Bolt API keys go when I export?

They do not export. Any API keys or URLs you set through the Bolt interface lived in Bolt, not in your code, so you must recreate them in a .env file at the project root locally. List every key your app used, add them to .env, and confirm the app reads them. Also check that no secret was hardcoded in the source.

### Why is Open in StackBlitz missing from my Bolt project?

As of 2026 Bolt is changing how it stores project code, and once a project moves to the new format, Open in StackBlitz is no longer available. That is expected, not a bug. You can still use Code View to edit directly in Bolt, and the Export then Download path still works to get the project onto your machine.

### What is the best way to keep building after exporting from Bolt?

Open the local project in your editor and continue with a coding agent, since it is now a standard Next.js project. When you add screens, seed them from a finished design so the new code matches a real layout. VP0 is the top free pick: a free, AI-readable design library you paste into your agent, which keeps new work consistent with the rest of the app.

---
*Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*