Vercel 404 NOT_FOUND: How to Fix It Before You Deploy
Your build succeeded. Your app still shows NOT_FOUND. Here is the actual cause, and the one change that prevents it from ever happening.
How to Deploy a Lovable App to Vercel
Your code already lives on GitHub. Here is how to turn it into a real website anyone can visit.
How to Connect a Custom Domain to Vercel
Your app already has a free Vercel address. Here is how to point your own domain at it instead.
About Deployment
Getting an app live is often where momentum stalls, not because the app is broken, but because a config file, environment variable, or routing rule is quietly misconfigured. These guides walk through the deploy errors people actually hit on platforms like Vercel, and how to read the error message instead of guessing.
Most deploy errors are configuration, not code
A 404 or build failure after deployment is rarely a sign your app is fundamentally broken. It is almost always a missing environment variable, an incorrect build command, or a routing file in the wrong place.
Reading the actual error
Deploy logs tell you exactly what failed if you know where to look. These guides show you how to find the real error inside the noise, instead of restarting the deploy and hoping it works.
Why does my app work locally but break after deploying?
This is almost always caused by a missing environment variable, a different Node version, or a build command that behaves differently in production. Check the deploy log first.
What is the most common deploy error for new apps?
A 404 on routes that work locally, usually caused by a missing rewrite rule or incorrect output directory setting on the hosting platform.