Does Lovable host my app?

Yes. Clicking Publish puts the app live on a lovable.app address with HTTPS, free on all plans. Custom domains need a paid plan. Lovable's docs say the plan does not cap visitors or bandwidth, except that newer apps on the Free plan are limited to 1,000 server requests per project per 10 seconds.

How do I deploy a Lovable app to Netlify or Vercel?

Connect the project to GitHub with Lovable's Git sync, then import the repository on Netlify or Vercel. Lovable's docs give the build command npm run build with Node.js 22, and an output directory of dist on Netlify and Cloudflare Pages. Add the environment variables from the project's .env file and add the new address to your sign-in provider's redirect URLs.

How do I download my Lovable project's code?

Two ways. Git sync, on all plans, keeps a GitHub, GitLab or Bitbucket repository in two-way sync. Download codebase, on paid plans, gives a one-time .zip from the code editor or Project settings, Git. Neither includes your database records or stored files.

Can I host a Lovable app on a static host?

Only an older React + Vite app, which builds to a dist folder of static files. Apps created from 13 May 2026 use TanStack Start, which runs server code, so a host that only serves files cannot run them. Check package.json: a TanStack Start project lists @tanstack/react-start.

Can I host a Lovable app on Snapy?

An older React + Vite app, yes: build it, zip the contents of dist and upload the zip with a free account and a confirmed email, up to 400 files and 150MB unzipped. Snapy has no fallback to index.html, so a deep link such as /dashboard returns a 404 when opened directly. A TanStack Start app cannot run on Snapy.

Lovable hosting

Lovable hosting: where to put your Lovable app

For most Lovable apps the best host is Lovable itself: publishing to a lovable.app address is free on every plan. Host elsewhere when you need your own pipeline or infrastructure. Apps created from 13 May 2026 run server code and need a server host such as Vercel, Netlify or Cloudflare; older React + Vite apps build to static files that any static host can serve, Snapy included.

Drop a file, get a link →

The short answer

Keep the app on Lovable unless you have a reason to move it. Lovable's hosting page (read 7 October 2026) says publishing to a lovable.app URL is free on all plans, HTTPS is automatic, and your plan does not cap visitors or bandwidth. The one limit it names: on the Free plan, apps created from 13 May 2026 get 1,000 server requests per project per 10 seconds. Custom domains need a paid plan.

Move the app when you need something Lovable's setup does not cover, such as your own deployment pipeline, a rule about where the app must run, or a hosting policy at work.

Step 1: find out which kind of Lovable app you have

Lovable builds on two stacks, and they need different hosts. From Lovable's guide to hosting outside Lovable:

Project	What you deploy	What the host needs
TanStack Start, created from 13 May 2026	Server output plus static assets	A host that runs server code: server rendering, server functions, API routes
Older React + Vite	The static `dist/` folder	Any static host, with a fallback to `index.html` for app routes

To check, open package.json in the Code tab. A TanStack Start project lists @tanstack/react-start in its dependencies. Or ask Lovable in the project chat.

Step 2: get the code out

Git sync, on all plans: connect the project to GitHub, GitLab or Bitbucket and Lovable keeps both sides in sync. Use this if the app will keep deploying from the repository.
Download codebase, on paid plans: a one-time .zip from the code editor (bottom of the file panel) or from Project settings, Git.

Neither copy includes the records in your database or the files in storage. If the app uses Lovable's built-in backend (Cloud), the frontend can stay pointed at it from a new host, or the data moves separately.

Step 3: pick a host

Netlify, Vercel or Cloudflare Pages (either stack). Lovable's docs say these platforms detect a TanStack Start build automatically. Connect the repository, use the build command npm run build with Node.js 22, set the output directory to dist on Netlify and Cloudflare Pages (Vercel needs none), and add the environment variables from the project's .env file, such as VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY. Then add the new address to your sign-in provider's allowed redirect URLs, or logins break. For an older React + Vite app, also add a rewrite so every route serves /index.html.

Your own server or a container (either stack). Lovable documents building a TanStack Start app with the Node.js server preset and running node .output/server/index.mjs, and copying an older app's dist/ folder to Nginx with a fallback to index.html.

A static host such as Snapy (older React + Vite only). No repository and no build server: you build on your own machine and upload the result.

Clone or download the project and run npm ci, then npm run build.
Zip the contents of dist, so index.html sits at the top of the zip.
Drop the zip on free HTML hosting, pick a name such as my-app for my-app.snapy.page, and type the code Snapy emails you. Hosting a page needs a free account with a confirmed email.
Add https://my-app.snapy.page to your sign-in provider's redirect URLs if the app has logins.

What Snapy can and cannot do with a Lovable app

It serves static files only. A TanStack Start app, or anything that needs server functions, cannot run on Snapy.
No fallback to index.html. Opening the home page and clicking through works. But someone who opens a deep link such as /dashboard directly, or refreshes on it, gets a 404, because no dashboard/index.html file exists. Switch the app to hash routing if deep links matter, or use a host with a rewrite rule.
Limits: a zip of up to 400 files and 150MB unzipped, 20 live links at a time on the free plan, and every hosted page sent with noindex until you turn on "findable in search" for that link. A custom domain is part of Snapy Pro.
What it adds: every open counted with the country and referrer, an email on the first open, and a password or expiry date on the link, all free.

Who should just use Lovable's own hosting

Your app was created from 13 May 2026 (TanStack Start) and you have no server of your own.
You are still building: Lovable's preview and publish flow is built around that.
The app uses the built-in backend, AI features or connectors, and you do not want to manage environment variables and redirect URLs yourself.
You want a custom domain with no extra setup and are on a paid Lovable plan anyway.

Snapy makes sense for a small, older Lovable front end you want to hand someone as a link, password-protected or set to expire, and see when it was opened. For other AI-built pages see publishing an AI-made page.