Error AtlasError Documentation and Resolution
Back to searchMore Next.js errors

Next.js

Next.js getStaticPaths returned conflicting paths

Conflicting SSG Paths

Next.js found duplicate or overlapping static paths returned by getStaticPaths, which is invalid because every generated page path must be unique.

Conflicting SSG Pathsbuild

Observed message

Conflicting SSG Paths

Why it happens

  • Two pages resolve to the same generated static path.
  • A catch-all route returns a path that conflicts with a more specific route.
  • getStaticPaths includes duplicate entries for the same URL.

How to fix it

  1. Remove duplicate paths from getStaticPaths output.
  2. Check catch-all and specific routes for overlapping generated URLs.
  3. Ensure each static path is returned by only one page.

Official reference

Next.js Docs: Conflicting SSG Paths

Related errors

app/ Static to Dynamic ErrorNext.js app static to dynamic rendering errorStatic Bail Out CaughtNext.js caught a Partial Prerendering bailout errorNo Document Import in PageNext.js imported next/document outside _documentNo async Client ComponentNext.js client component cannot be async

Explore more

Next.jsBrowse more Next.js errorsbuildBrowse more build errors
Next.js Conflicting SSG Paths: causes and fixes | Error Atlas