How to publish a Lovable app, and what to do when it fails

Lovable's publishing docs, read on November 14, 2026, put it in 2 clicks: “click the Publish button in the top-right corner of the editor,” then click Publish in the dialog, and “When the deploy finishes, Lovable shows your live link.” The address ends in lovable.app. Lovable's hosting docs add that “Publishing to a lovable.app URL is free and available on all plans,” and “Custom domains require a paid plan,” which starts with Pro at $25 a month. When a publish fails, Lovable shows a Publishing failed banner that names the cause, with Try again or Try to fix.

Every quote below comes from Lovable's docs and pricing page, and from Netlify's and Vercel's own pages, read on November 14, 2026 (JST). Lovable's docs pages carry no date of their own. Prices are in US dollars. Whether Lovable is free at all, with its credits and limits, is answered on Is Lovable free?

Publish in Lovable step by step

Lovable's docs walk through the Publish dialog in this order:

1. Open the dialog. Click Publish at the top right of the editor, next to Share. “On narrow windows it collapses to an icon without a label.” By default, “editors and above” can publish.
2. Set the address. The first time, edit the suggested address in the Website URL field or keep it. “By default, your app is published to your-app.lovable.app.” You can change it later in Project settings → URL subdomain.
3. Choose who can open it. Public means “anyone with the URL can visit the published app.” On Free and Pro, the other choice is Invite only, for up to 10 people per project. Workspace needs Business or Enterprise.
4. Check the security scan. The dialog runs a Quick scan and shows No security issues found or a count of findings. “Findings do not block publishing by default.” If your app uses Lovable's built-in backend and has critical findings, a Review security findings dialog opens, with Review, Publish anyway, and Try to fix.
5. Click Publish. A progress bar runs, and the dialog then says Your website is live, with Visit site and your address.

The live site is a snapshot. “The live site keeps showing the version you published, and later changes stay off it until you publish again.” To put new changes live, click Publish, then Publish changes. A small dot on the Publish button tells you the project has changes newer than the live version.

You can also type “Publish my app” in the project chat. That route “is treated as standard build usage and consumes credits,” while the dialog's button costs nothing. To take the site down, open Publish, then the ⋮ menu, and select Unpublish, or use Project settings → Publishing → Unpublish project.

What publishing costs on each Lovable plan

Publishing itself is free. Lovable's publishing FAQ says: “Publishing from the publish dialog costs nothing and works even when your credit balance is zero.” What costs money is your own domain, the badge, and the work your app does while it runs. The table is from Lovable's subscription plans and hosting docs.

A live site doesn't spend credits by itself. The hosting docs say “A live site does not consume credits on its own. Usage-based Run credits cover the work your app does while it runs, such as backend activity and AI features.” Lovable's pricing page adds that for most small or new apps, “the cost to publish, view, and keep your app running will be minimal and fully covered by the included grant,” and that apps with “significant visitor traffic and/or size may start incurring cost on top of the included grant.”

Running out of credits leaves the site up. “Running out of credits does not remove your published site. Building stops, and apps that rely on the backend or AI features can pause until credits are available again.” A paused backend can stay paused: open More → Database and click Wake up.

Annual billing “gives you two months free compared with paying monthly,” per the plans page. Higher Pro tiers add credits, up to 10,000 a month for $2,250.

Publish a Lovable app on your own domain

Lovable's custom domain docs say “Custom domains are available on paid plans.” The cheapest is Pro, from $25 a month.

• 3 ways to add one. Buy a domain through Lovable, connect one you own, or transfer one to Lovable. Start from Project → Settings → Domains, or Add domain in the Publish dialog.
• Publish first. “You need to publish your project before your domain can start serving your site.” Until the domain shows Active, Lovable keeps publishing to the lovable.app address.
• Root and www together. For a domain from another provider, keep Redirect www.yourdomain.com → yourdomain.com on when you connect the root domain.
• The DNS record. The standard A record value is 185.158.133.1, which many Lovable sites share. A spam blocklist listing that address doesn't take your site down.
• Several projects, one domain. One exact domain serves one project, but subdomains can go to different ones, such as yourdomain.com to one project and blog.yourdomain.com to another.
• After a downgrade. “Connected domains keep serving your published app,” but on Free “you can't buy domains or connect domains to projects” until you upgrade again.

