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 Vercel
Vercel makes deploying a modern web app straightforward, but the errors that show up right after a deploy, like a 404 on a route that worked locally, tend to confuse people who have not seen them before. These guides walk through the specific, common issues and how to actually fix them, not just restart the deploy.
Why a route can 404 after deploying
A route that works locally can 404 in production due to a missing rewrite rule, an incorrect output directory, or a framework preset that does not match your project structure.
Reading the deployment logs
Vercel deploy logs show the exact build output and errors in order. Reading them from the top, rather than jumping to the end, usually surfaces the real cause quickly.
Why do I get a 404 after deploying to Vercel?
This is most often a missing rewrite or redirect rule, or an output directory setting that does not match your framework. See the deployment guide for the exact fix.
Do I need to redeploy after changing an environment variable on Vercel?
Yes. Environment variable changes only take effect on the next deployment, so a fresh deploy is required after updating one.