vercel/next.js · error · ExportError
Found pages with `fallback` enabled: ${[...fallbackEnabledPa
Error message
Found pages with `fallback` enabled:
${[...fallbackEnabledPages].join('\n')}
Pages with `fallback` enabled in `getStaticPaths` can not be exported. See more info here: https://nextjs.org/docs/messages/ssg-fallback-true-export
What it means
Error "Found pages with `fallback` enabled: ${[...fallbackEnabledPages].join('\n')} Pages with `fallback` enabled in `getStaticPaths` can not be exported. See more info here: https://nextjs.org/docs/messages/ssg-fallback-true-export " thrown in vercel/next.js.
Source
Thrown at packages/next/src/export/index.ts:622
allExportPaths.push({ ...entry, path: normalizedPath })
if (prerenderManifest && !options.buildExport) {
const prerenderInfo = prerenderManifest.dynamicRoutes[entry.page]
if (prerenderInfo && prerenderInfo.fallback !== false) {
fallbackEnabledPages.add(entry.page)
}
}
}
if (allExportPaths.length === 0) {
if (!prerenderManifest) {
return null
}
}
if (fallbackEnabledPages.size > 0) {
throw new ExportError(
`Found pages with \`fallback\` enabled:\n${[...fallbackEnabledPages].join(
'\n'
)}\n${SSG_FALLBACK_EXPORT_ERROR}\n`
)
}
let hasMiddleware = false
if (!options.buildExport) {
try {
const middlewareManifest = require(
join(distDir, SERVER_DIRECTORY, MIDDLEWARE_MANIFEST)
) as MiddlewareManifest
const functionsConfigManifest = require(
join(distDir, SERVER_DIRECTORY, FUNCTIONS_CONFIG_MANIFEST)
)
View on GitHub (pinned to 258b1c1bc0)
Solutions
- Remove fallback: true from getStaticPaths for the listed pages, or drop output: export.
Defensive patterns
Strategy: validation
When it happens
Trigger: next export is run while pages use getStaticPaths with fallback enabled.
Common situations: Using fallback: true or blocking in getStaticPaths together with output: export.
AI-assisted analysis of vercel/next.js@258b1c1bc0 (2026-08-19).
Data as JSON: /api/errors/763e85a636e1c863.
Report an issue: GitHub.