Your website is a blank white page — here's what that actually means

What does a blank white page actually mean?

You typed in your own address and got nothing. Not an error, not a spinner, not a half-loaded page — a clean, empty white rectangle. The tab title might even be right.

This almost never means your work is deleted. Your project, your pages, your database rows are all sitting where you left them. What happened is narrower and more boring than it feels.

There are two completely different blank pages, and they look identical from the outside. One is a crash inside your app. The other is your app never arriving in the first place. The fix is different for each.

How do I find out which kind of blank page I have?

Open the blank page. Right-click anywhere on it and choose Inspect (or press F12). Click the tab marked Console. You will see either nothing, or a few lines in red.

Those red lines are the app telling you where it gave up. You don't need to understand the words. You need to copy them, all of them.

While you're there, click the tab marked Network and reload. If you see rows glowing red next to files ending in .js or .css, that's the second kind — the browser asked your host for your app's files and was told they aren't there. One developer on Vercel's community forum hit exactly this: the app ran fine on their own machine, then showed a white screen on deploy with those files missing.⁵

What causes a blank page most often?

It works in preview but not on the published site. This is the most reported version, and it's maddening because everything looks fine until real people try to use it. The published version is a separate frozen copy of your app, not a live mirror of the builder. Republishing is genuinely the first thing to try, and it's free.

One guide to broken Lovable apps puts a stale published copy at the top of its list, alongside a build error blanking the screen, login redirect settings pointing at the wrong address, a missing secret, and database access rules silently returning nothing.⁴

A setting that exists in one place and not the other. Your app needs a handful of secret values to talk to its database or an outside service. When you build, the tool has them. When the host builds the published copy, it only has what you gave the host. If one is missing, the app often doesn't degrade gracefully — it stops dead at startup, which is a white screen.⁷

There's a second trap on top. The tooling most AI builders generate only passes through values whose names begin with a specific prefix — Vite requires them to start with VITE_. Name it something else and it simply won't be there when the app looks for it. No warning, no error, white page.⁸

One bad piece of data. Your app fetches something, expects a list, gets nothing, and tries to read the first item of nothing. That's a crash. It explains the version that confuses people most: the page was fine yesterday and you changed nothing. You didn't — but a user did, or a row got deleted, or a permission changed.

The host itself. Sometimes it isn't you. Supabase, whose database sits under a huge number of AI-built apps, keeps a public record of its own problems, including an investigation into users in one country being unable to reach it at all.⁹ "The app is broken" and "the app is broken for some people" are different problems.

The blank flash that isn't really a blank page. Worth knowing this exists so you don't chase it. One Lovable user reported clicking a sidebar tab, seeing the page appear briefly, then a white screen covering the preview for about four seconds before the app displayed — while the same address in a new window worked normally.³ Slow is not the same as broken.

How do I fix a blank website, step by step?

1. 1
   Try a different device or a private window

   Load your site on your phone with wifi off. If it works there and not on your laptop, your laptop is holding an old broken copy. Hard reload and move on.
2. 2
   Republish

   Then check that the address you're testing is the published one, not the builder's preview. These are different copies of your app.
3. 3
   Open the console and copy the red text

   All of it, exactly as written. You don't need to understand it — you need to hand it over.
4. 4
   Give the red text to your AI tool

   One sentence of context is enough. You are no longer asking it to guess, which is the difference between one message and seventy-five.
5. 5
   Check your secret settings if a name in capitals appears

   A name in capitals with underscores is one of your secret values. Confirm it exists on your host, that it's spelled identically, and that it applies to the live site. Then republish — values added after a build don't reach a build that already happened.

My published site shows a blank white page. It works in the builder preview but not on the live address. Here is the exact error text from the browser console — tell me what is missing and what to change:

[paste the red text here]

How do I stop finding out from a customer next time?

Here's what actually stings about a blank page. Not the fixing. The fact that you found out because someone messaged you, or because you happened to open your own site — and you have no idea how long it had been like that. An hour? Since Tuesday?

That's the gap Fomio was built to close. You paste a link, it works out what to watch, and it checks from outside — from where your users are, not from inside the builder where everything always looks fine. It reports one of three things: Working, Having trouble, or Down. When something breaks it emails you and says in plain language what likely went wrong. On the paid plans it writes the prompt to paste straight into the tool you built with.

The free plan watches one app, checks every five minutes, emails you when it breaks, keeps a week of history, and needs no card. Builder watches three, checks every minute, keeps thirty days, and writes the fix prompts. Pro watches fifteen and gives your users a page they can check themselves instead of messaging you. Current prices are on fomio.ai/pricing.

Do the console check first, though. Today's blank page is probably a missing key or a stale publish, and both are twenty-minute problems once you stop guessing.