Can I skip the local build?

Only if the project is plain HTML with no build step. Framework projects have to be built before they can be served as static files.

Will the backend work?

Anything needing a running server won't. Calls to external services from the browser are unaffected.

Why not use bolt's own deploy?

Use it when you want speed. Use this when you want a short address you picked, no dependency on the tool, and the option of a password.

How large can the project be?

Up to 100 MB for a whole site, which a typical build is nowhere near.

Can I roll back a bad build?

Yes. Every publish is kept as a version and you can make an earlier one live again.

Host your bolt.new project on an address you chose

bolt.new builds in the browser and offers to deploy. Download the build instead and publish it where the link is yours.

You can host:

Drop your bolt.new build here

Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site

Free to use, live at your-name.99helpers.site in about ten seconds.

Why you might not want to leave it there

bolt.new is remarkable at going from a sentence to a running app without leaving the browser. The deploy button at the end sends it to a generated subdomain, which is a fine place for a demo and a poor place for anything you want to still be able to point at in six months. Downloading the project takes one click, and from there the address is your decision.

What bolt.new gives you

A downloadable project zip containing the full source
A WebContainer preview running in your browser
One-click deployment to a generated subdomain

The subdomain is generated, not chosen

A string of random words is hard to say out loud and harder to remember.

Previews are tied to the session

What runs in the browser sandbox stops when the tab does. The deployed copy is separate, and so is its lifespan.

No access control

Public or nothing. There's no way to give a link to three people and nobody else.

Putting bolt.new output online

1
Download the project
Use the download button to get a zip of the source, and unpack it locally.
2
Build it
Run npm install then npm run build. You'll get a dist folder with an index.html and the assets it needs.
3
Drop that folder in
Drag dist into the box above, choose an address, and publish. Everything resolves the way it did in the preview.

Worth knowing

Publish dist, not the project root — the source and node_modules aren't served and won't fit.
Set base to / in vite.config before building so assets are found from the site root.
A bolt project talking to Supabase or an external API keeps working; those calls run in the visitor's browser.
Add a 404.html copy of index.html if the app uses client-side routes.
Publish successive builds to the same address so the link you shared always shows the latest.

Questions

Can I skip the local build?: Only if the project is plain HTML with no build step. Framework projects have to be built before they can be served as static files.
Will the backend work?: Anything needing a running server won't. Calls to external services from the browser are unaffected.
Why not use bolt's own deploy?: Use it when you want speed. Use this when you want a short address you picked, no dependency on the tool, and the option of a password.
How large can the project be?: Up to 100 MB for a whole site, which a typical build is nowhere near.
Can I roll back a bad build?: Yes. Every publish is kept as a version and you can make an earlier one live again.

Try it with what bolt.new just made you

Drop it in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.

Back to the top Every AI tool we cover

Hosting artifacts from other tools

Hosting guides by file type

Everything gets its own address on 99helpers.site — see AI artifact hosting for every tool or free file hosting for any file type.