ChatGPT “Add files is unavailable”: diagnose and fix it

September 5, 2026 · Ask Your Docs

When ChatGPT says “Add files is unavailable,” identify the failing step before changing anything. A missing attachment control, a rejected upload and an incomplete answer have different causes. Confirm your account, check service status and try a small harmless file. Then follow the branch below that matches what you observe.

This guide combines current official troubleshooting guidance with a suggested diagnostic sequence. It does not claim that one fix resolves every upload error. Product limits were checked in September 2026; use the linked OpenAI documentation for later changes.

Choose the symptom you actually see

Write down the exact error and where it appears. Keep the distinction between “the file never attached” and “the answer did not use it.” A successful upload followed by a weak answer is not evidence that the attachment button needs fixing. This small observation prevents many unnecessary retries.

Check the account and conversation first

Confirm the signed-in account and selected workspace. A personal account and an organization workspace may have different capabilities or controls. Start a new conversation to see whether the problem is specific to the current context. Compare what happens without changing multiple settings at once.

OpenAI’s File Uploads FAQ documents uploads on free and paid plans with account settings and limits. Paying for an account does not make uploads unlimited. Do not upgrade solely because a button is disabled until you have identified an actual plan requirement.

If the issue occurs only in a managed workspace, ask the administrator to check the relevant capabilities. Use a harmless example to describe the problem. Moving internal company files into a personal account may violate your organization’s rules and would not prove that the original workspace is repaired.

Distinguish file size, upload rate and storage

These are separate constraints. A file can be small enough but still encounter a rolling upload limit. A fresh conversation does not necessarily create a fresh account allowance. OpenAI also notes that failed upload attempts can count toward a rate cap, so repeatedly submitting the same file may make diagnosis harder.

Current documented ceilings include 512 MB per file and two million tokens for text documents, with an approximate 50 MB spreadsheet limit depending on row size. Images have their own limit. Consult the official FAQ for account-specific usage and storage details rather than translating every error into “the document is too large.”

If the message gives a reset time, respect it. If a file is too large, prepare a smaller permitted copy containing the relevant section, with its title and source context. Do not delete business records to troubleshoot a storage warning; first understand what occupies the relevant storage and what your retention rules allow.

Check for an incident before changing your files

Open OpenAI’s service status and look for an incident relevant to uploads or ChatGPT. An incident is a reason to pause repeated troubleshooting of otherwise healthy files. Keep the error time so you can compare it with the incident period.

A normal status page is not proof that your individual account or request is healthy. Continue with a small-file check if the problem remains. Conversely, an unrelated incident does not explain every failure. Match the reported service and symptom before drawing a conclusion.

After a relevant incident is resolved, retry one harmless file and ask for a specific fact from it. That checks both attachment and basic reading. If the small file works but the original still fails, continue with the file-specific branch rather than assuming the incident is ongoing.

Isolate browser and network problems

OpenAI’s error troubleshooting guide recommends checks such as a refreshed page, a private browsing window or another browser. A clean session helps distinguish a local browser problem from an account-wide failure. Sign into the same intended account so the comparison remains meaningful.

Try one change at a time and record the result. If the file uploads in another browser, investigate the original browser’s extensions or site data. If it fails across browsers and devices, the evidence points beyond a single browser session. A successful alternate-browser test does not identify which extension caused the original issue.

On a managed device, follow your IT policy for network filters and security extensions. Give the administrator the exact symptom and the result of the comparison. Do not disable organization protections merely to force an upload. If clearing site data is appropriate, expect to sign in again and preserve any unsent work first.

Test the file rather than just its extension

Open the source in Word, Excel, a PDF reader or the application that created it. A filename ending in DOCX does not establish that the document is valid. Check for password protection, corruption or an export that created only a shortcut. OpenAI’s supported-file guidance distinguishes supported documents from Google Docs shortcuts.

Use the small fictional Word example as a control file. If it works while your source fails, inspect what differs: size, format, structure or content. Keep the original unchanged and create a clean copy only when you have permission.

Renaming an extension does not convert a file. Export it from the source application into a supported format, then open the exported copy to check it. If you reduce the document to a section, include any exceptions or definitions needed to interpret that section correctly.

If the upload works, check what was read

Ask for a known heading, table label or explicit fact. Compare the response with the original. For the Word example, the launch date is October 12, 2026, under Campaign scope. Ask for that passage before asking for an overall review. A general summary can hide missing content.

If the answer misses a chart or scan, investigate the input route and extraction behavior. The PDF guide covers text and visual retrieval; the Excel guide covers sheet structure and calculations. Upload acceptance and complete analysis are different checks.

For sources you need repeatedly, a ChatGPT Project can provide a maintained reference collection. That is an organizational choice after the upload problem is understood. A different library or connector does not guarantee a workaround for account restrictions or a service failure.

Escalate with a reproducible report

If the problem persists, collect a concise report for OpenAI support: exact message, time and timezone, account plan, workspace, browser or app, file type and size, and the smallest harmless reproduction. Include which checks you tried and what changed. The original confidential file may not be necessary to reproduce the problem.

Keep the failure sequence explicit: whether the control appeared, whether attachment completed and whether a known-answer prompt worked. If support requests logs, review them for sensitive content before sharing. A clear reproduction is more actionable than “uploads are broken,” and it reduces the chance of repeating checks that have already ruled out a cause.

Frequently asked questions