Skip to content

docs(how-to/file-route-conventions): add "Catch-all Route" section #13769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 6, 2025
+11 −0
Merged

docs(how-to/file-route-conventions): add "Catch-all Route" section #13769

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6c89ead
Update file-route-conventions.md
davidbielik Jun 6, 2025
85a3176
Update docs/how-to/file-route-conventions.md
timdorr Jun 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/how-to/file-route-conventions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -291,6 +291,17 @@ export async function serverLoader({ params }) {
}
```

## Catch-all Route

To create a route that will match any requests that don't match other defined routes (such as a 404 page), create a file named `$.tsx` within your routes directory:

| URL | Matched Route |
| -------------------------------------------- | ------------------------ |
| `/` | `app/routes/_index.tsx` |
| `/about` | `app/routes/about.tsx` |
| `/any-invalid-path-will-match` | `app/routes/$.tsx` |


## Escaping Special Characters

If you want one of the special characters used for these route conventions to actually be a part of the URL, you can escape the conventions with `[]` characters. This can be especially helpful for [resource routes][resource_routes] that include an extension in the URL.
Expand Down