No Output Directory found on Vercel

What it means

Vercel documents that the build step fails when the output directory is missing, empty or invalid, for example when it is not a directory. Only the contents of the Output Directory are served statically. When Vercel detects a framework it sets the Output Directory for you.

How to fix it

1. Run the build command locally and see which folder it creates. Confirm the files are generated where the Output Directory setting points.
2. In the project settings, check the Framework Preset and the Output Directory. When Vercel detects a framework it sets the Output Directory for you, so a manual override that does not match your build is worth removing.
3. Check the Build Command and the Root Directory. If the app lives in a subfolder or monorepo package, the Root Directory must point to it.
4. Check vercel.json. An outputDirectory value there overrides the setting for that deployment.
5. For a project that needs no build, choose Other as the Framework Preset. Vercel then serves public if it exists, and the project root otherwise.
6. If you use Turborepo or Nx caching, redeploy without the build cache. If that succeeds, the output directories are not configured in turbo.json or nx.json.

{
  "outputDirectory": "dist"
}

What a DeployDoctor scan can check

The build configuration check reports a missing build script, more than one lockfile and an engines.node range that Vercel cannot run. A scan reads the repository only. It cannot see the Output Directory or Framework Preset saved in your Vercel project settings.

Sources

• Vercel documentation: Error List, Missing public directory
• Vercel documentation: Configuring a Build, Output Directory
• Vercel guide: Missing routes-manifest.json or No Output Directory with Turborepo or Nx

Documentation last checked 2026-10-28. Vercel can change its documentation; confirm against the linked pages.