Lovable publishing failed or not working

When a publish fails, “a Publishing failed banner appears in the Publish dialog with a message explaining what went wrong and how to resolve it.” Lovable's troubleshooting lists these cases.

The publish worked, but the site looks wrong. Lovable's FAQ gives 4 checks:

• Old version on the live site. Publishing deploys the project “as it was at that moment.” Click Publish, then Publish changes.
• Wrong address. The lovable.app address uses the project's URL subdomain, “which can differ from the project's display name.” A custom domain's DNS changes “can take time to take effect.”
• Site down. Check status.lovable.dev, then whether the project is still published. A Free project can be unpublished after about a year with no visits, no owner login, no edits or publishes, and no custom domain. Lovable emails you, keeps the project and its lovable.app address, and you publish again to bring it back.
• “App temporarily unavailable.” On Free, apps created from May 13, 2026 refuse requests above 1,000 per project in 10 seconds. A visitor “can try again after a minute.”

If the site loads on some networks but not others, the hosting docs say “The visitor's internet provider is blocking the site,” and “Lovable can't lift a block that an internet provider applies.”

Host a Lovable app outside Lovable

You can run a Lovable app on another host. Lovable's outside hosting guide gives 2 ways to take the code: Git sync, “available on all plans,” which keeps a GitHub, GitLab, or Bitbucket repository in sync both ways, and Download codebase, “available on paid plans,” a one-time .zip.

What the new host needs depends on when the app was made:

For Vercel, Netlify, and Cloudflare Pages, the guide says to set the build command to npm run build with Node.js 22, and on Netlify and Cloudflare Pages the output directory to dist. An app on Lovable's built-in backend keeps calling it from the new host, so the host also needs VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY, from the repository's .env file. Moving the backend itself to your own Supabase project is a separate migration in the same guide.

Netlify's pricing page lists its Free plan at $0 with a “300 credit limit / month” and custom domains with SSL. Vercel's Hobby plan is free, but section 4 of Vercel's terms says “You shall only use the Services under a Hobby plan for your personal or non-commercial use.” Is Netlify free? and Can you use Vercel's Hobby plan for a commercial site? cover each one.

When the result is one static page

Some Lovable projects are a single page with no backend: a landing page, a waitlist, a portfolio, an event page. That kind of page can go on Convika. Convika hosts one HTML page at a lasting link. It runs no server code: no Node.js, no database, no sign-in, no server functions. A page's scripts can't send requests to another site's API either, so calls to Supabase fail on Convika. If your Lovable app saves data, logs people in, or runs server functions, Convika is not its host: keep it on Lovable, or move it as the section above describes.

For a page with no backend, there are 3 ways in:

• Drop the built folder. An older React + Vite app builds to a dist folder. Run npm run build on your computer from the Git-synced repository, then drop the dist folder, or a .zip of it, in the box at the top of this page. In your browser, the box puts the CSS, JavaScript, images, and fonts that index.html names inside one file, up to 2 MB, and lists any file it couldn't include. A project's source folder gets this answer: “This is a project's source code, which runs only after a build. Run npm run build, then drop the dist folder it makes.” A TanStack Start app renders its pages on a server, so its build isn't a folder of finished pages; use one of the next 2 ways.
• Rebuild it from the lovable.app link. The page must be public. Paste the link into the free rebuild tool and click Rebuild my page, with no account. It writes a new page in your page's colors and fonts and lists what it changed. The rebuild is a new page, not a copy of your project.
• Ask an AI for one HTML file. Paste the page's code into ChatGPT, Claude, or Gemini and ask for “one HTML file, with the CSS and JavaScript inside it and full https:// links for images.”

