Uploaded File Disappears From the ChatGPT Conversation

You uploaded a file, asked a question, and now the file is gone from the chat. Whether it's actually gone — or just out of context — depends on where it was attached.

Published: May 17, 2026 Author: AI Productivity Guide Team 🌐 查看中文版本

ChatGPT has three “where the file lives” scopes: attached to a single message, in a Project, or in a Custom GPT’s Knowledge. The three behave completely differently but the UI makes them look similar — that’s the #1 source of files “disappearing.” Message-scope attachments scroll out of active context after enough turns; Temporary Chat keeps nothing; a browser refresh drops uploads that only existed in memory. Figure out which scope you used before doing anything else.

Common causes

Ordered by hit rate, highest first.

1. File attached to a single message, not to the Project

The most common failure. Inside a Project you can still drag files into the chat input — that’s a message-scope upload, present only for that turn and the following few. Once the conversation grows, the file ref is compressed away and the model says “I don’t see that file.”

How to spot it: Refresh the page and look at the message you attached the file to. Icon still there = message-scope (persistent but subject to context window). Icon gone = session-only upload. For permanence, drag to the left-hand Project Files panel.

2. Long conversation; early turns compressed out

ChatGPT implicitly compresses long chats: early messages get summarized, and the raw tokens (including file references) are dropped. Beyond ~20-30 turns, the model frequently “forgets” the file from the opening turn.

How to spot it: Ask “list every file name you’ve seen in this conversation from the beginning to now.” Missing ones = already compressed out of active context.

3. Uploaded inside a Temporary Chat

Temporary Chat (the “Temporary chat” toggle in the top-right) is designed to keep nothing — files included. Looks fine while open; everything gone on close.

How to spot it: A “Temporary” label at the top of the chat, a slightly different close button, or ?temporary-chat=true in the URL. Open a regular chat and re-upload.

4. Browser refresh dropped an in-memory upload

In some paths the file is still in a front-end blob and was used by the model before being persisted to the backend. A refresh drops it — the conversation history remains, but the file icon doesn’t.

How to spot it: Conversation visible after refresh but file icon gone = the upload only existed in the browser session. Re-upload to the current message.

5. Retention window expired on Free tier

Free users have short file retention (check OpenAI’s Help Center for current values; commonly 7-30 days). A file uploaded three days ago may already be purged.

How to spot it: Old conversations show greyed-out file icons or 404 on click = expired. Plus / Team / Enterprise retain longer.

6. You opened the chat on a different browser / device

File uploads are often tied to a client session. A file uploaded from macOS web may not be visible when you open the same chat in the iOS app.

How to spot it: Switch device / browser and check the same message — if the file icon is gone, it’s a session-binding issue.

Before you start

Confirm whether this happens in Projects, a Custom GPT, or a plain chat — file scope differs across the three.
Duplicate the chat before retesting so history doesn’t pollute the next diagnostic.
Confirm your plan: Free / Plus / Team / Enterprise differ in retention window and max file size.

Info to collect

File type, size (MB), conversation length at upload time (how many turns).
Upload route: dragged into the chat, Project Knowledge, or Custom GPT Knowledge.
Full prompt text + ChatGPT reply screenshot; record verbatim the “I don’t see the file” line.
Whether you used Temporary Chat, whether you switched device / browser.
Subscription tier + how long ago you uploaded.

Shortest fix path

Ordered by ROI. The first two solve ~80% of cases.

Step 1: Put recurring docs in Project Files

Not the chat input — the Files panel in the left Project sidebar. Steps:

Create or open a Project.
Left Project sidebar → Files → Add files.
Every chat under that Project automatically can reference these files.

Message-scope is for one-offs. Project-scope is for recurring use. Custom GPT Knowledge is for multi-user / long-term-stable material.

Step 2: For long plain chats, re-attach every few turns

If you insist on a plain chat, proactively re-upload when the conversation exceeds ~10 turns:

[Re-attaching report_q3.pdf]
Continuing from earlier — based on this file, what was the Q3 margin?

Or paste a file summary at the top of a new turn and refer to the summary thereafter.

Step 3: For very long conversations, summarize once and use the summary

Turn 1:

Summarize this file in 500 words. I'll use the summary instead of
the file later in the conversation.

For the next 20+ turns, ask the model to answer from the summary plus any specific quote you provide. The full file no longer needs to live in every turn’s context.

Step 4: Never use Temporary Chat for file-dependent tasks

Temporary Chat is for trace-free one-off questions. Any file-related task goes in a regular chat or a Project.

To check if you’re in Temporary Chat:

Web: URL contains ?temporary-chat=true, or “Temporary chat” label at top.
App: top-right toggle highlights “Temporary chat.”

Step 5: When switching device / browser, verify file presence

Before continuing a cross-device chat:

List every file currently in this conversation that you can access.

Matches your memory → continue. Mismatch → re-upload.

Step 6: Download originals while the chat is still alive

If the file is something ChatGPT generated, or a file you modified there, download to local while the conversation is still open. Don’t treat ChatGPT as cloud storage — retention runs out.

How to confirm the fix

Open a fresh chat (don’t continue in the old one), upload the same file to a Project, ask the same question — confirm every chat under the Project can reference it.
Open the same Project from another account or device and have it list files — matching list confirms Project-scope worked.
Have a colleague duplicate the (shared) Project and run the flow — confirms behavior is reproducible.

If still broken

Cut the file to the absolute minimum: 1-page PDF / 100-row CSV — rules out the file itself being corrupt or weirdly encoded.
Swap formats: PDF → txt, xlsx → csv, to rule out a format-specific parser issue.
Try every upload route — message vs Project vs Custom GPT Knowledge — to see which one holds reliably.
Package source file, prompt, conversation length, subscription screenshot, file a ticket at help.openai.com.

Prevention

Lock in the mental model: one-off = message attach; recurring = Project Files; multi-user = Custom GPT Knowledge.
Originals always stay local — ChatGPT is workspace, not storage.
For conversations past ~15 turns, write a file summary at the top of the chat proactively.
Any file task uses a regular chat or a Project — never Temporary Chat.
Before continuing a cross-device chat, ask “list current visible files” to verify.

Tags: #ChatGPT #ChatGPT files #Troubleshooting #Debug #File disappears