← Blog · Published Oct 18, 2026 · Updated Oct 19, 2026 · by the Vibefixr team

Lovable app shows a blank white screen after deploy? Here’s why

You built the app in Lovable, it works in the preview, and then you deploy it to Vercel, Netlify or your own server and get… nothing. A white page. No error message, no layout, just white.

The good news: a blank screen is almost never a mystery. The HTML loaded fine. What failed is the JavaScript that is supposed to draw your app, and it crashed before React could render anything, including your error screens. The cause is written down in one place: the browser console.

Step 1: read the console, not the page

Open the deployed site, press F12 (or right-click → Inspect), switch to the Console tab and reload. The first red line is your clue. The most common ones:

Cause 1: environment variables that never made it into the build

This is the big one. Most Lovable apps talk to Supabase through a client file (often src/integrations/supabase/client.ts) that reads values like VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY (older projects use VITE_SUPABASE_ANON_KEY). Inside Lovable those are injected for you. Your .env file is not in Git, so when Vercel or Netlify builds the repo, those values are simply undefined, and creating the Supabase client throws while the bundle is still loading.

Two details trip people up:

• Vite bakes VITE_ variables in at build time. Adding them in the hosting dashboard does nothing until you trigger a fresh build. Saving the variable is not enough; redeploy.
• Names must match exactly. If the code reads VITE_SUPABASE_ANON_KEY, a variable called VITE_SUPABASE_PUBLISHABLE_KEY won’t help. Search your repo for import.meta.env to see every name the app expects, and copy the values from the .env file in Lovable’s code view.

Only ever put the publishable/anon key in a VITE_ variable. Anything with that prefix ends up in public JavaScript. A service_role or sb_secret_ key there is a data breach, not a config fix. See what to do if that already happened.

Cause 2: the host is serving the wrong folder

Classic Lovable projects are Vite + React apps. npm run build writes the finished site to dist/. If your host publishes the repo root, or a folder called build (the Create React App convention), it serves an index.html that points at files that don’t exist. On Netlify, check Build command = npm run build and Publish directory = dist. Vercel usually detects Vite on its own.

Cause 3: asset paths that point to the wrong place

If someone (or an AI prompt) set base in vite.config.ts, for example to deploy under a sub-path like GitHub Pages, every script URL gets that prefix. Deploy the same build to the root of a domain and the scripts 404. Unless you really host under a sub-path, base should be / or absent.

The “MIME type text/html” error has a second, harmless-looking cause: a tab that was open before you redeployed. It asks for an old file name (index-abc123.js) that no longer exists, and your SPA fallback answers with index.html. A hard refresh fixes it for you. Your users hit the same thing, so it’s worth handling in the app.

Not sure which of these is your problem? The free health check looks at your live app in seconds, or request a free scan and we’ll tell you what we find.

Cause 4: the home page works, but other pages are blank or 404

If / loads but refreshing /dashboard fails, the host doesn’t know that every route should be answered by index.html. That’s a routing rule, not a code bug. We cover it in detail in 404 on refresh after deploy; the same fix applies to Lovable.

Cause 5: a newer Lovable project deployed like an old one

According to Lovable’s own hosting docs, projects created from May 13, 2026 use TanStack Start instead of a plain Vite SPA. Those apps have a server part (server rendering, server functions, API routes), so uploading only static files to a CDN or object storage leaves you with a page that can’t do its job. Check package.json: if it lists @tanstack/react-start, you need a host that runs the server output (Lovable names Vercel, Netlify and Cloudflare Pages as auto-detected), plus the server-side variables such as SUPABASE_URL and SUPABASE_PUBLISHABLE_KEY.

It loads now, but login bounces you back

Not a blank screen, but it usually shows up right after. Supabase Auth only redirects to URLs it knows about. Add your new production domain to the Site URL and Redirect URLs in Supabase, and in Google/GitHub OAuth settings if you use social login.

A quick checklist

• Console error read and understood
• All import.meta.env names set on the host, followed by a fresh build
• Publish directory is dist (classic Vite projects)
• No unexpected base in vite.config.ts
• SPA fallback rule in place for deep links
• Stack checked: TanStack Start projects need a server-capable host
• Auth redirect URLs updated for the new domain

If you’ve been through all of that and the page is still white, the crash is somewhere in your own code, and the console stack trace tells you which file. That’s the point where a second pair of eyes saves hours.

FAQ

Related guides

• Your Lovable app freezes or goes blank right after login: here’s why
• Bolt.new app shows 404 when you refresh a page? Here’s why
• Supabase returns an empty array but the table has data? It’s usually RLS
• Google login sends users to localhost after you publish? Here’s the fix

Launching soon? Run through our launch checklist for AI-built apps: 14 checks, each linked to the full guide.

Information here is checked against official docs at the time of writing. Platforms change, so verify against the linked sources.