Why ChatGPT says "you can send up to -1 files"

OpenAI does not document this message, so everything below is observed behaviour rather than stated policy. It is consistent enough to work with.

The number is a remainder, not a rule

Normally that message reads "you can send up to 3 files", or any other figure under the web ceiling of 20 files per message. People read the number as a ceiling. It is not. It is a subtraction: your allowance minus whatever is already counted against you.

Subtraction with no floor at zero can produce -1, and the interface prints the result it was given.

That is worth sitting with for a second, because it tells you what will not work. You cannot comply by attaching fewer files. There is no number below one. The count itself has to be reset, which means the fix is never on the attachment side.

What pushes the count below zero

The first four are cosmetic. The last one is real, and telling them apart takes about a minute.

Fixes, in the order worth trying

1. Empty the composer

   Remove every attachment chip, including greyed out ones and anything stuck at 0 per cent. Delete the draft text as well. A half attached file is the single most common cause, and it is often invisible.

2. Reload the page

   A hard reload, so Cmd+Shift+R on Mac or Ctrl+F5 on Windows. Your conversation comes back from the server. Only the unsent draft is lost.

3. Start a new chat

   If the number is still negative, open a fresh conversation and try one small file there. This rules out a count tied to the specific thread.

4. Open an incognito window with extensions off

   Sign in and attach one small file. This is the test that matters, because it removes every piece of local state at once.

5. If it still fails, stop and wait

   At this point it is not your browser. You are against a server side allowance and nothing you do in the interface will move it.

Telling a display fault from a real block

Step four is the whole diagnosis. A clean session with no extensions and no cached composer state either works or it does not, and each outcome points somewhere different.

If the file uploads in incognito, the problem was local. Go back to your normal window, clear the composer properly, and carry on.

If incognito fails the same way, you have hit the rolling cap of 80 files every 3 hours, or on Free the much lower allowance of 3 file uploads per day, which is a daily reset. The general cap rolls rather than resetting at a fixed time, so slots free up gradually as your oldest uploads age past three hours. An hour is usually enough.

Retrying is the one thing that makes it worse

OpenAI's own documentation notes that failed upload attempts can count toward the rate cap. So a message that started as a stale counter becomes a real block if you sit there clicking.

Six frustrated retries against a broken display spend six slots and upload nothing. Reload once, test once, then either fix the local state or wait.

Getting the document in while the count is stuck

If you are blocked and the work is not optional, there is a route that sidesteps the counter entirely.

Pasting text into the message box is not a file upload. It does not touch the upload allowance, it does not depend on the composer's attachment state, and the negative number has no bearing on it. Open the document, copy the text, paste it in.

The catch is length. Anything past a few thousand words has to go in as several messages, in order, with a note at the start telling ChatGPT to wait until you say the last piece has arrived.

What to actually do

Treat the negative number as information about the interface, not about you. Clear the composer, reload once, and try a clean incognito session. Three minutes of work covers the large majority of cases.

If a clean session fails identically, the counter was telling the truth in a clumsy way and you are over the cap. Waiting is the fix, pasting is the workaround, and retrying is the one move that costs you something.