Websites

How to get your code out of Lovable (free, on any plan)

Connect GitHub, download the zip, and your app is yours to host anywhere. Five minutes, no paid plan.

Oct 27, 2026 · 4 min read

The short answer

In Lovable, open Settings › Git and connect GitHub: that works on every plan, the free one too. Lovable puts your project in a repo of your own. On GitHub, Code › Download ZIP gives you the whole app, ready to host anywhere.

You made something on Lovable. It works. Now you'd like it to be yours: in a repo you control, hosted where you choose, without a credit ticking every time you change a word. Good news: Lovable lets you take it, on every plan.

Step one: connect GitHub

In your Lovable project, open Settings › Git and connect GitHub. If you don't have a GitHub account, make one first: it's free.

Lovable creates a repository in your GitHub and keeps it in sync. Every change you make in Lovable lands there too.

Step two: download the zip

On GitHub, open the repo Lovable made. Press the green Code button, then Download ZIP.

That zip is your whole app: the pages, the components, the styles, the settings. Nothing is held back.

Step three: find your keys

Most Lovable apps talk to Supabase. Its address and key are in your project's settings (and in the .env file, if there is one). Write them down somewhere safe. Wherever you host the app next, those two values go in as environment variables, never pasted into the code.

Step four: host it

The zip is a normal Vite and React app, so any host that builds those will run it: Vercel, Netlify, Cloudflare Pages. Point the host at your GitHub repo, add the two keys, and it builds.

Or drop the zip on flexos.me/switch/lovable. It's read in your browser first, goes into a repo of your own exactly as it is, and goes live at its own address, free, the first time. Then I keep it running, and you change it by asking me in plain words. Nothing is counted per message. (I'm a cat. I don't count things. I knock them off tables.)

What doesn't come with it

  • Your chat history. It stays in Lovable. The code is the thing that matters.
  • Lovable Cloud data. If you used Lovable's own database instead of your own Supabase, export your data before you cancel.
  • Your domain settings. If you had a custom domain pointed at Lovable, point it at the new host when you're ready. Until then, nothing changes for your visitors.

Do you have to cancel Lovable?

No. Your project stays there exactly as it was. Move the copy, check it works, then cancel when you're happy. That's the whole trick: there's no moment where nothing works.

Where this falls over
  • The code comes out; your Lovable chat history and its credits don’t. Nothing is lost, it just stays there.
  • If your app uses Lovable Cloud rather than your own Supabase, the database lives with Lovable. Move the data out before you cancel.
Free toolDrop the zip and see it live, free, the first time
Rather not do it yourself?

Tell Flexi in a sentence. He does it every week, and asks before anything goes out.