React Router shows a blank page or the error screen for URLs that match no route
A mistyped URL shows a blank page or a default error screenShort answer
React Router only renders what you register. Add a catch-all splat route with the path *, throw a 404 response from it, and export an ErrorBoundary that recognises the 404 and renders your not found page. Otherwise the default error screen appears.
Fix it fast
1Find out which cause you have
List the registered routes. If there is no route with the path *, unknown URLs have nowhere to go.
grep -rn "route(" app/routes.ts2Match what you see, then jump to its fix
What does the error look like?
A mistyped URL shows a blank page or a default error screenNo custom 404 page appears for an unknown path
Cause 1 of 2
No catch-all route is registered
1Check
A splat route matches any URL that no other route matched.
cat app/routes.ts2Fix
Register a route with the path * pointing at its own module, and throw a 404 response from its loader.
// app/routes.ts
import { type RouteConfig, route, index } from "@react-router/dev/routes";
export default [
index("./home.tsx"),
route("*", "./catchall.tsx"),
] satisfies RouteConfig;
// app/catchall.tsx
export function loader() {
throw new Response("Page not found", { status: 404 });
}3Verify
Open a URL that does not exist.
curl -I http://localhost:5173/does-not-existConfirmed by reactrouter.com
Cause 2 of 2
The 404 is thrown but nothing renders it nicely
1Check
A thrown response is shown by the closest error boundary. Without your own, the default one renders.
grep -rn "ErrorBoundary" app2Fix
Export an ErrorBoundary from the catch-all module (or the root) and branch on the 404.
import { isRouteErrorResponse } from "react-router";
export function ErrorBoundary({ error }: { error: unknown }) {
if (isRouteErrorResponse(error) && error.status === 404) {
return <h1>Page not found</h1>;
}
return <h1>Something went wrong</h1>;
}3Verify
Reload the unknown URL and read the page.
npm run devConfirmed by reactrouter.com
How do I stop it coming back?
- Keep the catch-all route last in the list, as the fallback.
- Use the same 404 handling for missing records inside loaders, with a thrown data response.
- Check the status code too, so search engines do not index the not found page as a normal one.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix