Mendlark / Guides

Vercel "No Output Directory named dist found": how to fix it

The build log ends with Error: No Output Directory named "dist" found after the Build completed. You can configure the Output Directory in your Project Settings. The build itself worked. Vercel just looked for the finished site in a folder that is not there.

Stuck on this? Get it fixed for €49.

Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.

Get it fixed for €49

1. The output folder has a different name

Vite writes to dist, Create React App to build, Next.js to .next, and some static setups to public or out. Read the last lines of your local npm run build to see where files land, then set Project Settings → Build and Deployment → Output Directory to match, or choose the correct Framework Preset and leave the field empty.

2. The wrong framework preset was picked

If the preset says "Other" for a Vite app, or "Next.js" for a plain Vite app, Vercel looks in the wrong place. Switch the preset to Vite (or the right one), leave Output Directory on its default and redeploy.

3. The app lives in a subfolder

If your repo has the app inside a folder such as frontend/ or apps/web, set Root Directory to that folder. Otherwise the build runs at the repo root and the output lands somewhere unexpected.

4. The build command does not actually build

A package.json where build is missing, or does something else (for example only runs type checks), produces no folder. Run it locally and confirm it creates the output:

npm run build
ls dist   # or build, out, public

If the build fails instead, see build failed with exited with 1.

5. An override in vercel.json

A leftover outputDirectory in vercel.json beats the dashboard setting. Remove it, or make it match your real folder:

{
  "buildCommand": "npm run build",
  "outputDirectory": "dist"
}

6. Case and gitignore surprises

Vercel's servers are case sensitive, so Dist is not dist. Also check the folder isn't created by a script that only runs on your machine, and that a custom vite.config build.outDir has not renamed it.

Quick checklist

  • Local build creates a folder, and you know its name
  • Output Directory empty (with the right preset) or matches that name
  • Root Directory points at the app folder in a monorepo
  • No stale outputDirectory in vercel.json
  • Once deployed, a blank page is a different problem: blank page after deploying a Vite app

Stuck on this? Get it fixed for €49.

Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.

Get it fixed for €49

Still stuck?

Mendlark fixes this kind of problem for a fixed €49 (launch price, normally €79). We agree the problem first, test the fix and send it as a pull request, so nothing changes in your app until you merge it. If we can't fix it, you don't pay. Get the €49 fix, or start with a free scan.

Not sure what else is wrong? Paste your app link into the free instant check and get a plain-English list of problems in seconds.