template.tsx in Next.js — Resetting Client State with Unique Keys

The template.tsx file in Next.js behaves like a layout but remounts on every navigation due to its unique key. Unlike layouts that persist across routes, templates reset the state of child Client Components, re-run effects like useEffect, and show Suspense fallbacks on every route change. This makes them ideal for input resets, effect resynchronization, and dynamic UI transitions.

template.tsxClient Component resetnavigation remountunique key

~2 دقیقه مطالعه · آخرین به‌روزرسانی ۷ آبان ۱۴۰۴

1. What Is template.tsx?


template.tsx is a special file in Next.js that wraps a layout or page, similar to layout.tsx. However, unlike layouts, templates remount on every navigation due to being assigned a unique key.


2. When to Use a Template


  • To reset the state of Client Components (e.g. input fields)
  • To re-run useEffect on navigation
  • To show Suspense fallbacks on every route change

3. Defining a Template


Create a template.tsx file and export a default React component that accepts a children prop:

// app/template.tsx
export default function Template({ children }: { children: React.ReactNode }) {
  return <div>{children}</div>
}

4. Where Templates Render


Templates are rendered between the layout and its children, and are automatically assigned a unique key:

<Layout>
  <Template key={routeParam}>
    {children}
  </Template>
</Layout>

5. Template Behavior on Navigation


  • Templates are Server Components by default
  • They remount when their segment or dynamic params change
  • They do not remount on search param changes
  • Client Components inside reset their state
  • useEffect re-runs on remount
  • DOM inside the template is fully recreated

6. Navigation Examples


Starting at /

<RootLayout>
  <Template key="/">
    <Page />
  </Template>
</RootLayout>

Navigating to /about

<RootLayout>
  <Template key="/about">
    <AboutPage />
  </Template>
</RootLayout>

Navigating to /blog

<RootLayout>
  <Template key="/blog">
    <Template key="/blog">
      <BlogIndexPage />
    </Template>
  </Template>
</RootLayout>

Navigating to /blog/first-post

<RootLayout>
  <Template key="/blog">
    <Template key="/blog/first-post">
      <BlogPostPage slug="first-post" />
    </Template>
  </Template>
</RootLayout>

Navigating to /blog/second-post

<RootLayout>
  <Template key="/blog">
    <Template key="/blog/second-post">
      <BlogPostPage slug="second-post" />
    </Template>
  </Template>
</RootLayout>

Conclusion


template.tsx in Next.js is a powerful tool for controlling component behavior during navigation. By remounting with a unique key, it resets Client Component state, re-runs effects, and ensures a fresh UI experience on every route change.


نوشته و پژوهش‌شده توسط دکتر شاهین صیامی

مقالات مرتبط

Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

ادامه

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

ادامه

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

ادامه

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

ادامه

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

ادامه

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

ادامه