Nuxt 3 — Nitro renderer not found for route

Nuxt 3 build fails because a route or page does not have a matching Nitro renderer, often after changing the rendering mode or nitro preset.

advanceddebuggingnuxtnitro

Symptoms

Error: Cannot find renderer for route /path
Build fails with "nitro renderer not registered"
Works in dev mode but fails during build

Possible causes

The nitro preset does not support the configured rendering mode
A custom renderer was removed but routes still reference it
The route is SSR but the preset is static-only

Diagnosis steps

Check the nitro preset

cat nuxt.config.ts | grep nitro

Interpretation

The preset determines available renderers; some only support static or SPA.

List registered renderers

npx nuxi build --debug 2>&1 | grep renderer

Interpretation

The debug output shows which renderers are available for the preset.

Root cause

The Nitro server does not have a renderer registered for the route rendering mode, so the build cannot generate the output for that route.

Fix

Match the rendering mode to the preset capabilities, register a custom renderer, or switch to a preset that supports the required mode.

Verify the fix

Run the build and confirm all routes generate without renderer errors; test the route in production.

Symptom walkthrough

Nuxt 3 build fails because a route or page does not have a matching Nitro renderer, often after changing the rendering mode or nitro preset. The error appears in production but may not surface in local development because the conditions that trigger it depend on the deployment environment or runtime configuration. Understanding the full symptom set helps distinguish this issue from similar errors.

Diagnosis in practice

Follow the diagnosis steps in the frontmatter to isolate the cause. Each step includes a command and an interpretation of the output. The goal is to narrow down whether the issue is in the configuration, the runtime, or the application code. Reproduce the error in a minimal setup before applying a fix.

Root cause

The Nitro server does not have a renderer registered for the route rendering mode, so the build cannot generate the output for that route.

Fix

Match the rendering mode to the preset capabilities, register a custom renderer, or switch to a preset that supports the required mode. After applying the fix, monitor the system to confirm the error does not recur under load or in different environments.

Verification

Run the build and confirm all routes generate without renderer errors; test the route in production. If the verification passes, the fix is confirmed; if not, re-examine the diagnosis steps for missed contributing factors.

Diagnostic commands

Run these commands to reproduce and diagnose the issue:

cat nuxt.config.ts | grep nitro
npx nuxi build --debug 2>&1 | grep renderer