How to host a v0 export

v0 is Vercel's design-and-code generator. You describe an interface, v0 produces React and Tailwind code, and you refine it in the chat. The default next step is to deploy on Vercel, which makes sense if you already live in Vercel-land. If you just want to show someone what v0 built, or put it on your own domain, hosting the export yourself is lighter than a full deploy.

What you export depends on what you built. For a single self-contained component, copy the HTML that v0 produces and you host an HTML file by pasting it straight in, which gives you a URL in seconds. This is the same paste flow that works for any AI output, so a v0 component and a Claude artifact host identically. It is the fastest route for a static demo of one piece of UI.

For a multi-file app, export the project and you publish a v0.dev component by uploading the ZIP. NudgeHost unpacks it and serves the index as the entry point, with unknown paths rewritten back to it so client-side routing works. Under the hood this is the same pipeline you hit when you host a React app directly, because a v0 app is a React build once it leaves the chat. If the export is source rather than a build, run an install and a build locally first, then zip the output folder.

Whichever path you take, the output is static, a folder of files served as they are with the JavaScript running in the browser. See static site hosting for why that hosts without a server. v0 exports often pull Tailwind from a CDN and inline their shadcn components, and both work from the hosted page exactly as they did in the preview, so the design survives the move intact.

One practical detail trips people up. v0 sometimes splits output across several files, a page file and a folder of components, and pasting only the preview HTML loses the structure. If you want the full app rather than a static snapshot, take the project export and host the ZIP. If a static snapshot of the UI is all you need, the pasted HTML is enough and quicker. Pick based on whether the thing needs to actually run or just be seen.

A v0 build is often the centrepiece of a pitch, an internal demo, or a design review. You can share a presentation with a client and hand over the live link as the working demo rather than a screenshot in slides. A stakeholder clicking a real interface understands it faster than any description, and the link works on their phone as well as their laptop.

Re-export from v0 whenever the design changes, upload to the same link, and the URL stays the same so nobody needs a new one. Hosting is free to start, and most v0 exports are small enough to sit well under the free-plan limit. the pricing page adds custom domains and password protection for when the link goes to a client. The deploy step you were about to set up turns out to be a drag-and-drop.