Build failed with Error: routes-manifest.json" couldn't be found

ebatdev-7380 · October 17, 2025, 12:48pm

My build continuesly failing with Error: The file “/vercel/path0/.next/routes-manifest.json” couldn’t be found.
I dont have made any changes in config, still it failing.
What could be the reason ?

jacobparis · October 17, 2025, 8:13pm

We log the possible causes here. I checked your build logs and I’m seeing an out of memory issue, so if you haven’t touched anything else I think you’re falling into the “can also be caused by a Next.js build failure” case

You have a two options

upgrade to get higher memory limits
reduce the memory usage during build

I suspect it’s the Sentry sourcemap generation that is using most of the memory. Try disabling that temporarily to see if it unblocks builds, and if so you may be able to configure it to use less memory

github.com/vercel/vercel

errors/now-next-routes-manifest.md

main

# Routes Manifest Could Not Be Found

#### Why This Error Occurred

This error is often caused by a misconfigured "Build Command" or "Output Directory" for your Next.js project.

#### Possible Ways to Fix It

In the Vercel dashboard, open your "Project Settings" and draw attention to "Build & Development Settings":

1. Ensure that the "Build Command" setting is not overridden, or that it calls `next build`. If this command is not overridden but you are seeing this error, double check that your `build` script in `package.json` calls `next build`. If `buildCommand` exists in `vercel.json`, make sure it calls `next build`.
2. Ensure that the "Output Directory" setting is not overridden. This value almost never needs to be configured, and is only necessary if you override `distDir` in `next.config.js`. If `outputDirectory` exists in `vercel.json`, remove that property.
3. For `next export` users: **do not override the "Output Directory"**, even if you customized the `next export` output directory. It will automatically detects the correct output.

In rare scenarios, this error message can also be caused by a Next.js build failure (if your "Build Command" accidentally returns an exit code that is not 0).
Double check for any error messages above the Routes Manifest error, which may provide additional details.

ebatdev-7380 · October 18, 2025, 5:13am

If its due to build time, why build is failing within 2 minutes ? @jacobparis
Could you please help here, it blocking my important fixes deploymnets

Topic		Replies	Views
Vercel Deployment error Help nextjs	2	393	October 11, 2024
404 error after sucessful deploy Help nextjs	5	141	March 4, 2025
Build RBuild runs Locally Fine but on Vercel says Error Help nextjs	3	55	October 29, 2025
Nextjs build failing Discussions nextjs	3	168	March 19, 2025
Build Failed Help nextjs , react	2	118	February 5, 2025

Build failed with Error: routes-manifest.json" couldn't be found

Related topics