Suggest an editImprove this articleRefine the answer for “What are route groups?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Route Groups** in Next.js are a way to **logically group routes** without affecting the URL. They let you bring order to the `app/` structure without changing page addresses. **Key point:** a route group is a folder in parentheses that exists only for the developer, not for the user.Shown above the full answer for quick recall.Answer (EN)Image**Route Groups** in Next.js are a way to **logically group routes** without affecting the URL. They let you bring order to the `app/` structure without changing page addresses. In other words: > a route group is a folder in parentheses that exists only for the developer, not for the user. --- ## What route groups look like A route group is a folder whose name is in parentheses: ```txt app/ ├─ (auth)/ │ ├─ login/ │ │ └─ page.tsx → /login │ └─ register/ │ └─ page.tsx → /register └─ (marketing)/ └─ page.tsx → / ``` The `(auth)` folder **never appears in the URL**. --- ## Why route groups are needed ### 1. Logical organization of the project You can group routes by meaning: - authentication - marketing - admin panel - the public part At the same time, URLs stay clean and understandable. --- ## 2. Different layouts for the same URL levels Route groups are often used to: - have different layouts - for pages at the same URL level - but with a different UI structure Example: ```txt app/ ├─ (public)/layout.tsx ├─ (admin)/layout.tsx ``` Both groups can contain a `/` page, but with a different layout (via nested segments). --- ## 3. Isolating layouts and logic Each route group can have its own: - layout - loading - error - middleware logic - providers This is convenient when: - different parts of the site "live their own life" - you don't want to mix code --- ## 4. Clean and predictable URLs Route groups let you: - avoid adding technical segments to the address - avoid creating `/auth/login` when you want `/login` - keep a nice link structure The URL is designed for the user, the folders are for the developer. --- ## Important features - `(group)` **never appears in the URL** - `layout.tsx` can be used inside a group - groups do not affect URL nesting - can be combined with nested layouts --- ## An example with layout ```txt app/ ├─ (auth)/ │ ├─ layout.tsx │ └─ login/ │ └─ page.tsx → /login ├─ (main)/ │ ├─ layout.tsx │ └─ page.tsx → / ``` Here: - `/login` uses the `auth` layout - `/` uses the `main` layout - URLs stay clean --- ### Summary Route groups are needed to: - logically organize routes - apply different layouts - keep the URL uncluttered - isolate logic and providers In short: **route groups are an architectural tool for order in the project, not for user navigation.**For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.