Lovable turns a plain-language prompt into a working web app in minutes. The build part feels effortless. Then you try to get that app onto a real URL, and most guides assume you will connect a GitHub repository to Vercel or Netlify and wire up automatic deploys.
That works, but it brings back the exact complexity you picked Lovable to avoid. And Lovable’s own hosting sits on its paid plans (around $20 to $25 per month), with your live URL tied to that subscription, which is why so many builders look to host their app somewhere cheaper and fully under their control. This guide shows the no-Git path: export your project, run one build command, and host the result anywhere with drag-and-drop. You get a live URL, a custom domain, SSL, and a QR code, without a repository, a CI pipeline, or a hosting bill tied to the tool that built the site.
If you built your project with a different tool, our companion guide on deploying a Bolt.new site covers the same workflow for Bolt, and our guide on creating a landing page with AI and Astro templates walks through a template-first approach. For a comparison of all six AI code generators and their export workflows, see our complete AI deployment guide.
Why host a Lovable site outside Lovable?
Using Bolt.new instead of Lovable? See our Bolt.new deployment guide. The workflow is different because Bolt outputs plain HTML while Lovable outputs a React + Vite project that needs a build step.
Lovable can publish your app for you, but custom domains and ongoing hosting sit on its paid plans (around $20 to $25 per month), and your live URL stays tied to that subscription. The day the plan lapses, the site can go with it. Hosting the static build elsewhere changes that:
- Lower, predictable cost. A dedicated static host like Supadrop runs $5/mo flat, separate from whatever you pay Lovable to keep building.
- You own the deployment. Your site lives independently of your Lovable plan, so building in Lovable and hosting the result are no longer the same bill.
- Custom domain and SSL on your terms. Point your own domain at the host and keep full control of it.
The tradeoff is a single build step, covered below. For a frontend-only Lovable app, that is the entire job.
What Lovable actually exports
Every Lovable project is a standard Vite + React + TypeScript application styled with Tailwind CSS. This matters for hosting: it means there is always source code that needs compiling. There is no “vanilla HTML” mode the way some AI builders offer, so the build step is not optional.
You can get your code out two ways:
- Download a ZIP. From your project settings, export the full project as a
.ziparchive. No GitHub account required. This is the quickest route to a one-time deploy. - GitHub sync. Connect a repository and Lovable pushes every change automatically. This is the path Vercel and Netlify integrations rely on, and continuous sync is a paid feature.
Inside the export you get your React components, routing, Tailwind config, and folder structure: clean, readable, industry-standard code.
What is NOT in the export: anything that runs on Lovable’s managed backend. Authentication, a hosted database, Stripe payments, and AI orchestration built through Lovable Cloud or Supabase do not export as standalone code. The frontend that talks to those services exports fine, but the services themselves stay on Lovable’s infrastructure.
Is your Lovable app static?
Static hosting serves files (HTML, CSS, JavaScript, images). It does not run server-side code or hold a database connection. After you build a Lovable project, the output is static files, so the frontend will host anywhere. The real question is whether your app needs a backend to function.
Your Lovable app is a good fit for static hosting if:
- It is a landing page, portfolio, marketing site, event page, or brochure site
- It displays content but does not save anything from visitors
- It has no login, no user accounts, and no database reads or writes
- Any forms post to an external service (Formspree, Getform) rather than a Lovable backend
Your Lovable app needs more than static hosting if:
- It uses Lovable Cloud or Supabase for authentication or a database
- It processes payments through Stripe
- It stores or retrieves user-generated data
- It relies on server-side AI calls orchestrated by Lovable
If your app falls in the second group, you have two clean options. Keep the managed backend running and host the static frontend pointed at it, or move the whole app to a full-stack platform. Our guides on Vercel alternatives and Netlify alternatives cover platforms that run server-side code. For the underlying distinction, see our explainer on static vs dynamic websites.
Two ways to get your code out
Both export paths end at the same place: a folder of source code on your computer or in a repository. Here is how to choose.
| Method | Best for | Needs GitHub | Auto-redeploy |
|---|---|---|---|
| ZIP download | A fast, one-time deploy | No | No |
| GitHub sync | Ongoing edits with auto-deploys | Yes | Yes (via Vercel/Netlify) |
For the no-Git workflow in this guide, choose the ZIP download. Open your project settings in Lovable, export the project, and unzip it on your computer. You now have the project folder ready to build.
Build your Lovable project
This is the one step Lovable apps cannot skip. The export is source code, not the finished website. Compiling it into static files takes a single command.
- Open a terminal in your unzipped project folder
- Run:
npm install && npm run build- Vite produces a
dist/folder containing the finished static site: HTML, CSS, JavaScript, and assets - Compress that
dist/folder into a single.zip(right-click it and choose Compress, or runzip -r dist.zip dist). The ZIP is what you upload
If npm install fails, make sure you have Node.js installed (the LTS version works best). The build typically finishes in well under a minute.
Deploy your Lovable site on Supadrop
With your zipped dist/ folder ready, the deploy itself is drag-and-drop.
- Go to Supadrop and open the upload zone
- Drag your
dist.ziponto it - Supadrop unpacks the ZIP, detects
index.html, provisions SSL, and publishes your site - Your app is live at
yourproject.supadrop.sitein under 30 seconds
No server to manage, no terminal commands on the host, no configuration files. You also get a QR code generated automatically for the site, which is handy if you are putting the link on a card, a slide, or a flyer.
Handle client-side routing
Lovable apps are single-page apps, which means navigation happens in the browser with React Router rather than by loading new HTML files from the server. On static hosting this creates one predictable gotcha: if a visitor refreshes a sub-page like /pricing or opens that link directly, the host looks for a /pricing file that does not exist and may return a 404.
The fix is a “SPA fallback,” where the host serves index.html for any unknown path and lets React Router take over. If your host does this automatically, multi-page navigation just works. If you are not sure, you have two safe options:
- Keep it on a single page. For most landing pages and portfolios, one page with anchor links (
#features,#pricing) avoids the issue entirely. - Use hash-based routing. Ask Lovable to switch to hash routing, which puts the route after a
#(for example/#/pricing). Hash routes never hit the server, so refreshes and deep links always resolve.
Where to host a Lovable React app
Supadrop is not the only way to host a Lovable build. Since Lovable outputs a Vite + React project, any platform that serves static files works. Here is how the main options compare.
Vercel and Netlify integrate directly with Lovable through GitHub. Connect the repository once and every change you make in Lovable redeploys automatically. This is the best choice if you edit the site often and do not mind the GitHub connection. Both auto-run the build, so you skip the local build command.
Cloudflare Pages offers a generous free tier and unlimited bandwidth but requires a Git-based workflow. If you are already comfortable with Git, it is excellent. If you chose Lovable to avoid that, it adds the complexity back.
Supadrop trades automatic builds for a no-Git, no-pipeline path: you run one build command locally, then zip the dist/ folder and drag it. For a site you ship and share rather than edit daily, that is the shortest route. For a wider comparison, our free static website hosting guide covers seven platforms in detail.
Add a custom domain to your Lovable site
Once your site is live on a default subdomain (yourproject.supadrop.site), connecting your own domain makes it look professional.
The short version: point a CNAME or A record from your domain registrar to your host, wait for DNS propagation (usually under 10 minutes), and SSL provisions automatically. On Supadrop, custom domains are available on paid plans. The setup is the same regardless of which AI tool built the site.
Troubleshooting Lovable deployment errors
Blank page after upload. You uploaded the source code instead of the build output. Run npm install && npm run build, then zip and upload the dist/ folder, not the project root.
Sub-pages 404 on refresh. Your single-page app needs a SPA fallback so the host serves index.html for unknown paths. Keep the app on one page or switch Lovable to hash-based routing, as covered above.
Login, database, or payments do not work. These features run on Lovable Cloud or Supabase, not in the static build. Static hosting cannot run them. Keep those managed services live and configured, or move the app to a full-stack platform.
Missing styles or broken images. The build references absolute paths that do not match your host. Confirm you zipped the entire dist/ folder, including its assets/ subfolder, so the hashed CSS and image files resolve.
Environment variables are undefined. Lovable injects environment values at build time. Recreate any required variables locally before running npm run build, because the build bakes them into the output. Never put secret backend keys in a frontend build; only public, client-safe values belong there.
“npm install” fails. Make sure Node.js LTS is installed. If the error names a package, delete node_modules and package-lock.json, then run npm install again.
Frequently asked questions
Does a Lovable site work on static hosting if it uses Lovable Cloud or Supabase?
Partly. The frontend (your React pages and components) builds into static files and hosts anywhere, including Supadrop. But features that depend on Lovable Cloud or Supabase, such as authentication, a database, Stripe payments, or AI orchestration, run on managed backend services. Those do not export as standalone code.
If you host only the static build, the interface loads but any feature that calls the backend stops working unless those managed services stay live and the keys are configured. For a purely frontend Lovable app (a landing page, portfolio, or marketing site), static hosting works perfectly after one build step. Our explainer on static vs dynamic websites covers why.
Do I need a paid Lovable plan to export my project?
You can download a ZIP of your project from project settings without a paid plan, which is enough to build and host the static output yourself. The continuous GitHub sync, which pushes every change to a repository automatically, is a paid feature. For a one-time deploy with drag-and-drop, the ZIP download is all you need.
Why does my Lovable site show a blank page or a 404 after deploying?
Two common causes. First, you uploaded the source code instead of the build output. Lovable projects are Vite and React, so you must run a build, then zip and upload the resulting dist folder, not the project root.
Second, single-page apps use client-side routing, so refreshing a sub-page or opening a deep link returns a 404 unless the host serves index.html for unknown paths. If your host does not do this automatically, keep the app on a single page or switch Lovable to hash-based routing.
Can I deploy a Lovable site without connecting GitHub?
Yes. Download your project as a ZIP from Lovable, run npm install && npm run build on your computer, then zip the dist folder and drag that ZIP onto Supadrop. No GitHub account, no repository, no CI pipeline. The GitHub route is convenient if you want automatic redeploys, but it is optional.
Can I use a custom domain with a deployed Lovable site?
Yes. After your site is live on a default subdomain, point a CNAME or A record from your domain registrar to your host and SSL provisions automatically. On Supadrop, custom domains are available on paid plans. DNS propagation usually completes in under 10 minutes.
Can I update my Lovable site after deploying it?
Yes. Make your changes in Lovable, export and build again, then zip and re-upload the new dist folder. On Supadrop the updated site replaces the previous version immediately, in the same 30 seconds the first deploy took.