Their preview, their canvas
v0 shows you the app while you build it, in its own way. Here you describe a change and read what came back, then open the preview. If the live canvas is the part you like, you will miss it.
Bring your v0 project
v0 pushes to a branch. Bring the repository.
v0’s documentation describes connecting a chat to a GitHub repository: it starts from the base branch you choose and pushes its code changes to a working branch. That repository is the project. Paste its link here and it is cloned with every commit and every branch.
New project → “I already have one” → paste the link. Nothing in ${name} is changed.
Build a moving-quote calculator — bedrooms, miles, and a packing add-on.
calculator · live pricelive in 1 min · $0.18
In short
Connect the v0 chat to GitHub if it is not already (it is listed on the free plan), copy the repository link, and paste it into New project → I already have one. It comes across with full history. Vercel hosting stays where it is; the code is yours.
What changes, what does not
| Question | v0 | Here |
|---|---|---|
| Where the code lives | A GitHub repository; changes pushed to a working branch | A git repository here, cloned with its full history |
| Know the cost before you run it | Credits, with per-model token prices published | Yes — the rate under the composer, the cost printed on the answer |
| Choose the model | v0’s own models | 300+, each with its published price |
| Where it is hosted | Deploys to Vercel | Published and hosted here, on your own domain when you connect one |
| Run it yourself for $0 | Not published | Yes, on your own computer with your own model keys |
v0’s GitHub integration — base branch, working branch, pushes and pull changes — is as described in v0’s own documentation, and “Sync with GitHub” and per-model token prices are as listed on v0.app/pricing, both read on 17 September 2026. “Not published” means their page does not answer the question.
Step by step
Out of v0, into a repository you own.
- In v0: connect the chat to GitHubv0’s documentation describes selecting a base branch and a working branch that v0 pushes its changes to. Merge the working branch if you want the latest work on the base branch.
- Copy the repository linkFrom the repository on GitHub. The link a browser shows is fine.
- Here: New project → “I already have one”Paste the repository link. If it is private, connect GitHub and pick it from the list instead. GitLab and Bitbucket links work the same way.
- It is cloned with its full historyEvery commit comes across, into a repository that is yours here. It opens as a normal project from that point on — nothing about it is specific to us.
- Ask for the next change“Add a pricing page.” “Make the sign-up form send me an email.” The rate is under the composer before you send; what it cost is printed on the answer. Keys the app needs go in the project’s secrets.
The honest half
What v0 does that this does not.
Their hosting and services
Anything that ran on v0’s own hosting, database or auth does not come with the code. The repository is yours; those services were theirs. You will be asked before anything is rebuilt.
A price you can read
What you get in exchange: the model’s rate before you send, the cost printed on the answer, 300+ models each with its published price, and no credit with an unpublished exchange rate.
Related
Paste the link. Keep the history.
Free to start with no card. The repository comes across with every commit, and you ask for the next change from there.
Questions
Asked, answered
How do I get my code out of v0?
v0's documentation, read on 17 September 2026, describes connecting a chat to a GitHub repository and pushing code changes to a working branch; GitHub sync is listed on the free plan. Copy the repository's link and paste it here under New project → I already have one.
Which branch is imported?
The whole repository, every branch and every commit. If v0's latest work is on a working branch, merge it first or ask for that branch after the import.
What about the Vercel deployment?
It stays where it is. Nothing on Vercel or GitHub is changed by importing the repository. The app is published and hosted here when you ask, on your own domain when you connect one.
Do I lose anything?
Anything that ran as a Vercel-side service rather than as code in the repository is not in the clone. You are asked before anything is rebuilt here.