ChatGPT nominally accepts many formats, but deep processing only covers a subset: text PDF / DOCX / TXT / MD / CSV / XLSX / JSON / PPTX; images PNG / JPG / WEBP / GIF; common source-code extensions. Anything outside that (Pages, Keynote, HEIC, archives, executables, exotic video codecs) is either rejected at upload or technically uploads but never reaches the analysis pipeline. The reliable path isn’t arguing with the upload — it’s converting to a known-good type.
Common causes
Ordered by hit rate, highest first.
1. Format not in the supported list
The most common “rejected” reason. Apple iWork (.pages, .key, .numbers), HEIC photos, RAW image formats (.raw, .cr2, .nef), 3D models (.obj, .stl) — all outside the whitelist.
How to spot it: “This file type isn’t supported” or “I can’t process this file” at upload time = outside whitelist. Check the official Help Center for the current list.
2. Technically supported but analysis pipeline doesn’t cover it
ZIP / RAR / 7z upload but ChatGPT won’t extract them. EXE / DMG / APP upload but never get analyzed. SVG uploads cleanly but vision may not render it correctly.
How to spot it: Upload succeeds with no error, but when you ask it says “I can’t analyze this file” / “I only see the file name” = pipeline doesn’t take it.
3. File extension is wrong; byte signature doesn’t match
Renaming report.txt to report.pdf doesn’t make it a PDF. Some ChatGPT paths route by byte signature (magic number), others by extension — mismatch sends it down the wrong path.
How to spot it: Run file report.pdf on macOS / Linux. Output “ASCII text” but extension .pdf = this case.
4. Container with unsupported codec
.mp4 uploads but contains HEVC / AV1 / VP9 — the analysis pipeline only handles H.264. .docx with embedded legacy OLE objects fails to parse.
How to spot it: Run ffprobe video.mp4 to inspect codecs. Other tools open it fine but ChatGPT doesn’t = codec issue.
5. File too large hits a different limit
Per-type size caps vary (PDF typically ≤ 50MB, images ≤ 20MB, CSV / XLSX vary). Over the limit sometimes surfaces as “unsupported” when the real cause is size.
How to spot it: Upload a smaller file of the same type. If that one works, the issue is size; if it fails too, it’s a real type issue.
6. Backend processor changed — worked yesterday, fails today
“Supported” is dynamic. OpenAI occasionally switches backend PDF parsers, image libraries, etc., breaking edge formats (e.g. PDFs with embedded fonts) overnight.
How to spot it: Same file worked historically, started failing in the past week = backend change. Wait a few days or convert format.
Before you start
- Confirm whether this happens in Projects, a Custom GPT, or a plain chat — file types and size caps differ.
- Duplicate the chat before retesting so history doesn’t pollute the next diagnostic.
- Confirm your plan: Free / Plus / Team / Enterprise differ in size caps and supported types.
Info to collect
- The file’s actual type (run
file <name>, do not trust the extension). - Size (MB), origin (phone photo, screenshot, download, sent by colleague).
- Full error screenshot, or screenshot of an upload that “worked” but yields empty answers.
- Upload route: dragged into chat, Project Files, or Custom GPT Knowledge.
- Current model + subscription tier.
Shortest fix path
Ordered by ROI. The first two solve ~70% of cases.
Step 1: Identify the actual type before deciding what to convert
Don’t trust the extension. Run:
# macOS / Linux
file mystery_file
# e.g.: mystery_file: PDF document, version 1.7
# Windows PowerShell
Get-Item mystery_file | Format-ListOnce you know the real type, consult the conversion table (next step).
Step 2: Convert to a “high-fidelity supported type”
Map by content category:
| You have | Convert to | Tool |
|---|---|---|
| Pages / Keynote / Numbers | Apple iWork → Export → PDF | |
| HEIC | JPG / PNG | macOS Preview / iPhone settings / heif-convert |
| RAW image | JPG | Lightroom / darktable / phone export |
| EPUB | PDF / TXT | Calibre ebook-convert |
| Audio mp3 / m4a / wav | Transcript text | Whisper / MacWhisper (local) → upload .txt |
| Video mp4 | Key frames + transcript | ffmpeg for frames; Whisper for transcript |
| ZIP / RAR | Extract, upload individual files | unzip / unrar / Finder |
| .doc (legacy Word) | .docx | Word “Save As” |
| Scanned PDF | OCR’d PDF | ocrmypdf input.pdf output.pdf |
After converting, use the real extension (no more spoofing).
Step 3: HEIC / RAW photo special case
iPhone default camera shoots HEIC, which ChatGPT often won’t accept:
iPhone → Settings → Camera → Formats → choose "Most Compatible"
→ future photos will be JPGOr convert at send time: open in macOS Preview → Export as JPG → upload.
Step 4: Audio / video must be transcribed locally first
ChatGPT won’t auto-transcribe long audio. Run locally:
# Install whisper
pip install openai-whisper
# Transcribe
whisper meeting.m4a --model medium --language English --output_format txt
# Outputs meeting.txt — upload thisShort audio too — local transcription is more reliable than asking ChatGPT to “listen and summarize.”
Step 5: Extract archives locally
ChatGPT won’t unzip ZIP / RAR / 7z. Extract locally, pick the 3-5 files you actually need:
unzip -l archive.zip # See contents
unzip archive.zip -d ./out # ExtractDon’t upload all 20-100 files — cherry-pick the core ones.
Step 6: When all else fails, paste as text
The universal fallback: open in the source app → Select All → Copy → paste into ChatGPT as text. You lose styling but keep the information — fine for pure analysis tasks.
How to confirm the fix
- After conversion, open a fresh chat, upload, and ask a content-specific question (not “what do you see”) — confirm the answer references actual file content.
- Have it quote a sentence verbatim from the converted file; the quote should match the original — confirms conversion was lossless.
- Have a colleague run the same conversion pipeline and upload — confirms the path is reproducible.
If still broken
- Cut the file to the minimum: 1-page PDF / 1 image / 100-row CSV — see if the smallest case works.
- Redo conversion with a different tool:
marker-pdfinstead of Acrobat,magickinstead of Preview — different tools produce different artifacts. - Switch model: 4o → o3 / GPT-5; vision and extraction quality differs across models.
- Package source file + converted file + error screenshot, file a ticket at help.openai.com.
Prevention
- Standardize uploads: PDF / DOCX / TXT / MD for text; CSV / XLSX for tables; PNG / JPG for images; source extensions for code.
- Disable HEIC on iPhone permanently: Settings → Camera → Formats → Most Compatible.
- For any edited Office doc, re-save before upload to refresh the internal format.
- Extract big archives locally and cherry-pick — don’t ZIP an entire project for upload.
- Always Whisper-transcribe audio / video locally and upload the .txt — more reliable than asking the model to listen.
Related reading
- ChatGPT file upload failed
- ChatGPT generated file download failed
- ChatGPT uploaded PDF not analyzed correctly
- ChatGPT Projects
- ChatGPT file analysis
- ChatGPT Projects advanced workflow
Tags: #ChatGPT #ChatGPT files #Troubleshooting #Debug #File type