OpenAI says failed attempts can sometimes count towards an upload-rate cap, so avoid cycling through the same upload repeatedly. Use the checks below to narrow the problem one step at a time.
ChatGPT file upload not working: the quickest checks
Before changing anything, note the exact error message, time, account plan, upload route, file extension and approximate size. Do not include sensitive file contents in screenshots or support notes. If you need a comparison upload and organisational policy permits one, use a harmless, non-sensitive file you are authorised to use rather than the original document.
Start with the file and account checks, then move to service and browser conditions if the file appears to meet the published limits.
| Check | Check without exposing the document | What the result suggests | Next safe action |
|---|---|---|---|
| File type or export | Compare the extension with OpenAI's current supported-types page. For a native cloud-document format, check whether an export is required. | A mismatch is evidence that the chosen format or export path is unsupported; a match only clears this one check. | Export a fresh copy to a listed format if authorised. Preserve the original and treat the export as a new document version. |
| Per-file constraint | Compare the file with the current size, document-token, spreadsheet or image constraint that applies to that type. | Exceeding a documented constraint explains why that attempt cannot meet the stated requirement. Being below it does not prove the file will upload or parse. | Reduce or split a non-sensitive working copy only if that still meets the task and your handling policy. Use the limits guide for current figures. |
| Account, rate, storage or Project allowance | Check the relevant account plan and keep rolling upload rate, daily allowance, shared storage and Project counts separate. | A documented allowance may explain a refusal, but a generic error does not reveal which counter was involved. | Stop after one or two controlled retries. Wait for the applicable window, remove only material you are authorised to remove, or ask the account owner to review usage. |
| Service status | Check OpenAI's official status page before changing local settings. | A reported incident makes a service-side issue plausible; a green status page does not rule out every provider issue. | Preserve the time and error. If an incident is relevant, follow its updates instead of repeatedly retrying. |
| Chat or browser state | In order, try a new chat, refresh, a private window, relevant site-data clearing and an approved second browser. Isolate only non-security extensions if your policy permits. | A different result narrows the circumstances in which the symptom appears; it does not by itself prove the underlying cause. | Record which single change altered the result. Restore any temporary browser change. Never disable managed or security controls. |
| Managed workplace network | Ask an authorised administrator to compare the error and time with the organisation's network policy and OpenAI's administrator guidance. | Filtering is one documented possibility, not a diagnosis. | Let IT decide whether any domain review is appropriate. Do not disable a VPN, firewall or endpoint control, self-allowlist a domain, or move work to a hotspot, personal account, network or device. |
| Escalation | Check whether the same symptom affects one file or all authorised tests, then collate the evidence above. | The pattern can help IT or OpenAI Support investigate, but it still may not establish a cause. | Contact the appropriate administrator or OpenAI Support. Share the document itself only if specifically requested and you are authorised to do so. |
The upload route is only one part of the wider picture. You can also understand chat uploads versus workspace access before deciding where a document should be used.
Save the error evidence before retrying
Record the exact message, the time, your plan, the file type and size. If the error is generic (for example, "unknown error" or "something went wrong"), note that explicitly. This evidence will help you or your IT team investigate and will be useful if you need to contact OpenAI Support.
A practical stop condition: because OpenAI says failed attempts can sometimes count towards the upload-rate cap, limit yourself to one or two controlled retries before moving on. That statement does not establish which counter a particular failure affected.
Check format, size, usage and storage constraints
First, confirm that the file extension is one OpenAI currently supports. The common supported formats include PDF, DOCX, PPTX, TXT, XLS, XLSX, CSV and TSV. Native .gdoc files are not supported and must be exported to a supported format first (OpenAI supported file types).
Next, compare your file against the relevant limits. OpenAI maintains separate counters for per-file size, document tokens, spreadsheet size, image size, rolling upload rate, shared storage and Project file counts (OpenAI File Uploads FAQ). The full numeric table is maintained on the limits page: check the current ChatGPT upload limits and file types.
If the file meets those limits, move on to the service and browser checks.
Check current ChatGPT service status
Before changing local settings, check whether OpenAI is reporting a service disruption. OpenAI's general troubleshooting guidance recommends checking the service-status page as an early step (OpenAI Troubleshooting). If a reported incident matches the timing and surface, follow its updates and avoid repeated retries. A clear status page is useful evidence, but it does not prove that the service played no part.
Test chat and browser state safely
OpenAI's general troubleshooting guidance suggests the following controlled checks (OpenAI Troubleshooting):
- Start a new chat and retry the upload.
- Refresh the page.
- Try a private or incognito window.
- Clear relevant site data or cookies for the ChatGPT domain.
- If organisational policy permits, isolate non-security browser extensions temporarily and restore them after the test.
- Try a different approved browser if one is available.
These tests help isolate the problem one change at a time. For work documents, keep managed security controls in place and use only devices, accounts and networks permitted by your organisation. For your own non-sensitive test file, comparing another browser or network you control can help identify where the failure occurs.
If the issue persists, record the checks and their results rather than assigning a cause. On a managed workplace connection, move to the administrator path below.
Handle workplace network restrictions with IT
On a managed workplace network, filtering is one possible source of access or upload problems. OpenAI provides domain guidance for authorised administrators to review (OpenAI Network recommendations). Its current examples include *.oaiusercontent.com; that is a prompt for administrator review, not an instruction for an end user to change a control.
If you are on a managed network:
- Give your IT team the exact error, time, account and route, plus the results of the authorised checks you completed.
- Ask them to review whether the relevant domains are accessible under your organisation's network policy.
- Do not attempt to bypass, weaken or reconfigure your organisation's network controls yourself.
- Do not move work to a hotspot, personal device, account or network to work around a managed restriction.
Allowlisting a domain does not guarantee success in every organisation, and the decision to permit or restrict access belongs to your IT administrator.
What to send OpenAI Support
If the issue persists after all the steps above, contact OpenAI Support. Provide:
- The exact error message and when it occurred.
- Your account plan.
- The file extension and approximate size.
- What you have already tried, including a new chat, private window and approved browser-state checks.
- Whether the issue is specific to one file or also affects a harmless, authorised comparison file.
Do not attach the sensitive file itself unless OpenAI Support specifically requests it and you are authorised to share it.
Check the exact document version before retrying
Once the upload problem is resolved, confirm which version you are about to submit—especially if troubleshooting involved exporting, editing or splitting it. Check the document for prompt-injection signals before adding it to AI context.
.mdSiren is a document security checkpoint for AI systems. It checks incoming versions for supported prompt-injection and document-borne risks, returns Approved, Needs review or Quarantine, and keeps the current eligible Approved copy ready for retrieval and reuse. A revised file needs its own check.
See the document workflow, or Coming soon. Its decisions cover the reported checks; upload troubleshooting remains a separate step. If the upload succeeds but content appears missing, check how ChatGPT reads PDFs.
Frequently asked questions
Why does ChatGPT say "unknown error" when I upload a file?
"Unknown error" is a generic message that does not identify a specific cause. Work through the diagnostic sequence in this guide and record what each check shows. Do not infer a particular constraint, browser problem or network rule from that message alone.
Why did I hit a limit after failed uploads?
OpenAI's documentation states that failed attempts can sometimes count towards the upload-rate cap. Repeated attempts may therefore affect the rolling allowance, but the error does not reveal the counter. Stop retrying and use the account's current guidance to determine when another authorised attempt is appropriate.
Why can one file upload while another cannot?
The files may differ in extension, export, size, token count or a type-specific constraint. Compare each file with the current official requirements. One success and one failure narrows the test conditions, but it does not prove which difference caused the result.
Can a work firewall block ChatGPT uploads?
It can. OpenAI documents managed-network filtering as one possible source of access or upload problems. Ask your IT administrator to review the evidence and relevant domain guidance; do not treat the symptom as proof that the firewall caused it or attempt a bypass.
Should I disable my VPN or security controls?
Keep managed or workplace security controls in place and ask IT to review the error. On a personal setup, you can compare a harmless test upload using another network you control, provided the change does not breach your document-handling obligations. Restore temporary settings after the test.
Why did the PDF upload but its contents seem missing?
A successful upload does not guarantee that every page or visual was processed. PDF handling varies by plan and attachment route. See the dedicated PDF guide for details on what ChatGPT can and cannot read in different scenarios.
