How do I export or download my v0 project code?

01Option 1: Download the project as a ZIP

The simplest route is downloading the whole project. In early 2026, when users asked in Vercel's community forum where the old "add to codebase" command had gone, Vercel staff pointed them to the Download ZIP option in the new interface.

1. 1Open the project in v0Use the menu on the project or chat to find the download option.
2. 2Download the ZIPIt contains the full Next.js project: pages, components and configuration.
3. 3Unzip and installOpen the folder in a terminal and install dependencies with your package manager (npm install, for example).
4. 4Run it locallyStart the development server and open it in your browser to check everything renders.

02Option 2: Sync to GitHub

Connecting GitHub keeps your code in a repository that you own, and it means later changes in v0 can flow into the repo instead of requiring a fresh download each time. v0's pricing page lists GitHub sync on the free plan as well as paid plans.

GitHub is the better choice if you plan to keep iterating in v0 while also editing code elsewhere, or if anyone else will work on the project. It also makes deploying to Vercel, Netlify or another host a matter of connecting the repository.

03What about the shadcn CLI command?

v0 used to offer a command that added generated components straight into an existing codebase through the shadcn CLI. In January and February 2026, users in Vercel's community forum reported that the link no longer appeared in the new interface, and staff suggested downloading the ZIP instead. If you want to move individual components into a project you already have, copying the component files from the download works.

04Problems people hit after exporting

Exported projects usually run, but a few issues come up often enough to plan for.

• Missing environment variables: API keys and database URLs set in v0 or Vercel are not in the ZIP. Add them to a local .env file and to your host.
• Missing UI components: generated code can reference shadcn/ui components that were not included; install them with the shadcn CLI.
• Version mismatches: run the dependency install fresh rather than reusing an old lockfile from another project.
• Images and assets: check that files referenced by URL still load outside v0's preview.

05Where to host the exported code

Because v0 produces Next.js, Vercel is the path of least resistance, but any host that supports Next.js works. Vercel vs Netlify and Cloudflare Pages vs Vercel compare the main options, and both Vercel and Netlify have free tiers for small sites.

Owning the code is the main reason to export. Do I own a website made with AI? covers the ownership question for AI-built sites generally.

06Moving v0 components into an existing project

If you already have a Next.js app and only want a few screens from v0, you do not need the whole exported project. Copy the component files you want into your components folder, then check three things: that the shadcn/ui components they import exist in your project (install any missing ones with the shadcn CLI), that your Tailwind configuration includes the same theme values, and that any icons or utilities they use are installed.

Expect some adjustment. Generated components often assume their own layout wrapper and global styles, so spacing and colors can shift once they sit inside your app's design system. Treat them as a strong first draft and align them with your existing conventions rather than adapting your app to them.

• Copy only the components you need, not the whole app shell.
• Install missing shadcn/ui components with the CLI.
• Match Tailwind theme values so colors and spacing line up.
• Rename and restructure to fit your project's conventions.