Lovable is a great place to build. It’s an expensive place to just host.
Lovable’s plans are priced around building: credits, chat, an AI that writes your code. Once the site is done, you’re still paying builder prices for what is, underneath, a folder of files. These are the six things people run into.
Your domain costs a builder plan
On Lovable’s free plan the site lives on a lovable.app address. Connecting a domain you own needs a paid plan, starting with Pro at $25 a month.
“Edit with Lovable” on every page
Free-plan apps carry Lovable’s badge. Hiding it is a paid-plan setting — and if you downgrade later, it comes back the next time you publish.
The lovable.app address never goes away
Even with a custom domain, the lovable.app URL can’t be removed, and other connected domains reach your primary one through temporary 302 redirects rather than permanent 301s.
“Export” means GitHub and a build step
Lovable hands you a React + Vite project, not a website. Uploading the repo as-is gives a blank page, because the browser can’t run src/main.tsx.
Hosting is bundled with credits you stopped using
Finished sites don’t need 100 AI credits a month. Paying for them anyway is what keeps many people on Pro long after the building is done.
An app, but no place to publish content
A Lovable site is one app rendered in the browser. Adding a blog means prompting for one, then maintaining it, and client-rendered posts are harder for crawlers to read.
/blog/ that serves plain HTML. How it worksLovable behaviour as described in Lovable’s own documentation: Set up a custom domain and the Lovable FAQ; plan prices from lovable.dev/pricing (checked September 2026). Check Lovable’s pages for current terms.
The same build, three ways to put it online
What Lovable’s own publishing gives on its free and Pro plans, and what the built folder does on Fylo. The last two rows are there because they’re true.
| What you need | Fylo.Host | Lovable Free | Lovable Pro |
|---|---|---|---|
| Price with your own domain | $6.99/mo, ~$4.66 yearly | ✗ | $25/mo |
| Free public URLNo card needed | yours.fylo.dev | yours.lovable.app | yours.lovable.app |
| No “Edit with Lovable” badge | ✓Fylo badge on free only | ✗ | ✓ |
| Served from the edge, 330+ cities~100 ms TTFB on hosted sites | ✓ | Not published | Not published |
| One-click WebP, lazy loading, font subsetting | ✓ | Build it by prompt | Build it by prompt |
| Built-in blog with editor and RSS10 posts on Fylo’s free plan | ✓ | Build it by prompt | Build it by prompt |
| Form submissions to your inboxSpam filtering included | Pro and Business | Build it by prompt | Build it by prompt |
| Humans-only visitor countsBots and crawlers left out | ✓ | Not compared | Not compared |
| Hosts builds from any toolBolt, v0, Cursor, by hand | ✓ | Lovable projects | Lovable projects |
| Publish straight from the editor | Build, then upload | ✓ | ✓ |
| Database, sign-in, edge functionsLovable Cloud or Supabase | Keeps using yours | ✓ | ✓ |
How to host a Lovable app outside Lovable
Three steps, about five minutes the first time. After that, updating is one upload.
Get the code from GitHub
In your Lovable project, connect GitHub so the code syncs to a repository you own. Clone it, or on GitHub press Code → Download ZIP and unzip it.
git clone https://github.com/you/my-app
cd my-app
Build it once
With Node.js installed, run two commands. Vite writes the finished website into a new dist folder. No Node? The agent prompt does this part.
npm run build
// ✓ built in 4.2s → dist/
Drop dist, publish
Drag dist onto the box at the top. The pre-flight check confirms it’s a real build, then it’s live. Sign up free to keep it, then add your domain in the dashboard.
index.html
assets/index-a1b2c3.js
assets/index-d4e5f6.css
src/ node_modules/ .env
More than one page? Send Lovable this first.
Lovable apps change pages inside the browser. On a static host, a direct visit or a refresh on /pricing asks for a file that doesn’t exist. The home page always works; for multi-page apps, one prompt in Lovable makes every page load from any link. Build again after it’s done.
Uses Lovable Cloud or Supabase? The front end still talks to it.
A Lovable app reaches its database from the visitor’s browser, using a public URL and a publishable key that the build already contains. Moving the front end to Fylo leaves the backend exactly where it is.
Two things to do: add your new address to the auth redirect URLs so sign-in comes back to the right place, and never put a service-role or secret key in front-end code.
Relies on server code only Lovable runs? Keep it on Lovable.
Fylo serves static files. It doesn’t run a database, edge functions or server-side rendering, and it doesn’t edit your app by chat. If the app only works through Lovable’s own hosting, stay there — or keep the app on Lovable and put your marketing site and blog on Fylo.
Six things that go wrong moving a Lovable app, and the fix for each
The pre-flight check catches the first two before you publish. The rest take a minute in Lovable or your Supabase settings.
White screen after publishing
The source was uploaded instead of the build. Its index.html loads /src/main.tsx, which only Vite’s dev server can run.
npm run build and upload dist. The check above flags this.“Over your storage limit” on a small site
The whole project folder went up, node_modules included — often hundreds of megabytes. A typical Lovable build is a few MB.
dist. Drop the whole project and we pick dist out for you./pricing works from the menu, not from a link
React Router handles pages in the browser, so there’s no pricing file for the server to send on a direct visit.
Login sends people back to lovable.app
The auth settings only list your old addresses, so after sign-in the provider returns visitors there, or refuses the redirect.
“supabaseUrl is required” or empty lists
The build ran without the VITE_ settings that tell the app where its database is. They come from the project’s .env when you build.
.env is in the folder before npm run build. Publishable keys only.Shared links show a default title and image
Lovable apps set most text in the browser, so link previews and crawlers read what’s in index.html: often a generic title, description and social image.
index.html.Hosting built for sites that started as a prompt
Everything below is on by default or one toggle away in the dashboard. No build settings, no Git hooks, no config file.
dist as a folder or ZIP. Every file keeps its path; no repo connection or build settings./blog/, served as static HTML. 10 posts free. Blog guidepublic/, lazy loading, font subsetting and JS delay are toggles, on every plan.dist; the link you shared shows the new version.Free plan: 1 site and 10 MB, which fits most Lovable builds, with a small “Hosted with Fylo.Host” badge. Custom domains start on Starter and forms on Pro — see pricing. Also see ZIP file hosting and landing page hosting.
Lovable built the app. Let the blog bring the traffic.
A client-rendered app gives search engines little text to read. Blog posts on Fylo are plain HTML pages on the same domain, so every crawler — and every AI search engine — can read them without running JavaScript.
- Turn it on in the dashboard. Blog tab → choose the site → Enable blog. It appears at
/blog/; your Lovable build is left alone. - Write in a real editor. Visual and Code modes, a media library, categories, tags, cover images and private preview links for drafts.
- It looks like your site. Pick the Clean, Magazine or Minimal theme, or let Fylo copy the header and footer from your app.
- SEO plumbing included. Clean URLs, canonical and Open Graph tags, article structured data, an RSS feed and a sitemap.
- 10 published posts on the free plan, unlimited on paid plans. Publishing a post never needs a rebuild of your app. Blog guide
yourdomain.com/ ← your Lovable app
yourdomain.com/blog/ ← post index, plain HTML
yourdomain.com/blog/how-we-built-it/
yourdomain.com/blog/feed.xml ← RSS
yourdomain.com/blog/sitemap.xml
// in the app, link to it like any page
<a href="/blog/">Blog</a> // a normal link, not a router Link
The Lovable projects that end up on a real domain
Build in Lovable. Host where it makes sense.
Netlify, Vercel and Cloudflare Pages can host a Lovable build too; they want a Git connection and build settings. Fylo takes the built folder. See Fylo vs Netlify and Fylo vs Vercel.
Stay on Lovable’s hosting when
- You’re still building every day and want Publish to be one click from the chat.
- You already pay for Pro because you use the credits, so the domain comes along anyway.
- The app depends on something only Lovable’s hosting runs for it.
- You never want to touch GitHub, a terminal or an agent.
Host it on Fylo when
- The site is done or nearly done, and $25 a month for hosting feels like a lot.
- You want your own domain and no builder badge, with prices you can read today.
- You want a blog, working forms and real visitor numbers next to the app.
- You host several client or side projects and don’t want a builder seat for each.
Lovable website hosting questions
npm install and npm run build, and drop the dist folder that appears onto the upload box on this page. The site is on its own URL in seconds. Sign up free to keep it online, then add your own domain from the dashboard.npm install and npm run build, which needs Node.js on your computer. If that sounds like too much, open the project in a coding agent such as Claude Code, Cursor, Codex or Gemini CLI and paste the agent prompt from this page: it builds the project and publishes it to Fylo, and later publishes update the same URL./pricing is not a file in the build, so a direct visit or a refresh on that address has nothing to return. The home page and in-app links work. The quick fix is to ask Lovable to switch the router to HashRouter, which gives addresses like /#/pricing that always load. The prompt.index.html points at src/main.tsx, which a browser can’t run without Vite. Run npm run build and upload the dist folder. The pre-flight check on this page spots source code before you publish and tells you.dist folder. The URL stays the same. With the agent prompt, running it again updates the same site.index.html and replace the default social preview image. A Fylo blog helps too: its posts are served as plain HTML that every crawler can read./blog/ next to your app, with an editor, categories, an RSS feed and a sitemap, and nothing in your uploaded build changes. The free plan includes 10 published posts. Blog guide.Built with another AI? See Claude artifacts hosting, ChatGPT website hosting and Gemini website hosting.
Lovable built it.
Give it a domain of its own.
Drop the build once. We handle the milliseconds.
Host your Lovable app free No signup to try. Your domain from $6.99/mo. Live in seconds.