Don't stop here
Hand-picked guides our readers explore right after this one.
Master ChatGPT with advanced prompting techniques, mega-prompts, and proven frameworks
Read the guideExpert guide to Claude prompts with XML tags, artifacts, and complex reasoning
Read the guideResearch-grade prompts for Perplexity AI's search-powered responses
Read the guideWhen a ChatGPT Project accepts your file but then cannot read it, or answers about the wrong content, the cause is usually the file or retrieval, not a broken account. ChatGPT fails to read an upload for five main reasons: it is a scanned, image-only PDF with no selectable text (ChatGPT does not run OCR by default), the format is unsupported, the document is too large or exceeds the token budget, the file is password-protected or corrupted, or the model simply did not invoke the retrieval tool. On top of that, some 2026 builds had a bug where files added on the web were not read reliably while the same files added via the desktop app worked. The fixes are to make the file machine-readable (OCR to text or DOCX), keep it a supported format and reasonable size, and explicitly tell the Project to consult the file. This guide covers each.
The Project accepts the upload but says it cannot access the file
ChatGPT answers from general knowledge instead of your document
It reads a DOCX or TXT fine but not your PDF
Only part of a long document seems to be used
Files added on the web are ignored, but the desktop app reads them
ChatGPT does not run OCR on uploaded PDFs by default. If the PDF is a scan or export with no selectable text, there is nothing for the model to read, so it appears to ignore the file.
ChatGPT reliably reads PDF, DOCX, PPTX, TXT, CSV, JSON, XML, HTML, common code files, native spreadsheets (XLSX, XLS), and standard images (PNG, JPG). Obscure or non-standard formats extract poorly or not at all.
Very large files, or many files, can exceed what the Project can hold in context at once. Plus users get the most reliable results with files well under the theoretical limit (practically, tens of MB, not hundreds).
Like Custom GPTs, a Project does not always search its files on every turn. If you do not point it at the document, it may answer from general knowledge and skip retrieval entirely.
In some 2026 builds, files added through the web were not read reliably in Projects while the same files added via the desktop app worked, an upload-surface bug rather than a file problem.
When to try: First, if the file is a scanned or image PDF
If the file is a scan or image-only PDF, run OCR first (Adobe Acrobat, Google Docs 'Open with Google Docs', or an OCR app) and save the result as DOCX or TXT. Text-based files extract far more reliably than PDFs, and this fixes the most common 'ignores my file' case.
When to try: When it answers without using your document
Do not assume the Project will search on its own. Prompt it: 'Using only the files in this project, answer... and quote the relevant section. If the answer is not in the files, say so rather than guessing.' This forces retrieval instead of a general-knowledge answer.
When to try: For large files or unusual formats
Convert to DOCX or TXT for text, keep spreadsheets as XLSX/CSV, and split very large documents into logical sections. Aim for files in the tens of MB rather than hundreds. Smaller, clean, supported files are read most reliably.
When to try: If files added on the web are not being read
Remove and re-add the file, then confirm it still appears. If web uploads are being ignored, add the file through the ChatGPT desktop app instead, which sidestepped the 2026 web-upload bug for many users.
When to try: When only part of a long document is used
For a document that exceeds the context budget, split it into chapters or themes, ask ChatGPT to analyze each section, then ask for a combined summary. This often produces better results than forcing one huge file through at once.
When to try: If nothing above resolves it
Refresh the Project, clear browser cache and cookies for chatgpt.com, disable conflicting extensions, and confirm the file is not password-protected or corrupted (open it yourself first). Check status.openai.com if uploads fail across files.
Convert scanned PDFs to searchable text (OCR to DOCX/TXT) before uploading
Keep Project files in supported formats and reasonable sizes
Always instruct the Project to consult its files and quote from them
For big references, split into sections rather than one massive file
If web uploads act up, add files via the desktop app
Contact OpenAI via help.openai.com if a supported, text-based, reasonably sized file that opens fine on your computer is still not read after re-uploading on both web and desktop, and instructing retrieval explicitly. Include the file type and size. For scanned PDFs, format, or size issues, the fixes above resolve it faster than support can.
The most common reason is a scanned, image-only PDF with no selectable text, ChatGPT does not OCR PDFs by default. Run OCR (Acrobat, Google Docs, or an OCR app) and save as DOCX or TXT, then re-upload. Also check the file is not too large, password-protected, or corrupted.
A Project does not always search its files automatically. Tell it explicitly: 'using only the files in this project, answer X and quote the relevant part, and if it is not in the files, say so'. That forces it to actually read the document.
PDF (with real text), DOCX, PPTX, TXT, CSV, JSON, XML, HTML, common code files, native spreadsheets (XLSX, XLS), and standard images (PNG, JPG). For text, DOCX or TXT extract most reliably. Convert anything obscure before uploading.
Yes, some 2026 Project builds had exactly this web-upload issue while desktop-app uploads read fine. Add the file through the ChatGPT desktop app as a workaround, and re-upload on web after refreshing.
The document likely exceeds the context budget. Split it into chapters or themes, have ChatGPT analyze each part, then ask for a combined summary. Chunked analysis beats forcing one oversized file through at once.