Can I publish a v0 preview directly?

No — you need the built files. Copy the component into a small project, build it, and publish the output folder.

No. Once it's built to static files it can be hosted anywhere, including here.

Will shadcn/ui components work?

Yes. They compile to ordinary HTML, CSS and JavaScript, which is all that gets served.

What about server actions?

Those need a server. Static hosting serves files only, so a generation relying on server actions won't work unaltered.

Can I use my own domain?

Sites are served on a subdomain of the hosting domain. That address is short, permanent and yours to choose.

Host your v0 generations on an address of your own

v0 gives you a component and a preview on their domain. Export it, build it, and publish it somewhere you control.

You can host:

Drop your v0 build folder 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

v0 turns a prompt into a real React component with a live preview, and for iterating that's exactly right. The preview URL is a different matter: it's long, it's on Vercel's domain, and it's framed as somewhere to look at your work rather than somewhere your work lives. Once the design has settled, it deserves a proper address.

What v0 gives you

React and Next.js components with shadcn/ui and Tailwind
A preview on a v0 subdomain
Code you can copy into a project of your own

Preview URLs read as scratch space

A long generated subdomain tells a client you're showing them a draft, even when you're showing them the finished thing.

It's still inside the tool

Your work stays coupled to the account that made it, and to whatever that account's status is next month.

No control over access

You can't put a password on a preview and hand it to three specific people, which is often exactly the requirement.

Putting v0 output online

1
Get the code out
Copy the component into a project — a small Vite or Next setup is plenty — and make sure it renders on its own.
2
Build a static version
Run the build. For Next, use static export; for Vite, npm run build. You want a folder with an index.html in it.
3
Drop it in and publish
Drag the output folder into the box above, pick a short address, and it's live.

Worth knowing

Tailwind classes need the compiled stylesheet — publish the build output, not the raw component file.
v0 components often assume Next's font and image helpers; a plain Vite setup avoids that and builds smaller.
Static export is the setting to reach for if you're staying in Next.
Publish iterations to the same address so the link you shared keeps showing the current design.
Password-protect client work until the reveal, then lift the password in a click.

Questions

Can I publish a v0 preview directly?: No — you need the built files. Copy the component into a small project, build it, and publish the output folder.
Do I need Vercel?: No. Once it's built to static files it can be hosted anywhere, including here.
Will shadcn/ui components work?: Yes. They compile to ordinary HTML, CSS and JavaScript, which is all that gets served.
What about server actions?: Those need a server. Static hosting serves files only, so a generation relying on server actions won't work unaltered.
Can I use my own domain?: Sites are served on a subdomain of the hosting domain. That address is short, permanent and yours to choose.

Try it with what v0 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.