Next.js Docs Offline: A Single PDF for App Router and Pages Router

Table of Contents

• The Three PDF Strategy
• Why This Beats the Web Site
• What's Different in v15
• Suggested Reading Paths
  • Server Components-First (App Router)
  • SSR-First (Pages Router)
  • ISR-First (Migration)
• Bundling Vercel Docs Too
• A Real Use Case: Onboarding
• Generate Your Next.js PDF

The Three PDF Strategy

I generate three PDFs:

1. App Router only — for fresh learners and v15+ teams
2. Pages Router only — for legacy maintenance
3. Combined "what's different" — for migration projects

The flows:

Same from-url method we use for GitHub READMEs and every other doc bundle. Three minutes per PDF, plus generation time.

For most teams, you only need two of these. Pick based on your reality.

Why This Beats the Web Site

The Next.js docs site is genuinely good. It's also a SPA with toggles and there are practical issues:

• The toggle state isn't preserved across deep links
• Search results return both routers (you have to mentally filter)
• Scrolling resets when navigating between siblings
• The "Pages Router" warning banner is easy to miss when you're deep in a topic

A router-specific PDF removes all of that. There is no toggle. There is one mental model. You read.

What's Different in v15

Whatever Next.js version you're on, you'll want to know what changed.

When you generate the PDF, OfflineDocs pulls from nextjs.org/docs which is current. To pin to a version:

• Look at your package.json (next version)
• Look at archived docs URLs (Vercel keeps them around)
• Generate against that pinned URL

The Pages Router story has been mostly stable. The App Router story has changed every major (caching defaults, Server Actions, partial prerendering). Pin carefully.

This same pinning trick is one of the reasons offline reference PDFs matter for APIs — your code is on a version, your reference should be too.

Suggested Reading Paths

Server Components-First (App Router)

You're new to Next.js or starting a fresh project.

Reading order:

1. Getting Started
2. Routing fundamentals
3. Layouts and Pages
4. Server and Client Components (the conceptual core)
5. Data Fetching, Caching, and Revalidating
6. Server Actions
7. Streaming and Suspense
8. Authentication patterns
9. Deploying

You'll write better code by Friday.

SSR-First (Pages Router)

You're maintaining a Pages Router app or new to the framework but on a team that hasn't migrated.

Reading order:

1. Getting Started
2. Routing
3. Rendering (SSR, SSG, ISR)
4. API Routes
5. Data Fetching (getServerSideProps, getStaticProps)
6. Authentication
7. Deploying

The mental model is closer to "regular React + server" — easier to onboard from a CRA background.

ISR-First (Migration)

You're moving from Pages Router to App Router.

Reading order:

1. Migration guide
2. Server Components conceptual primer
3. Routing differences (special files: layout.tsx, page.tsx, loading.tsx, error.tsx)
4. Data fetching differences (no more getServerSideProps)
5. Caching defaults (this is the surprising part)
6. Server Actions (the new bit)

The migration guide alone is worth the PDF generation. Print it.

Bundling Vercel Docs Too

Most Next.js teams ship to Vercel. Vercel's deployment docs are technically separate but practically inseparable.

Generate https://vercel.com/docs/frameworks/nextjs as a sidecar PDF. Now you have:

• Next.js framework PDF
• Vercel-specific deployment PDF

Cleaner than mixing them.

If you don't ship to Vercel, skip this and you're done.

A Real Use Case: Onboarding

I helped a team onboard a contractor to a Next.js codebase last quarter.

The codebase was Pages Router. The contractor's last gig was App Router. Without context, every PR was going to be a small disaster.

We sent them the Pages Router PDF on Day 1. Day 3, they shipped their first PR. The PR worked.

That's the playbook for team training materials — give people one source of truth, not a docs maze.

Generate Your Next.js PDF

offlinedocs.ai/new → paste the router URL that matches your reality → generate.

Three minutes from "two routers, two mental models" to "one PDF, one focused weekend."

Pick a side. Read the docs. Ship the feature.