Claude vs ChatGPT for PDFs: The Context Window Is the Wrong Answer (2026)

You have a 90-page contract, report, or policy PDF and one question you actually need answered. Every ranking page on this query hands you a context-window spec sheet and calls it a decision.

That is a hardware answer to a workflow question.

Three things decide this, and none of them is the size of the context window: where you put the file, whether the PDF is a scan, and whether you are summarizing or judging.

Chris Alarcon’s rule for this one: the bigger window does not read your document, and when being wrong is expensive, run both models against each other before you trust either one.

One note on the window itself, since every other page leads with it. Anthropic states that Claude Sonnet 5 supports a 1M token context window on all paid plans, that Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6 support 500K, and that outside of these models the window is 200K, with no free-tier number published anywhere. OpenAI does not clearly publish context window sizes for its consumer tiers at all.

So the “bigger window” argument compares a published number to an unpublished one. That is one vendor being more transparent than the other, which is a real finding, just not the one those pages think they are making.

What will actually break your afternoon is file size caps, image handling, and retrieval behavior. All three are documented. None appear on that SERP.

Where You Put the File Changes the Rules More Than Which Brand You Picked

The most useful table for this job is not Claude versus ChatGPT. It is chat versus project knowledge, on both platforms.

	Claude chat	Claude project files	ChatGPT chat	ChatGPT project knowledge
File size cap	500MB per file	30MB per file	512MB per file, 2M tokens	512MB per file, 2M tokens
File count	Up to 20 per chat	Unlimited, must fit context window	80 files per 3 hours (Free: 3/day)	10 uploaded at a time
What gets read from a PDF	Text and visuals under 100 pages	Text extraction only, except multimodal PDFs	Text and visuals (Enterprise: visual retrieval)	Text only, images discarded
When it flips to search	Automatically at context limit (RAG)	Automatically at context limit (RAG)	Not documented for consumer tiers	Not documented for consumer tiers
Storage	Not published per-user	Not published per-user	25GB per user, 100GB per org	25GB per user, 100GB per org

Sources: Anthropic’s upload documentation, OpenAI’s file uploads FAQ, and OpenAI’s Projects documentation.

Read the first row again. That is the row this whole post exists for.

The Popular Advice About Big Files Is Backwards on File Size

The standard advice, including the top-voted Reddit answers on this, is that large files belong in the knowledge base rather than in chat. On total corpus volume, that is correct. On a single big file, Anthropic’s own numbers say it is exactly backwards.

Anthropic documents chat uploads at 500MB per file, up to 20 files per chat. The same page documents project files at 30MB per file.

That is a 16x gap running the opposite direction from the advice.

• One enormous PDF, used once: drop it straight into a chat. The project will reject it long before the chat does.
• Forty documents you will query for months: project knowledge. Unlimited file count there, and the chat’s 20-file ceiling becomes the binding constraint instead.

“Knowledge base for big stuff” sounds obviously right. It is right about how many, and wrong about how big.

There is a second cost the size cap hides. Anthropic specifies project files as “Text extraction only (except for multimodal PDFs).” Your chart-heavy quarterly report can lose its charts by being filed in the place you assumed was more thorough.

The Scanned PDF Trap Is the Most Expensive Surprise in This Comparison

If your PDF is a scan or a photo of a document, this section decides your answer by itself.

OpenAI’s file uploads FAQ states it directly: “ChatGPT Enterprise supports Visual Retrieval for PDF files… All other plans and document files only support text-based retrieval. This means that ChatGPT will extract digital text from the file and discard any images.”

Their dedicated visual retrieval page repeats it: “This capability is available only to ChatGPT Enterprise customers. It is not supported for ChatGPT Free, Pro, Team, or Edu accounts.”

A scanned document has no digital text. Extract the digital text, discard the images, and you are left with nothing.

Claude’s documented behavior on the same input: “Claude models can analyze both text and visual elements (like images, charts, and graphics) in PDFs that are under 100 pages.” No tier condition attached to that sentence.

Neither vendor uses the word OCR in consumer documentation, so nobody should claim either product does or does not perform it. What is documented is what gets read and what gets discarded, and that is enough to make the call.

But Claude’s advantage has an undocumented middle. Anthropic’s other threshold is that PDFs over 1000 pages get text only, and between 100 and 1000 pages the documentation says nothing. That band covers most real contracts, annual reports, and policy manuals, which is to say it covers the exact document that brought you here. Any page that tells you what happens in it is making it up.

