As of July 2, 2026, ChatGPT Free lets you upload 3 files per day, Plus can upload up to 80 files every 3 hours, and Pro is positioned for unlimited file uploads, but Pro is not a no-limits mode. File size, text-token, spreadsheet, image, storage, Project, GPT-knowledge, fair-use, abuse-prevention, and peak-hour limits can still stop an upload.
The fastest way to diagnose a blocked upload is to separate the upload-rate quota from the other caps. A Plus user who has not used 80 files may still hit a Project file cap, a 512 MB file cap, a 2 million token text cap, a 50 MB spreadsheet cap, a 20 MB image cap, or account storage. OpenAI's own help pages also currently disagree on the Plus Project-file cap: one page shows 20 files per Project, while the Projects help page shows 25. Treat that as an official conflict, not a reason to invent one definitive number.
Use the table below first, then jump to the cap that matches your symptom. If the active blocker is the 3-hour or daily quota, waiting is the honest fix. If it is Project capacity, storage, file size, or token length, reducing the right layer is faster than upgrading.
The Fast Answer: ChatGPT File Upload Limits by Plan
The headline number is the upload-rate quota. It controls how many files you can add over time, not how many files can live forever inside a Project, GPT, or account library.
| Plan | Upload-rate limit checked July 2, 2026 | Project file cap | What can still block you | First move when blocked |
|---|---|---|---|---|
| ChatGPT Free | 3 files per day | 5 files per Project | size, token length, storage, file type, peak load | wait for the daily pool or reduce the active file layer |
| ChatGPT Plus | up to 80 files every 3 hours | 20 or 25 files per Project in conflicting official pages | Project cap, 512 MB file cap, 2M token text cap, 50 MB spreadsheet cap, 20 MB image cap, storage | wait for the rolling window, or fix the non-rate cap |
| ChatGPT Pro | marketed for unlimited file uploads | 40 files per Project | fair use, abuse prevention, size, storage, Project, token, and context boundaries | slow down if rate-shaped; otherwise reduce the active layer |
The current source of truth for the 3/day Free number, 80 files every 3 hours, file-size limits, and storage caps is OpenAI's File Uploads FAQ. The current source for Project-specific limits is OpenAI's Projects in ChatGPT, which is why the Plus Project cap needs a conflict note instead of a false certainty.
Two practical consequences follow from that split. First, upgrading a plan changes the upload-rate and Project capacity, but it does not make an oversized file valid. Second, deleting a conversation or removing a file from a Project is not the same as resetting the 3-hour upload window.
How the 3-Hour Rolling Window Works
Plus users should think of the 80-file allowance as a moving window, not a fixed clock reset. If you upload 20 files at 9:00 and 20 more at 10:00, the first group starts aging out around 12:00 and the second group around 13:00. Capacity returns gradually as earlier uploads leave the window.
That is why a user can delete old files and still see an upload message. Storage cleanup can help when storage is the blocker, but it does not immediately restore a rate slot that is still inside the rolling window. For a pure rate cap, the correct action is boring but reliable: wait, then retry with smaller batches.
OpenAI also says limits may be lowered during peak hours. That matters because a limit message at 65 or 70 recent uploads does not always prove that the documented 80-file number is wrong. It may mean ChatGPT is temporarily operating under a lower cap. The product also does not show a live remaining-count meter for the rolling upload quota, so manual counting is imperfect.
The Free plan is different. Free users get a daily file-upload pool rather than the Plus 3-hour pool. If you are testing a document workflow on Free and hit the 3-file daily limit, splitting the same work into smaller chunks will usually make the problem worse because each chunk costs another upload.
Project, GPT, Storage, and File Caps Are Separate
The Project cap is the easiest limit to confuse with the upload-rate quota. A Project can be full even when your rolling upload quota still has room. According to the current Projects help page, Free gets 5 files per Project, Plus gets 25, and Pro gets 40. The File Uploads FAQ currently gives a different Plus Project number: 20. Because both pages are official and both were current in this run, the safest article answer is to show the conflict and tell large-Project users to check the live UI before planning a big upload set.
GPT knowledge files are another separate lane. The File Uploads FAQ describes up to 10 files per GPT for the lifetime of that GPT. That does not mean every ChatGPT chat, Project, or message has the same 10-file meaning. When a guide says "10 files" without naming whether it means simultaneous upload, GPT knowledge, message batch, or Project storage, it is compressing multiple rules into one misleading number.
Per-file limits are more mechanical:
| File layer | Current cap to plan around | What to do when it is the blocker |
|---|---|---|
| Any chat or GPT file | 512 MB per file | compress, split, or remove unnecessary pages |
| Text and document files | 2 million tokens per file | extract the relevant section or split by chapter/topic |
| CSV and spreadsheets | about 50 MB, depending on row size | filter columns/rows, split sheets, or summarize locally first |
| Images | 20 MB per image | resize or compress before upload |
| Storage | 25 GB per end user; 100 GB per organization | delete old files from Library storage or account storage surfaces |
The better mental model is a stack. Upload-rate answers "how many files over time?" Project answers "how many files can this workspace carry?" File size answers "is this individual file valid?" Storage answers "does the account have room?" Token length answers "can ChatGPT read this document as one object?" A plan upgrade can raise some layers and leave others unchanged.
Diagnose the Upload Message Before You Upgrade
When ChatGPT refuses a file, do not start with the subscription page. Start with the symptom. The wrong fix wastes time: waiting will not repair a 600 MB file, and upgrading will not help if the current blocker is a malformed spreadsheet or a full Project.
Use this order:
| Symptom | Likely cap | What to try first |
|---|---|---|
| You uploaded many files recently and every small valid file now fails | rolling or daily upload quota | wait for the 3-hour window or daily pool to recover |
| The Project already has many files attached | Project file cap | remove stale Project files, split the work into another Project, or reduce the file set |
| One large PDF or archive fails | 512 MB file cap | compress, split, or upload only the pages that matter |
| A long document uploads but analysis feels incomplete or fails | text-token cap or context pressure | split into sections and ask targeted questions |
| A spreadsheet fails even though it is under 512 MB | spreadsheet-specific cap or row shape | reduce rows/columns and save a smaller CSV |
| Uploads fail across old conversations and Projects | storage cap | check Settings > Storage or Library storage and delete old uploads |
| Pro user sees throttling-like behavior | fair-use, abuse-prevention, or temporary load control | slow down, reduce batch size, and retry later |
Reducing file count is useful only when file count is the active blocker. Combining related documents into one clean PDF can be smart for a review packet, but it is not magic: the merged file still has to satisfy size, token, and spreadsheet limits. If the merged file becomes too large or too noisy, it can make the analysis worse.
Should You Upgrade From Free to Plus or Pro?
Upgrade decisions should follow the cap you actually hit.
Move from Free to Plus when the 3-file daily pool is the recurring blocker and your files are otherwise valid. Plus changes the practical workflow because 80 files every 3 hours is enough for normal document review, school work, research packets, screenshots, small spreadsheets, and mixed file conversations.
Do not move to Plus just to solve one oversized file. A 700 MB PDF remains too large. A text file above the token cap still needs splitting. A spreadsheet that exceeds the spreadsheet cap still needs reduction. If your main pain is file shape rather than file count, a better pre-upload workflow beats a plan change.
Pro makes sense when the rate ceiling is repeatedly the real constraint and the work is worth the price: heavy document review, repeated research batches, long client work sessions, or team-like usage inside one account. Even then, read "unlimited file uploads" as a plan position, not as permission to ignore fair-use, safety, storage, Project, and file-size boundaries. The ChatGPT pricing page is useful for plan positioning, but the Help Center pages still control the operational limits.
ChatGPT Upload Limits Are Not API Limits
The ChatGPT web and app upload rules are consumer-product rules. OpenAI API file handling uses separate endpoints, billing, storage, and rate limits. If you are building a production workflow that processes hundreds or thousands of files, do not try to turn the ChatGPT upload box into a backend.
Use ChatGPT when the work is interactive: read a few files, compare documents, ask follow-up questions, inspect screenshots, or reason through a Project. Use an API workflow when the work is repeatable: ingestion, extraction, classification, batch review, logging, retries, and audit trails. That route has its own constraints and costs, but at least the limits belong to the system you are actually building.
For a non-technical user, the practical bridge is still simple: keep ChatGPT for judgment-heavy file conversations, and reduce file count or file size before upload. For a developer, the bridge is architectural: move repeatable file processing into an API or data pipeline rather than trying to schedule around an interactive quota.
FAQ
How many files can Free users upload to ChatGPT?
As of July 2, 2026, Free users are limited to 3 file uploads per day. That is a daily pool, not the Plus 3-hour rolling window.
How many files can ChatGPT Plus users upload?
Plus users can upload up to 80 files every 3 hours, subject to temporary reductions during peak hours. Project, storage, file-size, spreadsheet, image, and token caps still apply.
Does ChatGPT Pro have unlimited file uploads?
Pro is positioned for unlimited file uploads, but that does not erase all product boundaries. Fair use, abuse prevention, 512 MB file size, Project capacity, storage, token, spreadsheet, image, and context constraints can still matter.
How many files can I put in a ChatGPT Project?
The current Projects help page lists Free at 5 files per Project, Plus at 25, and Pro at 40. The File Uploads FAQ currently lists Plus at 20 and Pro/Team/Education/Business at 40. Because the official pages conflict for Plus, check the live Project UI before planning a large Plus Project.
What is the maximum file size in ChatGPT?
The general hard limit is 512 MB per file. Text and document files also have a 2 million token cap. Spreadsheets are approximately capped at 50 MB depending on row size, and images have a 20 MB per-image cap.
Can I see how many uploads I have left?
ChatGPT can show storage usage under Settings > Storage or Library storage, but it does not show a live remaining count for the rolling upload quota. If upload timing matters, track recent uploads manually and leave room for peak-hour reductions.
What should I do if I need to upload more than the limit?
First identify the active cap. If it is the rolling or daily quota, wait. If it is Project capacity, remove or split Project files. If it is file size, tokens, spreadsheet size, image size, or storage, reduce that layer. Upgrade only when the count or plan capacity is the recurring blocker.