Intercepting routes (.) in NextJS

Introduction

Intercepting routes lets you show extra content or UI without leaving the current page. It helps keep the user experience smooth and fast.

You want to open a sidebar or modal while keeping the main page visible.

You need to show a preview or details panel without a full page reload.

You want to keep some parts of the page stable while changing others.

You want to handle nested navigation inside a section without leaving it.

Syntax

NextJS

app/(group)/page.tsx
app/(group)/@modal/page.tsx

// Use parentheses for route groups
// Use @ prefix for intercepting routes
// Link to intercepting route with dot notation: href="/group.(modal)"

Parentheses () create route groups that don't add to the URL path.

The @ prefix marks a folder as an intercepting route.

Examples

This example shows a dashboard page with a sidebar that opens as an intercepting route.

NextJS

app/dashboard/page.tsx
app/dashboard/@sidebar/page.tsx

// Link to open sidebar: href="/dashboard.(sidebar)"

This example shows a shop page with a modal that appears without leaving the shop page.

NextJS

app/shop/page.tsx
app/shop/@modal/page.tsx

// Link to open modal: href="/shop.(modal)"

Sample Program

This example shows a dashboard page with a link that opens a sidebar as an intercepting route. The sidebar content appears next to the main dashboard content without a full page reload.

NextJS

import Link from 'next/link';

export default function DashboardPage() {
  return (
    <main>
      <h1>Dashboard</h1>
      <nav>
        <Link href="/dashboard.(sidebar)">Open Sidebar</Link>
      </nav>
    </main>
  );
}

// In app/dashboard/@sidebar/page.tsx
export default function Sidebar() {
  return (
    <aside aria-label="Sidebar">
      <h2>Sidebar Content</h2>
      <p>This content appears alongside the dashboard without leaving it.</p>
    </aside>
  );
}

Important Notes

Intercepting routes keep the URL clean and let you show extra UI parts.

Use semantic HTML and ARIA labels for accessibility in intercepting UI like sidebars or modals.

Test in browser DevTools to see how the URL and UI update without full reloads.

Summary

Intercepting routes let you add UI parts without leaving the current page.

Use parentheses and @ folders to set up intercepting routes in Next.js App Router.

They improve user experience by avoiding full page reloads and keeping context.

Practice

1. What is the main purpose of intercepting routes in Next.js App Router?

easy

A. To force server-side rendering on every route

B. To reload the entire page on every navigation

C. To disable client-side navigation

D. To add UI parts without leaving the current page

Solution

1. Step 1: Understand intercepting routes concept

   Intercepting routes allow adding UI parts while staying on the same page, avoiding full reloads.

2. Step 2: Compare options with concept

   Options suggesting page reloads, disabling navigation, or forcing server-side rendering contradict the idea of smooth UI updates without full reloads.

3. Final Answer:

   To add UI parts without leaving the current page -> Option D

4. Quick Check:

   Intercepting routes = add UI parts without leaving page [OK]

Hint: Intercepting routes keep you on the page while adding UI [OK]

Common Mistakes:

• Thinking intercepting routes reload the whole page
• Confusing intercepting routes with disabling navigation
• Assuming intercepting routes force server rendering

2. Which folder name syntax is used to create an intercepting route in Next.js App Router?

easy

A. @modal

B. modal

C. (modal)

D. [modal]

Solution

1. Step 1: Recall folder naming for intercepting routes

   Intercepting routes use parentheses around folder names, like (modal), to mark them as intercepting.

2. Step 2: Evaluate options

   (modal) uses parentheses correctly. @modal uses @ for parallel routes, modal omits parentheses for regular routes, and [modal] uses square brackets for dynamic routes.

3. Final Answer:

   (modal) -> Option C

4. Quick Check:

   Intercepting route folder = parentheses [OK]

Hint: Intercepting routes use (folderName) syntax [OK]

Common Mistakes:

• Using square brackets instead of parentheses
• Omitting parentheses for intercepting routes
• Confusing @ folders with intercepting route folders

3. Given this folder structure in Next.js App Router:
app/(modal)/page.tsx
What happens when you navigate to a route inside (modal)?

medium

A. The modal UI appears without leaving the current page

B. The entire page reloads and shows only the modal content

C. Navigation fails with a 404 error

D. The modal opens in a new browser tab

Solution

1. Step 1: Understand intercepting route behavior

   Routes inside (modal) folders add UI parts like modals without leaving the current page.

2. Step 2: Analyze navigation effect

   Navigation triggers modal UI overlay, not a full page reload or error.

3. Final Answer:

   The modal UI appears without leaving the current page -> Option A

4. Quick Check:

   Navigation in (modal) = modal UI without reload [OK]

Hint: Routes in (modal) show UI without page reload [OK]

Common Mistakes:

• Expecting full page reload on modal route
• Thinking navigation causes errors
• Assuming modal opens in new tab

4. You wrote this intercepting route folder: app/@(sidebar)/page.tsx. Why does it cause a build error?

medium

A. Parentheses cannot be combined with @ in folder names

B. The folder name must be all lowercase

C. You need to add a layout.tsx file inside the folder

D. The file extension should be .jsx, not .tsx

Solution

1. Step 1: Check folder naming rules for intercepting routes

   Parentheses indicate intercepting routes; @ folders are separate special folders. Combining them is invalid syntax.

2. Step 2: Identify cause of build error

   Using @(sidebar) mixes two folder naming conventions, causing build failure.

3. Final Answer:

   Parentheses cannot be combined with @ in folder names -> Option A

4. Quick Check:

   Invalid folder name combining ( ) and @ causes error [OK]

Hint: Don't mix ( ) and @ in folder names [OK]

Common Mistakes:

• Thinking lowercase folder name fixes error
• Assuming missing layout.tsx causes build error
• Confusing file extension with folder naming

5. You want to show a sidebar UI on some pages without leaving the current page. Which folder structure correctly implements this intercepting route in Next.js App Router?

hard

A. app/(sidebar)/page.tsx without layout.tsx

B. app/(sidebar)/page.tsx with a layout.tsx inside (sidebar) wrapping children

C. app/@sidebar/page.tsx with page.tsx only

D. app/sidebar/page.tsx with a layout.tsx inside sidebar wrapping children

Solution

1. Step 1: Identify correct intercepting route folder

   Using parentheses (sidebar) marks it as an intercepting route folder.

2. Step 2: Confirm layout usage for UI wrapping

   Adding layout.tsx inside (sidebar) allows wrapping children with sidebar UI, enabling partial UI updates.

3. Step 3: Evaluate other options

   app/sidebar/page.tsx with a layout.tsx inside sidebar wrapping children lacks parentheses, so it's a normal route. app/@sidebar/page.tsx with page.tsx only uses @ which is for special folders, not intercepting routes. app/(sidebar)/page.tsx without layout.tsx misses layout.tsx, so sidebar UI won't wrap children properly.

4. Final Answer:

   app/(sidebar)/page.tsx with a layout.tsx inside (sidebar) wrapping children -> Option B

5. Quick Check:

   Intercepting route with layout wraps UI correctly [OK]

Hint: Use (folder) plus layout.tsx to wrap UI in intercepting routes [OK]

Common Mistakes:

• Omitting layout.tsx inside intercepting route folder
• Using normal folder instead of (folder) for intercepting route
• Confusing @ folders with intercepting route folders