Migrate from chatpdf to claude.
1 documentation-derived translation pattern — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
ChatPDF's folder of PDFs you chat against maps to a Claude Project, where files uploaded to the project's knowledge are shared across every conversation in that project. To migrate: create a Project in Claude, upload the same PDFs into the project's knowledge (its Files section), add a short instruction describing how to answer, then start chats that draw on those documents. For ad-hoc single-document Q&A you can also just attach a PDF directly to a normal Claude chat instead of building a project. Claude additionally reasons, drafts, and runs code on the documents, going beyond ChatPDF's read-and-cite scope.
- Warning: Basic Projects exist on free Claude accounts, but the expanded project-knowledge behaviour that retrieves across many uploaded files (RAG) is limited to paid plans (Pro, Max, Team, Enterprise); ChatPDF offers a free tier with no account, so getting parity on large knowledge bases assumes the user pays for Claude.
- Warning: Claude project-knowledge files are capped at 30 MB each, and a project's knowledge is surfaced via retrieval (Claude's help docs describe roughly up-to-10x context expansion) rather than loading every page verbatim, whereas ChatPDF Plus handles single PDFs up to 2,000 pages / 32 MB; very large document sets may exceed what the project retrieves at once.
- Warning: Claude does not surface ChatPDF-style explicit per-answer page citations by default; it cites uploaded files conversationally, so verifying an exact source page takes more manual checking.