This is a quick, version-specific overview of the Next.js 14 App Router. In this routing model, folders under the app directory represent URL segments, while special files define pages, layouts, loading states, and other route behavior.
Pages, layouts, and route structure
A route becomes available when its segment contains a page file. Layouts can provide shared UI around nested pages, and route groups can organize code without changing the public URL. Static and dynamic route segments support different content patterns; choose a structure that matches how the application is navigated.
Server and Client Components
In the App Router, components are Server Components by default. Use a Client Component when the UI needs state, event handlers, browser-only APIs, or other client-side behavior, and mark its entry point with "use client". Keeping client boundaries focused can limit the amount of code sent to the browser.
This page summarizes Next.js 14, not every current feature. The supplied Next.js 14 docs and release notes describe that version; current documentation may differ. Check the documentation that matches your installed version before copying an API or migration pattern.