Why Intercepting routes (.) in NextJS? - Purpose & Use Cases

The Big Idea

Discover how to add dynamic UI parts effortlessly as users move through your app!

The Scenario

Imagine you want to add a special sidebar or modal that appears on some pages without changing the main page layout manually every time.

You try to update each page's code to include this extra UI, but it quickly becomes messy and repetitive.

The Problem

Manually adding UI elements to many pages means repeating code and risking inconsistencies.

It's hard to keep track of where to add or remove these elements, and updating them later is a headache.

The Solution

Intercepting routes lets you insert UI parts like sidebars or modals automatically when navigating to certain paths.

This keeps your code clean and lets you control layouts dynamically without touching every page.

Before vs After

✗ Before

if (page === '/dashboard') { renderSidebar(); renderPage(); } else { renderPage(); }

✓ After

<> <Sidebar /> <Page /> </>

What It Enables

You can create flexible, dynamic layouts that change smoothly as users navigate, improving user experience and developer productivity.

Real Life Example

On an e-commerce site, showing a shopping cart sidebar only on product pages without rewriting each product page component.

Key Takeaways

Manual UI updates across pages are repetitive and error-prone.

Intercepting routes lets you inject UI dynamically based on navigation.

This keeps your app clean, flexible, and easier to maintain.

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