So test your own file: ask Claude to describe a specific chart or signature block on a specific page. If it can, visuals are being read. If it cannot, you are getting text extraction and should plan accordingly.

The nested version of this trap that will genuinely catch you

Same PDF, same ChatGPT account, two different behaviors depending on how it got there.

OpenAI documents it: “PDFs uploaded as GPT Knowledge or Project Files are processed using text-only retrieval. PDFs uploaded by users during interactions with a published GPT or within a Project conversation are processed using visual retrieval.”

So filing a PDF into your project’s knowledge strips its images. Dragging the identical file into that project’s chat window does not. The tidy habit is the one that costs you the images, which is worth knowing before you commit a workflow to it. Same argument as Claude Projects vs Custom GPTs.

Claude has its own version of this asymmetry, in the project-files line quoted above. On both platforms, the knowledge base is the lossier destination for anything visual.

Why Claude “Forgot” Something That Was Definitely in Your Project File

The most common complaint about long-document work has a documented mechanical answer.

Anthropic explains that when retrieval augmented generation is enabled, “Claude uses a project knowledge search tool to retrieve relevant information… Instead of loading all project content into memory at once, Claude intelligently searches and retrieves only the most relevant information needed to answer your questions.”

The trigger is the part that matters:

RAG automatically activates when your project approaches or exceeds the context window limits. You’ll see a visual indicator.

It reverses if the project drops back below the threshold, and Anthropic says it can expand capacity by up to 10x.

At your desk: below the threshold, everything you filed is loaded. Above it, Claude searches instead of reading, and only finds what its search judged relevant to your phrasing.

Same project. Two behaviors. The switch happens on its own.

That is why the clause you know is in there comes back as “I don’t see that in the documents.” Not a hallucination, a retrieval miss. Ask again using the document’s specific language rather than a paraphrase.

One caveat. Anthropic’s RAG page says “RAG for projects is available for all Claude plans (free, Pro, Max, Team, and Enterprise),” while their Projects article describes enhanced project knowledge with RAG as paid-plans-only. Two Anthropic pages, same period, opposite claims. Check your own account for the indicator rather than trusting either page.

Summarize This and Find the Clause Are Two Different Jobs With Two Different Risk Levels

Every page on this query treats “work with a PDF” as one task. It is two, and only one can hurt you.

Summarize and orient is low stakes. What is this report about, what are the main findings, what do I need before the meeting. If the model softens a nuance, you find out in the meeting and correct it. Both tools are fine here.

Find the clause and judge it is not. What is the termination notice period, does this indemnity cap cover third-party claims, does this policy apply to me. Being wrong has a dollar figure attached.

That second job is where Chris Alarcon’s trust-but-verify rule from his Claude vs ChatGPT for Excel breakdown applies without exception: the fully autonomous agent does not exist yet. Run the AI in parallel with your manual process until its answers match yours, and keep QA-ing after they do. His cross-check is the specific move for documents: if you are using ChatGPT, paste the output into Claude and ask it to QA it. Then reverse it. AI is already smarter than us at plenty of things and it can still be wrong.

For a contract, that means a concrete loop:

1. Ask model A for the clause, requiring it to quote the exact passage and give the page number.
2. Open the PDF and read that page yourself. Everyone skips this and it takes ninety seconds.
3. Paste model A’s answer into model B and ask it to QA the interpretation against the same document.
4. Where the two disagree, that is your list for a human who is paid to be right.

Step one does most of the work. A model forced to quote and cite cannot hand you a smooth paraphrase of a clause that is not there.

Two setup habits from that same breakdown make either job go better:

• One job per session. Do not dump 20 files covering 20 topics and fire off 10 questions. The exception that works is same-domain consolidation. Four contracts from one vendor relationship is one job. Four unrelated policies from four departments is four jobs, and merging them is how you get answers that quietly blend documents.
• Decide the output format before you upload. That preference is the actual skill. It separates “summarize this contract,” which returns prose you have to re-read, from “give me a table with clause, page number, plain-English meaning, and risk to me.”

Capture and processing are separate problems here the same way they are in meeting notes, and whether this work belongs in a chat, a project, or something scheduled is the routing question covered in the Claude at Work pillar.

Where Each One Genuinely Wins

Neither is the universal answer, and pages that pick a winner outright are not being straight with you.

