> ## Documentation Index
> Fetch the complete documentation index at: https://fabricate.build/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Exporting Your Code

> Push your project to a new GitHub repository or download it as a zip — you always own your code.

Your Fabricate project is a real, full-stack codebase, and you can take it with you at any time. Export your code by pushing it to a brand-new GitHub repository or downloading the whole project as a zip file.

<Note>
  You always own your code. Fabricate generates a standard React 18, TypeScript, and Cloudflare Workers project — there's no proprietary format and no lock-in.
</Note>

## Push to a New GitHub Repository

Send your project's code to a fresh GitHub repository. This is a clean, one-time copy of your codebase into a new repo you own.

Use this when you want your code on GitHub but don't need an ongoing connection. If you'd rather keep Fabricate and GitHub in step as you continue building, set up [GitHub Sync](/build/github-sync) instead — it provides continuous two-way sync.

## Download as a Zip

Download the entire project as a zip file. You get the full codebase — frontend, backend, and configuration — ready to open in your own editor, run locally, or move wherever you like.

<Tip>
  A zip download is the quickest way to grab a complete snapshot of your app exactly as it stands right now.
</Tip>

## Export vs. GitHub Sync

Both options give you your code. The difference is whether the connection continues.

|                      | Export                            | GitHub Sync                           |
| -------------------- | --------------------------------- | ------------------------------------- |
| **What you get**     | A one-time copy (new repo or zip) | A continuously synced repository      |
| **Direction**        | One-way                           | Two-way                               |
| **Stays up to date** | No                                | Yes                                   |
| **Best for**         | A snapshot of your code           | Ongoing development across both tools |

## You Own Your Code

Exporting isn't a special escape hatch — it's a core part of how Fabricate works:

* **Standard stack** — React 18 + TypeScript + Vite on the frontend, Cloudflare Workers and D1 on the backend, styled with Tailwind and shadcn/ui.
* **No lock-in** — the exported project is plain code you can read, run, and modify anywhere.
* **Yours to keep** — whether you export once or never, the code belongs to you.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Does exporting stop me from building in Fabricate?">
    No. You can keep prompting and building in Fabricate after an export. Exporting just produces a copy of your code.
  </Accordion>

  <Accordion title="Should I export or use GitHub Sync?">
    Export when you want a one-time copy. Use [GitHub Sync](/build/github-sync) when you want Fabricate and a GitHub repository to stay aligned as you continue working.
  </Accordion>

  <Accordion title="Can I run the exported app on my own?">
    Yes. The project is a standard full-stack app built for Cloudflare's platform, so you can run and deploy it yourself.
  </Accordion>
</AccordionGroup>

## Where to Go Next

<CardGroup cols={2}>
  <Card title="GitHub Sync" icon="github" href="/build/github-sync">
    Keep Fabricate and GitHub in two-way sync.
  </Card>

  <Card title="File Explorer" icon="folder" href="/build/file-explorer">
    Browse the code before you export it.
  </Card>
</CardGroup>