---
title: "Discussion on \"App Router vs Pages Router: What Actually Changed in Next.js\" | Hashnode"
description: "Discussion on \"App Router vs Pages Router: What Actually Changed in Next.js\". Half the \"Next.js is confusing now\" complaints come from mixing App Router concepts into Pages Router thinking. Here's what actually changed, not just what's new."
url: "https://hashnode.com/posts/app-router-vs-pages-router-what-actually-changed-in-next-js/6a92edb4ec28ed1c41e0e193"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [App Router vs Pages Router: What Actually Changed in Next.js](https://jayesh-sojitra.hashnode.dev/app-router-vs-pages-router-what-actually-changed-in-next-js?utm_source=hashnode&utm_medium=feed)

Half the "Next.js is confusing now" complaints come from mixing App Router concepts into Pages Router thinking. Here's what actually changed, not just what's new.

Aug 29 · 3 min read · jayesh-sojitra.hashnode.dev  
Read the article

-   [#nextjs](https://hashnode.com/tag/nextjs)
-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#webdevelopment](https://hashnode.com/tag/webdevelopment)
-   [#frontend](https://hashnode.com/tag/frontend)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#codinglife](https://hashnode.com/tag/codinglife)
-   [#softwareengineering](https://hashnode.com/tag/softwareengineering)
-   [#frontenddevelopment](https://hashnode.com/tag/frontenddevelopment)
-   [#frontend-development](https://hashnode.com/tag/frontend-development)
-   [#developercommunity](https://hashnode.com/tag/developercommunity)

## Written by

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra)

@jayeshsojitra

  
[View profile](https://hashnode.com/@jayeshsojitra)

Jayesh Sojitra | AI &amp; Frontend

## Responses 1

Markdown supported · ⌘↵ to post

[Tarun Sharma](https://hashnode.com/@101beardo)

[Aug 30](https://hashnode.com/posts/app-router-vs-pages-router-what-actually-changed-in-next-js/6a92edb4ec28ed1c41e0e193/comment/6a94320289b81ef5057a192d)

Good breakdown of the mental model. Two things worth adding for anyone migrating now. The fetch caching default flipped in Next 15, fetch is no longer cached by default so you have to opt into force-cache explicitly, which trips up people following older tutorials that assume it caches. And use client marks a boundary, not a whole subtree. You can still render server components inside a client component by passing them as children or props, so you rarely need to push the directive as far down the tree as people assume.