ChatGPT wins on volume and throughput. 80 files every 3 hours is a generous documented allowance, and the 2M token per-file cap does not apply to spreadsheets at all. If your PDF work sits next to CSVs, that exemption is real. Storage is published too, at 25GB per user and 100GB per org, which is more than Anthropic publishes on that dimension.

ChatGPT’s free tier is honest about being a trial. 3 file uploads per day tells you immediately whether it fits your week.

Claude wins on scanned and image-heavy documents on any tier. Anthropic documents visual analysis of PDFs under 100 pages with no tier condition, while OpenAI restricts visual retrieval to Enterprise. That is the largest documented capability gap between the two for this job.

Claude wins on published transparency. Context windows by model and plan, page thresholds, per-destination file caps. You can plan against numbers instead of guessing.

Both share one weak spot: non-PDF documents. Anthropic states that for DOCX, TXT, and the rest, “Claude extracts text only from these files. If they contain embedded images, Claude won’t be able to read or interpret them.” Same for Google Drive: “Claude extracts text content only from Google Drive files. Images embedded in documents are not processed.” A Word doc full of screenshots is a bad input on either platform.

Frequently Asked Questions

Is Claude or ChatGPT better for PDFs in 2026?

For one large PDF, especially a scanned or image-heavy one, Claude. Anthropic documents that Claude analyzes both text and visual elements in PDFs under 100 pages on any tier, while OpenAI documents that visual retrieval for PDFs is Enterprise-only and all other plans extract digital text and discard images. For a large library of documents you query repeatedly, both handle it, and the deciding factor is where you put the files rather than which brand you picked.

What is the maximum PDF size Claude can handle?

Anthropic documents 500MB per file for chat uploads, up to 20 files per chat. Project files are capped much lower at 30MB per file, with unlimited file count as long as total content fits the context window. Separately, Claude analyzes text and visuals in PDFs under 100 pages and processes text only for PDFs over 1000 pages.

Can ChatGPT read a scanned PDF?

Not on consumer plans. OpenAI documents that visual retrieval for PDFs is available only to ChatGPT Enterprise customers and is not supported for Free, Pro, Team, or Edu accounts. On those plans ChatGPT extracts digital text from the file and discards any images, so a scanned or photographed document has no extractable text and yields nothing usable.

Why did Claude miss something that was in my project file?

Anthropic documents that retrieval augmented generation activates automatically when a project approaches or exceeds context window limits. Below that threshold everything is loaded at once. Above it, Claude switches to searching and retrieving only what it judges relevant, which means the same project can behave two different ways depending on how full it is. A visual indicator appears when the switch happens.

How many PDFs can I upload to ChatGPT?

OpenAI documents up to 80 files every 3 hours, with free users limited to 3 file uploads per day. Individual files are capped at 512MB and 2M tokens, spreadsheets at roughly 50MB. Inside Projects, only 10 files can be uploaded at the same time, and the project count per plan runs from 5 on Free to 40 on Edu, Pro, Business, and Enterprise.

The Verdict, By What Is Actually on Your Desk

No single winner. A fork, decided by the document rather than the brand.

• One huge PDF you need answers from today: either tool, dropped into a chat window, not filed into a project. Chat takes 500MB on Claude and 512MB on ChatGPT. The project route caps at 30MB on Claude and strips images on both.
• A scan, a photo, or anything image-heavy: Claude, unless you are on ChatGPT Enterprise. Consumer ChatGPT discards the images, and images are the entire document.
• A library you will query for months: project knowledge on either platform, with the images caveat understood, plus the awareness that Claude switches to search once the project outgrows the window.
• A contract you are going to sign: neither one alone. Make the model quote and cite the page, read that page yourself, then cross-check with the other model per the Excel breakdown’s verify rule.
• You are only paying for one: ask whether your documents are born digital or scanned. That question decides it faster than any context window number.

Put the file in the right place. Test whether the visuals are being read. Then argue about which one writes prettier summaries.

Published and last reviewed July 18, 2026. Limits verified that day against vendor documentation linked inline: Anthropic’s upload page (itself dated April 22, 2026), Anthropic’s context window and RAG for projects pages, OpenAI’s file uploads FAQ, visual retrieval FAQ, and Projects documentation. No first-party head-to-head test was run for this page. These numbers drift, and both vendors ship changes constantly, so check the official pages before relying on any figure here.