← All errors · VercelVercel build & deploy errors
404: NOT_FOUND on Vercel
Exact error
404: NOT_FOUND. Code: NOT_FOUND
What it means
Vercel has no file or route for the requested path.
Likely causes
- Wrong Output Directory or Framework Preset in project settings.
- Single-page app (Vite/React Router) without a rewrite, so refreshing a deep link 404s.
- Deployment URL pointing to a deleted deployment.
How to fix it
Check Project → Settings → Build & Development: framework preset and output directory (Vite uses dist).
For SPAs with client-side routing, add a rewrite:
// vercel.json { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }
Prevent this next time
- Add a CI job that runs `npm ci && npm run build` on every push, mirroring a clean Vercel build.
- Pin your Node.js version in package.json `engines` and commit your lockfile.
Guide: catch outages before your users do.
FAQ
What does "404: NOT_FOUND on Vercel" mean?
Vercel has no file or route for the requested path.
What usually causes it?
Wrong Output Directory or Framework Preset in project settings. Single-page app (Vite/React Router) without a rewrite, so refreshing a deep link 404s. Deployment URL pointing to a deleted deployment.
How do I fix it?
1. Check Project → Settings → Build & Development: framework preset and output directory (Vite uses dist). 2. For SPAs with client-side routing, add a rewrite:
Related errors
Get new fixes weekly
No spam. Unsubscribe anytime. Privacy