Free includes 1 published page, 1 custom subdomain such as www.yourbrand.com, a form that keeps entries, 10,000 page views a month, and 90 days of visitor stats, with a small Convika bar at the bottom. Pro costs $12 a month and removes the bar. Section 7 of the terms allows commercial use on every plan.

Publish a Lovable landing page on Convika

1. Get the page as a folder or one file

Build the project and keep its dist folder, or save the single HTML file an AI wrote for you. For a page you'd rather rebuild from its link, use the rebuild tool instead and skip to step 3.

2. Drop it in the upload box

Drop the folder, the .zip, or the .html file in the upload box at the top of this page, or open Paste code. Click Get my preview link. The preview works for 3 minutes, with the page's scripts and forms off, and needs no account.

3. Keep the page and publish it

Click Keep this page — free, no card and sign up. On the page's screen, click Publish page, choose Public, and click Next. The first time, click Publish free. The page goes live at an address like yourpage.convika.page, with the Convika bar at the bottom.

Lovable, another host, or Convika

Frequently asked questions

How do I publish my Lovable website?

Click Publish at the top right of the editor, then Publish in the dialog. Lovable runs a quick security scan, deploys the project, and shows Your website is live with your lovable.app link. To put later edits live, click Publish, then Publish changes.

Is publishing on Lovable free?

Yes. Lovable's docs say “Publishing to a lovable.app URL is free and available on all plans,” and publishing from the dialog “works even when your credit balance is zero.” Your own domain and hiding the badge need a paid plan. Is Lovable free? covers the Free plan's credits.

How much does it cost to publish a Lovable site on a custom domain?

Lovable Pro, from $25 a month or $250 a year, is the cheapest plan with custom domains. The domain's registration is extra: buy it through Lovable, which bills it apart from your plan, or connect one you already own.

Does publishing on Lovable use credits?

Not from the Publish dialog. Asking Lovable to publish in the project chat “is treated as standard build usage and consumes credits.” Once the site is live, backend work and AI features use Run credits, covered first by the monthly Cloud grant of 20 credits.

Why is my Lovable publish failing?

The Publishing failed banner names the cause: a temporary issue, an error in your app's code, a configuration problem such as a file too large to include, an expired connection such as Supabase, a database change that conflicts with live data, or an error on Lovable's side. Click Try again for a temporary issue, and Try to fix for a code or configuration error.

Why don't my changes show on my published Lovable site?

The live site is a snapshot from your last publish. Lovable says “Later changes do not reach your live app on their own.” Click Publish, then Publish changes. A dot on the Publish button shows when the project has unpublished changes.

Does a published Lovable site expire?

No. “Published sites have no fixed expiry date.” Lovable can unpublish a Free project after about a year with no visits, no owner login, no edits or publishes, and no custom domain. It emails you first, keeps the project and its address, and you publish again to bring it back.

How do I unpublish a Lovable project?

Click Publish, open the ⋮ menu in the dialog, and select Unpublish, or go to Project settings → Publishing → Unpublish project. The live URL stops working, and the project stays in the editor.

Can I host my Lovable app on Netlify or Vercel?

Yes. Connect Git sync, which is on every plan, and import the repository on the other host with npm run build and Node.js 22. An app created from May 13, 2026 needs a host that runs its server part; an older React + Vite app is a static dist folder. The app keeps using Lovable's built-in backend unless you migrate it.

Can I put a Lovable landing page on Convika?

Yes, if the page needs no backend. Drop the built dist folder in Convika's upload box, or rebuild the page from its lovable.app link with the free rebuild tool. Convika hosts one static page and runs no server code, so an app that saves data, logs people in, or calls Supabase stays on Lovable.

Sources

Each source was read on November 14, 2026 (JST). Lovable's docs and pricing page carry no date of their own.

• Lovable docs: Publish your Lovable project, How Lovable hosts your app, Set up a custom domain, Subscription plans, Deploying and hosting outside Lovable, FAQ
• Lovable pricing
• Netlify pricing (no date on the page)
• Vercel Terms of Service (last updated October 19, 2026) and Adding a custom domain (last updated September 16, 2026)