Export the project
Bolt support currently documents opening the project title menu at the top left and choosing Export > Download. The ZIP contains source files, which may still need a build before a browser can load them.
Bolt.new export hosting · Updated October 4, 2026
Turn a Bolt.new Export Into a Shareable Preview Link
Build the static frontend, upload its output, and give a client or teammate a browser link to review. HTMLShare previews the files you upload; it does not run the Bolt source project or move its backend.
How to host a Bolt.new export
The reliable path is export → build when needed → upload the browser-ready files. The source ZIP and the finished static output are different artifacts.
Check the project type
A self-contained HTML page can be uploaded as-is. For Vite, React, Svelte, or another framework, check package.json and follow the project's production build instructions.
Build the static frontend
Run the build locally with the package manager and script the project specifies. A typical Vite app uses npm run build and writes its static output to dist/.
ZIP the output
Upload the generated static files, not src/ or node_modules/. Keep index.html and its assets together, with the entry file at the archive root or one folder deep.
Publish and review
Upload the ZIP to HTMLShare, open the preview URL, and check links, styles, scripts, and responsive behavior before sending it to a reviewer.
Does your Bolt project need a build step?
Check the files Bolt exported rather than guessing from the project name. A browser can load static HTML and its assets; framework source usually needs to be compiled first.
Plain HTML, CSS, and JavaScript
If index.html already references browser-ready files and there is no build script, keep the page and its assets together and upload that static project.
Vite or another frontend framework
Build the project first. For Vite, the standard output is dist/. For another framework, use its configured static build output and verify that it contains index.html and the generated assets.
Next.js or server-backed app
A server-rendered app is not a static upload. It can only use static hosting if it supports a static export and the exported site does not depend on server routes, server actions, or runtime features.
A common Vite build
Use the package manager and scripts shown by your project. For a typical npm-based Vite project, build locally and upload the generated dist/ files:
npm install
npm run build
# Upload the generated files in dist/Vite's production build creates static files for static hosting. If the app is deployed under a path instead of a domain root, check its base-path setting before rebuilding.
Why does a Bolt export show a blank page?
A blank screen often means the browser received source files or an incomplete build. Check the archive and browser console before rebuilding.
The source ZIP was uploaded
A source project may contain TypeScript, JSX, or module imports that need a build tool. Build it first, then upload the generated static output.
The entry file is nested too deeply
Check the ZIP contents and make sure index.html is at the root or directly inside one enclosing folder, with the assets beside it.
Styles or scripts cannot load
Look for localhost URLs, machine-specific file paths, or asset paths that do not match the hosted page. Rebuild with the correct public base path if your framework requires one.
The page expects a backend or private setting
A static build cannot start an API server or read private environment variables at runtime. Check the browser console and keep server-side secrets out of frontend code.
Share a Bolt.new app without GitHub
GitHub and a Vercel project are not required for a static review link. Export and build the frontend on your machine, then upload the output ZIP. This route is for a browser preview; choose production hosting if the app needs server code, deployment automation, or a permanent production setup.
- Build from the downloaded project with its existing package manager.
- Upload only the static output, keeping index.html and assets together.
- Send the preview URL instead of asking reviewers to run the project locally.
Bolt preview, HTMLShare, or production hosting?
Bolt preview or built-in publishing
Keep iterating inside Bolt and share work through its own workflow.
Boundary: The project remains connected to Bolt's builder and publishing choices.
HTMLShare preview link
Hand off a browser-ready static frontend for client review, QA, or a quick demo.
Boundary: It serves uploaded static files; it does not build source code or run a backend.
Production app hosting
Run server code, API routes, authentication, databases, CI/CD, or a long-lived production site.
Boundary: Choose a platform and deployment setup that supports the app's runtime needs.
What static hosting will not run
A static preview serves files to the browser. It does not start or migrate the services that may power a Bolt app.
- Server routes, server functions, or a persistent Node.js process.
- Databases, authentication servers, or private backend services.
- Private environment variables or API secrets. Frontend build variables can be visible to visitors.
Browser code may still call an external API you host elsewhere, subject to that service's configuration. Keep credentials server-side and use a production platform when the app needs a runtime.
Treat a preview URL as shareable: do not include credentials or confidential client data in the build.
FAQ
Common questions
How do I host a Bolt.new export?
Export the project, build its static frontend if it uses a framework, ZIP the generated output with index.html and its assets, then upload that ZIP to HTMLShare and share the preview URL.
Can I upload a Bolt.new ZIP directly?
Only when the ZIP already contains browser-ready static files. If it contains a source project with package.json, src/, or unbuilt JSX and TypeScript, build it first and upload the output folder instead.
Does a Bolt.new export need to be built first?
Plain HTML may be ready as-is. Vite and other framework projects generally need their production build command before they become static files a browser can load.
Why is my Bolt.new export blank?
Common causes include uploading source instead of the build, a nested or missing index.html, broken asset paths, or frontend code that expects a server or environment value that is not available in a static preview.
Can I host Bolt.new without GitHub or Vercel?
Yes, for a static review preview. Export and build the project on your machine, then upload the static output. A server-backed production app still needs a host that runs its server features.
Can I share a Bolt.new app with a client?
Yes, when the client needs to review the static frontend. Send the HTMLShare URL so they can open it in a browser without downloading the project or running a local server.
Can I preview a Bolt app on a phone?
Yes. Open the published URL on the phone or scan the QR code shown on HTMLShare's publish result screen, then check the layout and interactions on the actual device.
Will static hosting run my Bolt backend or database?
No. The preview contains the uploaded browser files. APIs, databases, authentication services, server functions, and private secrets must remain on or move to services designed to run them.
Have a built Bolt frontend?
Upload its static output, open the preview on your devices, and send one link for review. Move to production hosting when the project needs a backend or server runtime.