# How to host a website made with v0

By Avatar 8 (Avatar 8 LLC) · Published November 20, 2026 · https://deed.page/blog/host-a-website-made-with-v0

To host a website made with v0 means putting the Next.js app v0 generated on a server so anyone can open it at a normal HTTPS address. v0's Publish button does that on Vercel; to host it elsewhere you turn the project into a static export and upload the `out` folder, and deed.page's Free plan holds 25 sites of up to 25 MB each with no account ([pricing](https://deed.page/pricing)).

This guide covers when v0's own publishing is enough, which v0 projects a static host can serve, and how to publish one with `curl` or through MCP. Every deed.page command here was run against production on November 20, 2026, and the test sites were then deleted.

## How do I host a website made with v0?

The short answer: click Publish in v0, or export the code, set `output: 'export'` in `next.config`, run `next build`, and upload the `out/` folder to a static host.

v0's docs, checked November 20, 2026, say Publish deploys to a Vercel project with a stable `vercel.app` production URL, and that you can pick a custom domain in the same flow ([v0: Deployments](https://v0.app/docs/deployments)). If that is all you need, stay there. The [v0 FAQ](https://v0.app/docs/faqs) also says Git is optional and that you "can still export code and deploy elsewhere". Host it yourself when you want a different address, no Vercel project, or an agent that keeps updating the page.

## Check whether your v0 project can be static

v0 builds with Next.js, React, TypeScript, Tailwind CSS, and shadcn/ui ([v0 FAQ](https://v0.app/docs/faqs)). A Next.js app can become plain HTML, CSS, and JavaScript, but only the parts that do not need a running server. The [Next.js static exports guide](https://nextjs.org/docs/app/guides/static-exports) (checked November 20, 2026) lists what does not work in an export, including route handlers that read cookies, rewrites, redirects, Incremental Static Regeneration, and image optimization with the default loader.

- **Landing pages, portfolios, docs, and dashboards with client-side data** usually export cleanly. deed.page fits here.
- **Apps with API routes, server actions, auth, or a database call on the server** need a host that runs Next.js. Keep v0's Vercel publishing, or use a host with a Next.js runtime; Netlify, for example, has a [guide for v0 apps](https://www.netlify.com/knowledge-base/deploy-your-v0-app-to-netlify/).

## Build it and publish it with one curl

Get the code onto your machine through v0's GitHub connection or its code export. Then set this in `next.config.mjs`:

```js
const nextConfig = { output: 'export', trailingSlash: true, images: { unoptimized: true } }
export default nextConfig
```

`images: { unoptimized: true }` lets `next/image` work without a server. `trailingSlash: true` writes each page as `about/index.html`. We tested both settings: without it, Next.js wrote `about.html` next to an `about/` folder of data files, and `/about/` showed that folder's file list instead of the page. With it, `/about` redirected to `/about/` and served the page.

```bash
npm ci && npx next build
tar -C out -czf site.tar.gz . && curl -T site.tar.gz "https://deed.page/v1/sites?slug=bakery-v0-export-m3x8&ref=blog"
```

Our test was a three-page app built with Next.js 16. The `out` folder had 33 files, and the tarball was 182 KB. The reply had `"url": "https://bakery-v0-export-m3x8.deed.page/"`, `"version": "v1"`, `"files": 33`, and a `deed_tok_…` owner token shown once. Keep that token; it is the only credential. Pick your own suffix, since that slug is only an example. A stranger sending the same request got `409 slug_taken` with the suggestion `bakery-v0-export-m3x8-2` ([choosing a slug](https://deed.page/blog/choosing-a-slug)). The `/_next/static/` chunks served as `text/javascript`, so client navigation between pages worked.

To ship a new build, send it with the token:

```bash
curl -T site.tar.gz -H "Authorization: Bearer $DEEDPAGE_TOKEN" \
  "https://deed.page/v1/sites?slug=bakery-v0-export-m3x8&ref=blog"
```

That returned `"version": "v2"` at the same URL. Sending an identical tarball returned `"unchanged": true` and no new version. Bigger builds go up in parts ([large sites](https://deed.page/blog/plan-upload-large-sites)).

## Publish through MCP instead

If an agent such as Claude or Cursor holds the built files, it can publish through deed.page's MCP server at `https://deed.page/mcp` ([docs](https://deed.page/docs)). The call looks like this:

```json
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_site","arguments":{"slug":"bakery-v0-mcp-t6p3","files":{"index.html":"<!doctype html><title>Sourdough bakery</title><h1>Sourdough bakery, built in v0</h1><a href=\"/about/\">About</a>","about/index.html":"<!doctype html><title>About</title><h1>About the bakery</h1>"}}}}
```

It returned `ok: true`, `version: "v1"`, the subdomain URL, and a token, and both `/` and `/about/` served their pages. `update_site` with that token and `merge: true` replaced the home page and kept `/about/`; without the token it refused with `unauthorized`. The [MCP walkthrough](https://deed.page/blog/mcp-publish-walkthrough) covers the rest.

## FAQ

**Can I host a v0 site for free outside Vercel?**
Yes, if the project works as a Next.js static export. deed.page's Free plan is $0 for 25 sites of 25 MB each. Server features such as API routes and server actions need a host that runs Next.js.

**Do I have to remove the Vercel parts of my v0 app?**
Only the parts that need a server. A static export has no API routes or image optimizer, so set `images: { unoptimized: true }` and move any server calls to an external API the browser can reach.

**Will the site disappear if nobody visits it?**
No. deed.page sites do not expire unless you send `X-Ttl` for a throwaway page ([TTLs](https://deed.page/blog/ttl-for-throwaway-pages)). Free sites show a small "Published with deed.page" link; Hobby at $3 a month removes it.
