Bundling All of TanStack Into One PDF Reference

TanStack's docs are some of the prettiest in the React ecosystem.
They're also a single-page app, which means:
- Ctrl+F finds you exactly nothing once you're offline
- Your browser's "Save as PDF" gives you a 3-page PDF where 90% of the content is missing
- Every navigation is a JS route change, not a real page
Beautiful online. Useless offline.
Here's the workflow that turns the entire TanStack stack into one searchable PDF.
Table of Contents
- The SPA-Docs Problem
- The Five TanStack Products
- The Workflow
- Why TanStack Devs Especially Need Offline Copies
- A TanStack Annotation Workflow
- Combined or Separate?
- What About TanStack Form/Table V9?
- Generate Your TanStack PDF
The SPA-Docs Problem
When docs are a SPA, your browser doesn't really have a page to print.
The HTML file you load is a shell. The actual content gets rendered by JavaScript on navigation. Print-to-PDF captures the shell plus whatever's currently rendered. Everything else is gone.
This is true for TanStack. It's true for a lot of modern docs. The team made a great UX choice for online reading and an unintentionally hostile choice for offline reading.
OfflineDocs handles SPAs by rendering the pages, walking the route tree, and bundling everything into a real PDF. You don't have to know it's a SPA. You just paste the URL.

The Five TanStack Products
If you're a TanStack user, you're probably using more than one of these:
| Product | What it does | Docs URL |
|---|---|---|
| Router | Type-safe routing | tanstack.com/router |
| Query | Server state | tanstack.com/query |
| Table | Headless tables | tanstack.com/table |
| Form | Headless forms | tanstack.com/form |
| Start | Full-stack framework | tanstack.com/start |
You can bundle them all into one PDF. Or five separate PDFs. Or both.
I do both. The combined PDF lives on my tablet for reading. The per-product PDFs live on my desktop for "I just need the Query API right now."

The Workflow
Five paste-and-generate cycles, ~10 minutes total:
- Paste
https://tanstack.com/router/latest→ Router PDF - Paste
https://tanstack.com/query/latest→ Query PDF - Paste
https://tanstack.com/table/latest→ Table PDF - Paste
https://tanstack.com/form/latest→ Form PDF - Paste
https://tanstack.com/start/latest→ Start PDF
You can also do "the whole TanStack" in one go — paste https://tanstack.com/ and pick all the products. That gives you one combined PDF.
The from-url source method handles the SPA rendering. Same as the GitHub README to PDF flow, just pointed at a different kind of site.

Why TanStack Devs Especially Need Offline Copies
Three reasons:
Five products = five mental models. Router thinks differently than Query. Form has its own conventions. Sitting with the docs, not fighting your browser, helps.
Type signatures matter. TanStack libraries are deeply typed. The docs explain why certain types look the way they do. You want to read those explanations carefully, not skim them while three other tabs ping.
The releases ship fast. Pinning a PDF to the version your app is on is genuinely useful. When TanStack Router ships a major, your PDF still describes the version your prod code is on.

A TanStack Annotation Workflow
I read TanStack docs with two passes:
Pass 1: Concepts. I highlight the "why this exists" sections. TanStack libraries each solve a specific problem. Those problem statements are usually buried in the intro chapters and they're worth re-reading.
Pass 2: APIs. I sticky-tab the methods I keep needing. useQuery, flexRender, createRouter. Quick lookup beats searching docs.
After a month, my TanStack PDFs look like a chef's recipe books. Stained, dog-eared, marked. That's the whole point.
For a deeper take on annotation workflows, there's a guide on print and reading systems.

Combined or Separate?
| Format | When |
|---|---|
| Combined "all of TanStack" PDF | Reading on a flight, onboarding, learning a new product |
| Per-product PDFs | Daily reference while shipping a feature |
| Both | Most TanStack devs |
The combined PDF is ~600 pages. Per-product PDFs are ~80-150 each.
Reading the combined PDF cover-to-cover is genuinely worth it once. After that, you'll mostly use the per-product ones.
What About TanStack Form/Table V9?
TanStack libraries occasionally ship breaking majors.
Pin the version in your URL when you generate: tanstack.com/table/v8 vs tanstack.com/table/latest.
Your team is on v8? Generate a v8 PDF. When you migrate to v9, generate a v9 PDF and read the diff intentionally.
This avoids the "the docs say one thing but my code does another" confusion that hits whenever a major lands.
Generate Your TanStack PDF
offlinedocs.ai/new → paste https://tanstack.com/router/latest (or any TanStack URL) → generate.
Repeat for the other products if you want per-product PDFs.
Or paste https://tanstack.com/ for the everything-bundle.
Ten minutes from now, you'll have a TanStack reference that doesn't need WiFi to find what you need.
Ready to Get Started?
Start creating your Offline Docs Now! Reduce screen time and save your eyes.