app directory, nested folders are normally mapped to URL paths. However, you can mark a folder as a Route Group to prevent the folder from being included in the route's URL path.
This allows you to organize your route segments and project files into logical groups without affecting the URL path structure.
Route groups are useful for:
- Organizing routes into groups e.g. by site section, intent, or team.
- Enabling nested layouts in the same route segment level:
A route group can be created by wrapping a folder's name in parenthesis:
Organize routes without affecting the URL path
To organize routes without affecting the URL, create a group to keep related routes together. The folders in parenthesis will be omitted from the URL (e.g.
Even though routes inside
(shop) share the same URL hierarchy, you can create a different layout for each group by adding a
layout.js file inside their folders.
Opting specific segments into a layout
To opt specific routes into a layout, create a new route group (e.g.
(shop)) and move the routes that share the same layout into the group (e.g.
cart). The routes outside of the group will not share the layout (e.g.
Creating multiple root layouts
To create multiple root layouts, remove the top-level
layout.js file, and add a
layout.js file inside each route groups. This is useful for partitioning an application into sections that have a completely different UI or experience. The
<body> tags need to be added to each root layout.
In the example above, both
(shop) have their own root layout.
Good to know:
- The naming of route groups has no special significance other than for organization. They do not affect the URL path.
- Routes that include a route group should not resolve to the same URL path as other routes. For example, since route groups don't affect URL structure,
(shop)/about/page.jswould both resolve to
/aboutand cause an error.
- If you use multiple root layouts without a top-level
layout.jsfile, your home
page.jsfile should be defined in one of the route groups, For example:
- Navigating across multiple root layouts will cause a full page load (as opposed to a client-side navigation). For example, navigating from
app/(marketing)/layout.jswill cause a full page load. This only applies to multiple root layouts.