{"items":[{"id":"290b4ff6-095a-4452-a61c-8331028af43c","title":"NextJS App Router Rendering Strategies: CSR, SSR, SSG, ISR & PPR","slug":"nextjs-app-router-rendering-strategies-csr-ssr-ssg-isr-ppr","contentHtml":"

This post is synced from my website using webhooks.

1. Full Page Client Side Rendering (CSR)

This one is very similar to how we used to build classic React apps before frameworks like NextJS.

When you use full Client Side Rendering, Next.js sends an almost empty HTML page. Then the browser runs JavaScript, fetches the data, and builds the page on the client. So the browser does all the work. The server just gives it the basic tools.

You might choose CSR when:

You don’t need SEO (for example, in dashboards or admin panels),
The page is very interactive,
The content is personalized for the logged-in user.

\"use client\";\n\nimport { Post } from \"@/lib/types\";\nimport { useEffect, useState } from \"react\";\n\nexport default function Page() {\n  const [post, setPost] = useState<Post | null>(null);\n\n  useEffect(() => {\n    fetch(\"https://jsonplaceholder.typicode.com/posts/1\")\n      .then((res) => res.json())\n      .then(setPost);\n  }, []);\n\n  if (!post) return <div>Loading…</div>;\n\n  return (\n      <div className=\"flex w-150 flex-col gap-y-5\">\n        <h2 className=\"text-2xl font-bold\">{post.title}</h2>\n        <p>{post.body}</p>\n      </div>\n  );\n}\n

One downside of CSR is that the user might see a loading spinner for a while, especially on slower networks. Also, SEO bots usually can’t read JavaScript, so these pages don’t work well for search engines.

Maybe your page is very heavy has a lots of data manipulation, re-renders, and first-build. It can be good to do it in a server.

But for dynamic apps with lots of interaction, CSR is a good choice. And of course, you can always mix CSR with other strategies.

2. Server-Side Rendering (SSR)

With SSR, Next.js runs your code on the server and sends back a fully rendered HTML page. It fetches data on every request and includes everything in the HTML, including dynamic metadata.

This is useful for SEO and when your data changes often.

import { Post } from \"@/lib/types\";\n\nexport default async function Page() {\n  const res = await fetch(\"https://jsonplaceholder.typicode.com/posts\", { cache: \"no-store\" });\n  const items = ((await res.json()) as Post[]).slice(0, 10);\n  return (\n      <ul className=\"list-decimal\">\n        {items.map((item) => (\n          <li key={item.id}>{item.title}</li>\n        ))}\n      </ul>\n  );\n}\n

Here, the { cache: 'no-store' } tells Next.js to fetch fresh data every time. This keeps the content up to date.

Just a quick tip: when using Server Components like this, you can't use hooks like useState, useEffect, or anything that depends on the browser (like accessing window or navigator). If you need those, you’ll need to use a Client Component. I’ll write more about workarounds for that in a future post, so feel free to subscribe if you’re interested.

3. SSR + CSR Components

Many pages need both good SEO and some interactive features. For example, maybe you want to show a blog post (static content) but also allow users to like it (interactive).

In Next.js, you can mix Server Components (for data fetching and layout) with Client Components (for interactivity). This is a really powerful combo.

import { LikeButton } from \"@/components/LikeButton\";\nimport { Post } from \"@/lib/types\";\n\nexport default async function Page() {\n  const res = await fetch(\"https://jsonplaceholder.typicode.com/posts/1\", { cache: \"force-cache\" });\n  let post = (await res.json()) satisfies Post;\n  post = { ...post, likes: 0 };\n  \n  return (\n      <article className=\"flex flex-col items-center\">\n        <h1>{post.title}</h1>\n        <LikeButton initialLikes={post.likes} />\n      </article>\n  );\n}\n

// LikeButton.tsx (Client Component)\n'use client' // Don't forget to add\nimport { useState } from 'react'\n\nexport default function LikeButton({ initialLikes }) {\n  const [likes, setLikes] = useState(initialLikes)\n\n  return (\n    <button onClick={() => setLikes(likes + 1)}>\n      ❤️ {likes}\n    </button>\n  )\n}\n

The server renders the page with fresh data, and the client handles the like button’s interactivity.

4. Static Site Generation (SSG)

If your page doesn’t change often, and doesn’t use dynamic data — go with SSG.

Think of simple pages like Home Pages , About pages, Pricing tables, Static blog content.

Next.js will generate these pages at build time and serve them as pure HTML. This makes them super fast and great for SEO.

It also means zero* server cost, the server just returns the same file again and again, like a CDN.

// No fetch, no revalidate, no dynamic params or searchParams. Just plain static content.\nexport default function Page() {\n  return <div>This is a fully static page</div>\n}\n

But what if you still need to fetch some data, like a list of features or testimonials, but that data rarely changes?

You can use cache: \"force-cache\" in a Server Component. This tells Next.js to fetch the data at build time and reuse the result on every request — just like classic SSG.

import { Post } from \"@/lib/types\";\n\n// A static page that fetches data at build time\nexport default async function Page() {\n  const res = await fetch(\"https://jsonplaceholder.typicode.com/posts\", { cache: \"force-cache\" });\n\n  const data = ((await res.json()) as Post[]).slice(0, 10);\n\n  return (\n      <ul>\n        {data.map((post) => (\n          <li key={post.id}>{post.title}</li>\n        ))}\n      </ul>\n  );\n}\n

✅ This fetch only runs once during the build.
\n✅ Great for rarely-changing content.
\n❌ You need to rebuild your app to see updated data.

If you want the same fast speed but want to update the content automatically after a while, check out ISR below 👇

5. Incremental Static Regeneration (ISR)

ISR is one of the best features of Next.js. It gives you the speed of static pages and the ability to update them without rebuilding your whole site.

Normally, if you use SSG (Static Site Generation), your page is built once when you deploy. If something changes in your data, you'd have to rebuild and redeploy your whole app to see the updates.

Here’s how it works:

The page is built and cached at build time (just like SSG).
You can set a revalidate time, like every 60 seconds.
While the cached version is served to users, Next.js checks if it’s time to update.
If it's time, the next user who visits the page will trigger a rebuild in the background.
That user still sees the old page, but the next one gets the updated version.

So, the page is regenerated quietly while your site stays online and fast.

import { Post } from \"@/lib/types\";\n\nexport default async function Page() {\n  const res = await fetch(\"https://jsonplaceholder.typicode.com/posts\", {\n    next: { revalidate: 60 },\n  });\n\n  const data = ((await res.json()) as Post[]).slice(0, 10);\n\n  return (\n      <ul>\n        {data.map((post) => (\n          <li key={post.id}>{post.title}</li>\n        ))}\n      </ul>\n  );\n}\n

When to use ISR

Pages that change sometimes (like product listings, articles, events)
You want the performance of static and the freshness of dynamic
Great when rebuilding the site every time is too expensive

ISR is what makes scalable content possible, especially if you have hundreds or thousands of pages. You don’t need to rebuild the whole site. Just let Next.js handle it automatically in the background.

6. Partial Prerendering (PPR)

This one’s still experimental, but super interesting.

Imagine your page loads instantly with static HTML for the layout, header, footer, product info, but the personalized parts (like a shopping cart or profile info) or \"how many product left?\" sections can be loaded afterwards, with a loading spinner.

You can do that with PPR, using <Suspense>, Client Components, and React streaming.

The static parts load instantly
The dynamic part (ProductList) loads when ready
Great for performance + personalization

// app/ppr-example/page.tsx\nimport { Suspense } from \"react\";\n\nexport const experimental_ppr = true;\n\nexport default function Page() {\n  return (\n    <>\n      <header>\n        <h1>This will be prerendered</h1>\n      </header>\n      <main>\n        <Suspense fallback={<div>Loading...</div>}>\n          <ProductList />\n        </Suspense>\n      </main>\n    </>\n  );\n}\n\n// components/ProductList.tsx\nimport { Post } from \"@/lib/types\";\nexport async function ProductList() {\n  const res = await fetch(\"https://jsonplaceholder.typicode.com/posts\", {\n    next: { revalidate: 60 },\n  });\n\n  const data = ((await res.json()) as Post[]).slice(0, 10);\n\n  return (\n    <ul>\n      {data.map((post) => (\n        <li key={post.id}>{post.title}</li>\n      ))}\n    </ul>\n  );\n}\n

$\"\"$

","contentJson":null,"remote":false,"status":"published","publishAt":null,"language":"en","summary":"In this post, I walk you through all the main rendering strategies in the Next.js App Router: CSR, SSR, SSG, ISR, and even the experimental PPR. We will look at when to use each one, with real examples and simple code you can try yourself. I will also share my experiences and best practices along the way.","coverUrl":"https://cdn.sanity.io/images/jl0ycvey/production/5b268f6f1491730a501f80932674bfdc716c7f7e-1200x630.svg","bannerUrl":"https://cdn.sanity.io/images/jl0ycvey/production/5b268f6f1491730a501f80932674bfdc716c7f7e-1200x630.svg","coverCredit":null,"createdAt":"2026-08-03T13:29:01.282Z","updatedAt":"2026-08-11T09:18:02.720Z","author":{"id":"0ebaf234-e115-4fe4-b486-863fa81ed026","username":"yusifaliyevpro","displayName":"Yusif Aliyev","avatarUrl":"/api/uploads/5f821688-b50d-4845-a900-53de5c68a64d.webp","remote":false},"tags":[{"slug":"approuter","name":"approuter"},{"slug":"csr","name":"csr"},{"slug":"nextjs","name":"nextjs"},{"slug":"renderingstrategies","name":"renderingstrategies"},{"slug":"ssr","name":"ssr"}],"likeCount":2,"liked":false,"commentCount":0,"recommendCount":0,"recommended":false,"recommendedBy":null}],"nextCursor":null}