Verified against OpenAI documentation · August 9, 2026
ChatGPT file upload failed? First separate the file itself from the limit that blocked it. A file can be under 512 MB and still exceed the text-token cap, the rolling upload rate, a Project file-count limit, or shared storage. The right fix depends on which limit the error is describing.
Quick diagnosis
- Try one small PDF or TXT file in a new chat.
- Confirm the active ChatGPT account, plan, and workspace.
- Compare the file size, token length, file count, and storage with the limits below.
- Check OpenAI Status for an upload incident.
- If the message says “upload limit reached,” stop repeated retries; failed attempts can count toward the rolling rate.
Current ChatGPT file limits
| Limit or surface | Current official guidance |
|---|---|
| Any file in a ChatGPT conversation or GPT | 512 MB maximum per file |
| Text and document files | 2 million tokens per file; this cap does not apply to spreadsheets |
| CSV or spreadsheet | Approximately 50 MB, depending on row size |
| Image | 20 MB per image |
| Rolling upload rate | Up to 80 files every 3 hours; OpenAI may lower this during peak periods |
| Free-plan allowance | Up to 3 file uploads per day |
| Shared storage | 25 GB per end user; 100 GB per organization, across chats, Projects, and custom GPT knowledge |
| Files in a Project | Plus: up to 20; Pro, Team, Education, and Business: up to 40 |
| Files in one custom GPT | Up to 10 files for the lifetime of that GPT |
These are different gates. A 20 MB image can satisfy the file-size rule but still fail because the account hit its rolling rate or storage cap. Conversely, deleting a file may free storage without resetting the short-term upload window.
Which upload surface are you using?
ChatGPT conversations, Projects, custom GPT knowledge, and Advanced Data Analysis share some account and storage limits but do not have identical file-count rules. Check the destination before comparing the error with a generic “ChatGPT limit.” The official FAQ also treats API uploads separately: API features have their own requirements, supported purposes, and limits.
- Conversation: check the per-file size, token, image, rate, and shared-storage limits.
- Project: check the plan-specific file-count limit as well as the file and storage limits.
- Custom GPT: check the 10-file lifetime limit and the GPT knowledge storage cap.
- API: do not assume a ChatGPT subscription limit also applies to an API request.
1. Reduce the file to a clean test case
Start with a short, ordinary PDF or TXT file. If that succeeds, the original file may be too large, too long, damaged, password-protected, or unusually complex.
- Export a document again as a standard PDF or DOCX.
- Split a long report into logical sections.
- Remove embedded media that is not needed for the question.
- Save a spreadsheet with fewer sheets or rows when testing.
- Resize an image below 20 MB and keep the original separately.
2. Check tokens, not only megabytes
A document can be far below 512 MB and still exceed the 2-million-token limit. Long OCR output, repeated text, source-code archives converted to text, and tables with many rows can be token-heavy. A smaller file is not automatically a shorter document.
If a large document is important, split it by topic, upload one section at a time, and ask a focused question. This reduces context noise and makes it easier to identify which section caused the failure.
3. Check the rolling rate and shared storage separately
OpenAI documents two limits that are often confused: a rolling upload-rate cap and shared storage caps. The rate window can be exhausted even when your stored files are few. The storage cap can remain full even after the upload window has reset.
- Stop retrying the same failed upload and wait for the rolling window to move.
- Open Settings → Storage to review available storage when that view is present on your account.
- Remove unneeded files from recent chats, Projects, or custom GPT knowledge when storage is the problem.
- Remember that failed attempts can sometimes count toward the upload-rate cap.
ChatGPT does not currently show exactly how much of the rolling upload-rate quota remains. Do not interpret the storage screen as a live countdown for the short-term rate.
4. Confirm the account, plan, and workspace
If you use more than one ChatGPT account or organization, verify the active profile before troubleshooting. A personal account and a work organization can have different storage pools, project rules, and permissions. A file that works in one workspace may fail in another without the file changing.
- Check the email or login method shown in the active profile.
- Confirm whether the upload is in a personal account, Team, Enterprise, Education, or Business workspace.
- Check the Project file-count rule for the current plan.
- Do not buy a different plan until you know which limit blocked the upload.
5. Account for document and image behavior
A successful upload does not guarantee that every visual element will be understood. OpenAI says that, outside Enterprise visual retrieval for PDFs, other plans and document files use text-based retrieval and may discard embedded images. If a chart, scan, or screenshot matters, upload the important image separately or use a suitable PDF workflow.
For sensitive documents, remove credentials, customer data, health information, and unnecessary personal details before uploading. Only share a file when you have permission to send its contents to the service.
6. Rule out browser, app, and network problems
- Start a new chat and upload one small file.
- Try a private window or another current browser.
- Temporarily disable an aggressive content blocker for ChatGPT.
- Update the ChatGPT mobile app if the problem occurs only on a phone.
- Try a stable network without a restrictive corporate proxy or VPN.
These steps isolate a client-side failure; they cannot bypass an account-level file, rate, project, or storage cap. If a small supported file fails in more than one browser and there is no status incident, continue with the support checklist.
7. What to send to OpenAI Support
Prepare the account email, plan or workspace, a screenshot of the exact error, the file type and approximate size, the exact timestamp and timezone, the browser or app version, and the request ID if one appears. Explain whether a small test file succeeds. Do not send the confidential file itself unless support provides a secure route and you are authorized to share it.
Official sources
HiseHub is independent and is not affiliated with OpenAI. Limits, availability, and product behavior can change; the official pages above control.