Fix guide · updated 2026-11-09
Lovable publish not working: changes not showing, Publishing failed, or no Publish button
Publishing failed · Fix build errors · latest changes not on the live site
You clicked Publish in Lovable and nothing changed on your live site. Or the dialog shows Publishing failed, or there's no Publish button at all. Each of these has a short list of causes, and the Publish dialog (top right of the editor) usually tells you which one. Find what you see below.
1. The live site doesn't show your latest changes
This is the most common one, and nothing is broken. Lovable's docs explain that publishing deploys a copy of your project as it was at that moment. Everything you change afterwards stays in the editor until you publish again: click Publish, then Publish changes. A small dot on the Publish button means you have changes the live site doesn't have yet. Accepting a draft is not publishing either: its edits join your unpublished changes.
If the dialog said Your website was updated and you still see the old version:
- Reload without the browser's cache (
Ctrl+Shift+R, orCmd+Shift+Ron a Mac), or open the site in a private window. - Check that you're opening the exact published address. The
lovable.appaddress uses your project's URL subdomain, which can differ from the project's name, and changing the subdomain moves the site to a new address. - On a custom domain, DNS changes can take time. If the domain itself doesn't work, see Lovable custom domain not working.
If the live site opens on a blank page instead, see Lovable blank page or 404 after deploy.
If the live site is up to date and something on it is broken while the preview works, see Lovable published site not working.
2. The dialog shows "Fix build errors"
Instead of the publish button, the dialog shows Try to fix. Your latest changes failed to build, so publishing them would fail the same way. Click Try to fix and Lovable will try to fix it in the chat, or fix the error yourself, then publish once the preview builds. To read the real error and fix the common ones, see Lovable build unsuccessful.
3. A "Publishing failed" banner
The banner says which kind of failure it is. Lovable's docs list these, with what to do:
- A temporary issue, like a timeout or a rate limit on a connected service. Click Try again; retries usually work.
- An error in your app: a build error, or an edge function that couldn't be deployed. For a build error, the banner shows a short summary of it. Click Try to fix. If your edge functions fail once they're live, see Edge Function returned a non-2xx status code.
- A configuration issue in your project, for example a file too large to include. Click Try to fix.
- An external connection or secret that needs your attention, like an expired Supabase connection or a connected service that reached its plan limits. Lovable can't change those for you: reconnect the service or update its plan, then click Try again.
- A database change that conflicts with existing data. The banner shows the database's own error message. See the next section.
- An internal error on Lovable's side. Try again in a few minutes. If it keeps failing, contact Lovable support with your project link.
4. A database change conflicts with your live data
A change can work while you build and still fail when you publish, because your live database already holds rows that break it. We reproduced the usual cases on Postgres 16. Supabase databases run on Postgres, so the messages are the same. Here's what each one needs:
column "username" of relation "profiles" contains null values. A new required column was added, and the rows you already have don't have a value for it. Give the column a default, or add it as optional, fill in the existing rows, then make it required:
alter table public.profiles add column username text not null default '';
could not create unique index "profiles_email_key", with Key (email)=(a@x.test) is duplicated. The change makes a column unique, and some rows already share a value. Find them, decide which row to keep, then publish again:
select email, count(*) from public.profiles
group by email having count(*) > 1;
insert or update on table "orders" violates foreign key constraint "orders_profile_id_fkey", with Key (profile_id)=(99) is not present in table "profiles". The change links two tables, and some rows point to something that no longer exists. Find them:
select o.* from public.orders o
where not exists (select 1 from public.profiles p where p.id = o.profile_id);
invalid input syntax for type integer: "free". A column changes type, and some rows hold values that can't be converted. Clean up those values first, or keep the old type.
For this kind of failure, Lovable's banner offers Ask Lovable, and Lovable confirms with you before changing anything, since the fix touches real data. Read what it proposes before you agree. Deleting the rows that get in the way makes the error go away fastest, and it also deletes your users' data. If rows have to change, know which ones, and keep a copy first.
5. No Publish button, or you can't click it
- Narrow window: the button collapses to an icon without a label, next to Share.
- "You don't have permission to publish this project" when you hover it: publishing needs editor access or above. Ask the project's owner or a workspace admin.
- "Approval needed" or "Publishing blocked": an Enterprise workspace policy requires an admin's approval, or doesn't allow this kind of publishing. Use Request approval, or ask an admin.
6. People can't open the live app, or it asks them to log in
The row under the website address in the Publish dialog sets who can see the site. Public, the default, lets anyone with the link in. With Invite only on the Free and Pro plans, only the people you add can open it, after logging in, up to 10 per project. On Business and Enterprise plans, Workspace limits it to logged-in workspace members. A change of audience only takes effect when you click Publish or Publish changes.
7. The site was live and went offline
Published sites don't expire. Lovable may unpublish a project in a Free workspace after about a year with no visits, no owner login and no edits. An app that uses Lovable's built-in backend or AI features also needs credits available to keep answering requests. Publishing itself is free, but asking Lovable to publish from the chat uses credits like any other request.
Still stuck?
Write down the exact words of the banner, including the build or database error it shows, and what you changed since the last publish that worked. That's what anyone helping you will ask for first, and the change since the last good publish is usually where the problem is.
Other Lovable app problems? See Fix a Lovable app.