Conversion Guide

How to Export a Bolt.new Project: Downloads, GitHub, and StackBlitz Handoff

Every way to get code out of Bolt.new: the ZIP download, the StackBlitz workspace, and the GitHub push. What each contains and when to use it.

By AI to Wordpress Engineering Team·July 28, 2026·1,720 words
Expert-WrittenRegularly UpdatedSecurity Verified

Convert your website now

Upload ZIP → Security Scan → Free Preview → Download WordPress Theme

How AI to Wordpress Converts Your Website

1Upload ZIPLovable, Webflow,Framer, or HTMLMax 100 MB2Security ScanMalware detection,virus scanningAuto-reject threats3AIAI ConversionDOM → WordPresstemplate generation2-5 min avg4Preview & PayLive WP previewbefore purchaseDownload ZIP

1
How Bolt.new Actually Stores Your Project

How to Export a Bolt.new Project: Downloads, GitHub, and StackBlitz Handoff — visual guide for How Bolt.new Actually Stores Your Project

Visual Guide: How Bolt.new Actually Stores Your Project

This section includes step-by-step visual guidance for optimal results.

Bolt runs on StackBlitz's WebContainers, which means your project has a real Node filesystem inside the browser tab. This design is why Bolt export is unusually clean: what you see in the file tree is what ends up in the ZIP. There's no server-side compilation step or platform-specific wrapping — the download is genuinely a folder of code.

2
The Three Export Paths

Downloading the ZIP is the fastest path for one-off handoffs. Pushing to GitHub is the correct path for anything you plan to iterate on outside Bolt. Forking to StackBlitz keeps the project in-cloud but under a different (non-Bolt) editor. All three produce the same underlying source; the difference is where the source ends up living.

Pro Tip

Use your platform’s official export or download option and upload that ZIP directly. Keep all files together in one complete archive.

3
Using the ZIP Download

Click the download button in Bolt's top toolbar. A ZIP with the entire workspace saves to your machine within seconds. Unzip and you have a standard npm project. Verify with `npm install && npm run build` — a clean build here means a clean build inside the AI to Wordpress converter.

Technical Architecture

How AI to Wordpress Processes Your WebsiteSecure, isolated conversion pipeline from any builder to WordPressINPUT SOURCESLovableWebflowFramerReplitCursor AIV0.devBase44HTML/CSS/JSSECURE PIPELINEVirus ScanFile ValidationFramework DetectionDOM ParsingAI Structure MapTemplate GenerationQA ValidationOUTPUTWordPress Theme Filesheader.phpfront-page.phpstyle.cssfunctions.phpfooter.php🔍 Live PreviewFree — before payment⬇ Download ZIPAfter payment — yours forever

4
Using the GitHub Integration

Connect a GitHub account via Bolt's settings, choose or create a target repository, and let the initial push complete. Subsequent commits from inside Bolt land in the repo automatically. This gives you version history, PR workflows, and a clean handoff to any migration tool that accepts a GitHub URL — which the AI to Wordpress converter does.

5
What's Inside the Exported Project

The scaffold Bolt chose (usually Vite + React or Next.js), `package.json` with the exact dependencies Bolt installed, `src/` with components and pages, `public/` with static assets, framework config files, and any Tailwind or shadcn/ui configuration Bolt added. Environment variables from Bolt's runtime UI are excluded for security. Assets referenced in code are included via their actual file paths.

Security Note

Every file you upload is automatically scanned for malware before processing. Unsafe files are rejected immediately to protect your WordPress installation.

6
Running the Export Locally

Node 18 or higher and npm or pnpm are enough. `npm install` restores dependencies, `npm run dev` starts the Vite or Next dev server, `npm run build` produces the compiled output. Everything Bolt did inside its preview happens on your machine using the same tooling — nothing is Bolt-specific.

7
Feeding the Export Into the AI to Wordpress Converter

Paste the GitHub URL or drop the ZIP into the uploader. The pipeline installs dependencies, runs the build, pre-renders every route with headless Chromium, and produces a WordPress theme with real HTML per page. Total time: three to seven minutes for a typical Bolt project.

8
Handling Bolt's Backend-Free Nature

Bolt is oriented toward frontend generation. If your Bolt project talks to Supabase, Airtable, or another BaaS, the compiled bundle keeps those calls working from any host — including WordPress — because the API integration lives in the JavaScript, not on Bolt's side. Add the WordPress domain to your BaaS's allowed origins and every request continues to fire.

