Opting out of caching in NextJS

Introduction

Sometimes you want your web page to always show fresh data. Opting out of caching helps you do that by telling Next.js not to save the page content for later.

When showing live data like stock prices or sports scores that change often.

When displaying user-specific information that should not be shared or stored.

When debugging and you want to see changes immediately without cached versions.

When your page content depends on real-time events or external APIs that update frequently.

Syntax

NextJS

export const revalidate = 0;

Setting revalidate to 0 tells Next.js to never cache the page.

This is used in server components or page files to control caching behavior.

Examples

This page will never be cached and always fetch fresh data on every request.

NextJS

export const revalidate = 0;

export default function Page() {
  return <p>Always fresh content</p>;
}

This page caches content for 10 seconds before refreshing.

NextJS

export const revalidate = 10;

export default function Page() {
  return <p>Content updates every 10 seconds</p>;
}

Sample Program

This Next.js page shows the current time and never caches it, so it updates on every request.

NextJS

export const revalidate = 0;

export default function LiveTime() {
  const time = new Date().toLocaleTimeString();
  return <p>Current time: {time}</p>;
}

Important Notes

Opting out of caching can increase server load because pages are generated on every request.

Use this only when you really need fresh data to avoid slowing down your site.

Summary

Set revalidate = 0 to disable caching in Next.js pages.

This ensures the page content is always fresh and up-to-date.

Use it carefully to balance freshness and performance.

Practice

1. In Next.js, how do you disable caching for a page to always fetch fresh content?

easy

A. Set cache: false in next.config.js

B. Use getStaticProps without any options

C. Add no-cache header in _app.js

D. Set export const revalidate = 0; in the page file

Solution

1. Step 1: Understand Next.js caching control

   Next.js uses the revalidate export to control caching duration for static pages.

2. Step 2: Disable caching by setting revalidate to zero

   Setting revalidate = 0 tells Next.js to never cache and always fetch fresh data.

3. Final Answer:

   Set export const revalidate = 0; in the page file -> Option D

4. Quick Check:

   revalidate = 0 disables caching [OK]

Hint: Remember: revalidate = 0 means no caching [OK]

Common Mistakes:

• Confusing revalidate with cache settings in config
• Trying to disable caching via headers only
• Omitting the export keyword for revalidate

2. Which of the following is the correct syntax to disable caching in a Next.js page?

easy

A. export const revalidate = '0';

B. export const revalidate = 0;

C. const revalidate = 0;

D. export default revalidate = 0;

Solution

1. Step 1: Check correct export syntax

   In Next.js, caching control requires exporting a constant named revalidate.

2. Step 2: Use number zero without quotes

   The value must be a number 0, not a string, and must be exported properly.

3. Final Answer:

   export const revalidate = 0; -> Option B

4. Quick Check:

   Correct export with number zero disables caching [OK]

Hint: Use number 0 without quotes and export it [OK]

Common Mistakes:

• Using string '0' instead of number 0
• Not exporting the variable
• Using default export incorrectly

3. Given this Next.js page code snippet, what will be the caching behavior?

export const revalidate = 0;

export default function Page() {
  return <h1>Fresh Content</h1>;
}

medium

A. The page is never cached and always fetches fresh content

B. The page is cached and refreshed every 10 seconds

C. The page is cached indefinitely

D. The page throws a runtime error due to invalid revalidate value

Solution

1. Step 1: Identify the revalidate value

   The code sets revalidate = 0, which disables caching.

2. Step 2: Understand effect on page behavior

   With caching disabled, the page always fetches fresh content on each request.

3. Final Answer:

   The page is never cached and always fetches fresh content -> Option A

4. Quick Check:

   revalidate = 0 means no caching [OK]

Hint: revalidate 0 means always fresh, no cache [OK]

Common Mistakes:

• Assuming default caching applies
• Thinking 0 means cache forever
• Confusing with ISR default timing

4. You wrote this code to disable caching but the page still caches:

const revalidate = 0;

export default function Page() {
  return <div>No Cache</div>;
}

What is the error?

medium

A. Missing export keyword for revalidate

B. revalidate cannot be zero

C. Page component must be a class

D. Return statement syntax is incorrect

Solution

1. Step 1: Check revalidate declaration

   The variable revalidate must be exported to affect caching.

2. Step 2: Identify missing export

   Without export, Next.js ignores the variable and uses default caching.

3. Final Answer:

   Missing export keyword for revalidate -> Option A

4. Quick Check:

   revalidate must be exported to disable caching [OK]

Hint: Always export revalidate to control caching [OK]

Common Mistakes:

• Forgetting to export revalidate
• Thinking revalidate must be non-zero
• Confusing functional and class components

5. You want a Next.js page to always show fresh data but only disable caching for authenticated users. Which approach correctly opts out of caching only for them?

hard

A. Set revalidate = 0 inside getStaticProps conditionally

B. Set export const revalidate = 0; unconditionally in the page file

C. Use server-side rendering with export const dynamic = 'force-dynamic'; and check auth inside

D. Add Cache-Control: no-store header in _app.js for all requests

Solution

1. Step 1: Understand conditional caching needs

   Disabling caching only for authenticated users requires dynamic rendering based on request context.

2. Step 2: Use dynamic rendering with auth check

   Setting export const dynamic = 'force-dynamic'; forces server-side rendering, allowing auth checks per request.

3. Step 3: Why other options fail

   Set export const revalidate = 0; unconditionally in the page file disables caching for all users; Set revalidate = 0 inside getStaticProps conditionally is invalid because revalidate is static; Add Cache-Control: no-store header in _app.js for all requests affects all requests globally.

4. Final Answer:

   Use server-side rendering with export const dynamic = 'force-dynamic'; and check auth inside -> Option C

5. Quick Check:

   Dynamic rendering enables conditional caching [OK]

Hint: Use dynamic rendering to control caching per user [OK]

Common Mistakes:

• Trying to set revalidate conditionally inside getStaticProps
• Disabling caching globally instead of per user
• Misusing cache headers in _app.js