What causes "Vercel 404 NOT_FOUND After Deploy"?

Framework Preset set to 'Other' so Vercel serves the wrong folder Output Directory does not match the build output SPA (React/Vite) without a catch-all rewrite Dynamic routes without dynamicParams / generateStaticParams fallback in Next.js Custom domain DNS pointing elsewhere vercel.json not committed or rewrites conflicting with next.config.js

How do I fix "Vercel 404 NOT_FOUND After Deploy"?

1. Test the .vercel.app URL first: Open the deployment's .vercel.app URL If it works but your domain 404s, fix the domain DNS (see domain guide) If both 404, continue with build output checks 2. Fix Framework Preset and Output Directory: Settings > Build and Deployment > Framework Settings Select the correct framework (e.g. Next.js, Vite) Make sure Output Directory matches your build folder (dist, build, out) Redeploy 3. Add an SPA rewrite: Create vercel.json at the repository root Add: { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] } Use /((?!api/).*) as source to keep API routes working Commit the file and redeploy 4. Fix Next.js dynamic routes: Set export const dynamicParams = true in the route Add a revalidate interval or use force-dynamic only where needed Add default.js for every parallel route slot Move rewrites from vercel.json into next.config.js

Try or Bye

Browse all analyzed products with real user feedback patterns.

Vercel 404 NOT_FOUND After Deploy

Ongoing Web Updated October 21, 2026

Quick answer

A sitewide 404 after a successful Vercel build usually means the wrong Framework Preset or Output Directory; 404s only on refreshed routes mean a single-page app is missing a rewrite to index.html.

Most likely fix: Test the .vercel.app URL first.

Symptoms

Build succeeds but the site shows '404: NOT_FOUND', either on every page, only on dynamic routes, only after refreshing a client-side route, or only on the custom domain.

Why it happens

Framework Preset set to 'Other' so Vercel serves the wrong folder
Output Directory does not match the build output
SPA (React/Vite) without a catch-all rewrite
Dynamic routes without dynamicParams / generateStaticParams fallback in Next.js
Custom domain DNS pointing elsewhere
vercel.json not committed or rewrites conflicting with next.config.js

How to fix it

Try these in order — the most common fix is first.

1. Test the .vercel.app URL first
1. Open the deployment's .vercel.app URL
2. If it works but your domain 404s, fix the domain DNS (see domain guide)
3. If both 404, continue with build output checks
2. Fix Framework Preset and Output Directory
1. Settings > Build and Deployment > Framework Settings
2. Select the correct framework (e.g. Next.js, Vite)
3. Make sure Output Directory matches your build folder (dist, build, out)
4. Redeploy
3. Add an SPA rewrite
1. Create vercel.json at the repository root
2. Add: { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }
3. Use /((?!api/).*) as source to keep API routes working
4. Commit the file and redeploy
4. Fix Next.js dynamic routes
1. Set export const dynamicParams = true in the route
2. Add a revalidate interval or use force-dynamic only where needed
3. Add default.js for every parallel route slot
4. Move rewrites from vercel.json into next.config.js

This guide also covers

vercel 404 not found
vercel 404 after deploy
404 not_found vercel
vercel react router 404 on refresh
vercel page not found

Still not working?

If Vercel keeps failing, you're not alone. See every Vercel problem users report or the alternatives people switch to.

Other Vercel errors