Performance Tip

Minified CSS and JavaScript files convert more efficiently and produce cleaner WordPress themes. Use your builder's production export option.

9
Iterating After Export

Two workflows coexist happily. Iterate in Bolt for prompt-driven changes, or edit locally after export for engineering work. If you use GitHub as the source of truth (recommended), both workflows can happen in parallel without stepping on each other. Re-run the WordPress conversion when the design changes meaningfully.

Your Files Are Always Secure

Malware scanned before processing
Sandboxed conversion environment
Per-user data isolation
Auto-deleted after 72 hours

Frequently Asked Questions

Does Bolt.new give me the complete source code?
Yes. Because Bolt is built on top of StackBlitz WebContainers, everything runs against a real filesystem you can see, edit, and download. The download button ships every file in the workspace, not a subset.
Do I need a paid Bolt account to export?
Basic export works on the free tier. Paid plans unlock higher token limits, longer sessions, and larger project sizes, but do not gate the export itself. If you can see the code, you can download it.
Is the download a normal npm project?
Yes. Standard Vite + React (or Next.js if Bolt chose that scaffold) with `package.json`, `src/`, `public/`, config files, and everything else you'd expect. `npm install && npm run dev` works locally without any Bolt-specific tooling.
Can I push my Bolt project directly to GitHub?
Yes. Bolt integrates with GitHub via StackBlitz's connectors. Authorise the connection once and every subsequent commit inside Bolt lands in the repo. This is the recommended path for engineering work and migrations, because it preserves history and avoids the timeout risk of large ZIP downloads.
What's the difference between exporting from Bolt and forking to StackBlitz?
Exporting downloads the code to your machine. Forking to StackBlitz keeps the project inside StackBlitz's environment but under your own account, which is useful if you want to continue development in StackBlitz's more traditional IDE without Bolt's AI layer. Both preserve the same underlying source.
Are runtime secrets or API keys included in the export?
Only if you put them in a committed `.env` file. Secrets set via Bolt's UI as runtime env vars are excluded from the export. Re-create them locally in `.env.local` after downloading. This is safer than the alternative — you don't want secrets in a downloaded ZIP.
Can I re-import a modified export back into Bolt?
The cleanest path is via GitHub. Push your local changes to the connected repo and open the repo inside StackBlitz — Bolt will pick up the new state. Direct ZIP re-imports are not supported; the flow is designed around GitHub as the source of truth once you leave Bolt's editor.
Does the export include Bolt's chat history?
No. Bolt-side conversations, prompts, and AI chat transcripts stay inside Bolt's workspace and are not part of the source. The export is production code only.

Ready to Convert Your Website?

Secure upload with malware scanning. Free preview before purchase. WordPress theme in minutes.

Conversion Guides by Builder

Lovable

→ WordPress Guide

Webflow

→ WordPress Guide

Framer

→ WordPress Guide

Replit

→ WordPress Guide

Cursor AI

→ WordPress Guide

V0.dev

→ WordPress Guide

Base44

→ WordPress Guide

Bolt.new

→ WordPress Guide

Google AI Studio

→ WordPress Guide

Static HTML

→ WordPress Guide

Claude

→ WordPress Guide

React

→ WordPress Guide

Next.js

→ WordPress Guide

Related Articles

Migrate Bolt.new to WordPress: A Practical Migration Guide

Move a StackBlitz Bolt.new project into WordPress without losing design, routes, or SEO. Build steps, assets, hydration, plugins and cutover playbook.

Read the full guide

Bolt.new: In-Depth Review, Use Cases & WordPress Conversion Guide

Complete Bolt.new review — StackBlitz's AI coding platform that generates full-stack apps in your browser. Features, pricing, limitations, and WordPress conversion walkthrough.

Read the full guide

How to Convert Any Website to WordPress — Complete Guide

The definitive guide to converting websites from any builder to WordPress. Compare methods, learn the process, and get your WordPress theme in minutes.

Read the full guide

Manual vs AI Website Conversion: Complete Comparison

Compare hiring a developer versus using AI tools like AI to Wordpress. See costs, timelines, quality differences, and when to choose each approach.

Read the full guide

Explore More

All Guides Security Technology Pricing Converted Websites

Convert by Platform

Lovable → WordPressWebflow → WordPressFramer → WordPressReplit → WordPressCursor AI → WordPressV0.dev → WordPressBase44 → WordPressBolt.new → WordPress