ChatGPT Attachments Lost After Refresh

Uploaded files vanish from a conversation after page reload. Usually a session, sync, or storage scope issue. Recover the file and prevent it next time.

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

You drag a PDF into a ChatGPT conversation, get a few useful answers about it, then reload the tab and the attachment chip is just gone. The conversation history is still there but the file itself shows as missing, and follow-up questions get blank-look replies. ChatGPT stores attachments in a per-conversation scoped slot that does not always survive reload across devices, expired session tokens, or storage cleanup. The fix is to re-attach if you still have the source, harvest content from the chat history if you do not, and configure your workflow so this stops happening.

Common causes

Ordered by hit rate, highest first.

1. Session expired between upload and reload

Attachment URLs are signed with a session-scoped token. If your login token rotated or expired (often after 7-14 days), the chip resolves to nothing on reload.

How to judge: Try logging out and back in, then reopen the chat. If the chip still resolves to “file unavailable”, the underlying object was already invalidated.

2. File was uploaded from a different device

Files uploaded from the mobile app sometimes do not propagate to the web client immediately, and vice versa. On reload from the other device, the attachment is missing.

How to judge: Was the upload from a different device than the one you reloaded on? If yes, this is the cause.

3. Storage retention window expired

ChatGPT keeps uploaded files only as long as needed for the conversation, typically a rolling window. Older attachments in old chats can be garbage collected, especially on Free plans.

How to judge: How old is the upload? More than a couple of weeks and you are likely past retention.

4. Browser cleared site data or third-party cookies

If you cleared cookies, cleared site data, or have aggressive privacy extensions, your client may have lost the local references that resolve attachment chips.

How to judge: Did you clear browser data, switch browsers, or run a “clean cookies” extension recently? If yes, that is the cause.

5. Code interpreter sandbox was recycled

Files created by code interpreter live in a sandbox that gets reset between sessions. On reload, generated files (CSVs, charts) often cannot be re-downloaded.

How to judge: Was the file produced by code interpreter, not uploaded by you? If yes, the sandbox is gone.

6. Project file unlinked from conversation

If your chat is inside a Project and the file lived at the Project level, an admin or you may have removed it from the Project. The chat keeps a reference that no longer resolves.

How to judge: Open the Project, look at the file list. If the file is missing there, that is the source.

Before you start

Locate the original file on your local disk or cloud drive, you will likely need to re-attach.
Decide whether the answers in the chat are enough, or whether you need to re-process the file from scratch.
Note the upload date, recent uploads are easier to recover than old ones.

Information to collect

Original filename and approximate size.
Where the file was uploaded from (web, desktop, iOS, Android).
Whether the chat is inside a Project.
Date of the original upload.
Plan tier (Free, Plus, Team, Enterprise) and any retention policy your org has.
Whether other attachments in the same chat are intact or also missing.

Step-by-step fix

Step 1: Reload once and check the chip state

Sometimes the chip just failed to render on first load. Refresh the page once more, wait for the conversation to fully render, then look at the user message that originally contained the upload. If the chip appears, you are fine.

Step 2: Re-attach the original file

If you still have the source on disk, drag it into a new message in the same conversation with:

Re-attaching the same file as before. Please use this version
for any further questions.

The model will treat it as a fresh upload and answer using the new attachment.

Step 3: Harvest useful content from the chat history

Even if the file is gone, the answers you already got are still in the transcript. Ask:

Summarize everything you extracted from the file earlier in this
conversation. Include all key data points, quotes, and conclusions
so we can continue without re-uploading.

That gives you a portable summary you can keep working with.

Open the Project that contains this chat. Sidebar, then Files. If the file is missing, re-upload it to the Project (not the chat). All chats in that Project will then see it.

Step 5: Try the other client (web or app)

If you uploaded from mobile and the web shows nothing, open the chat in the mobile app, or vice versa. Occasionally the chip exists on the original client only.

Step 6: Switch to a stable browser session

Use a normal (non-incognito) window, in the same browser you originally uploaded from. Sign out and back in. This refreshes the session token that signs attachment URLs.

Step 7: For code interpreter outputs, re-run the analysis

If the missing file was a generated CSV or chart, ask the model to re-run the same analysis. With the original input still attached, it can regenerate the output quickly.

Verify

After re-attaching, ask a precise question about page 3 of the file (or row 50 of a CSV). A correct answer confirms the attachment is active again.
Reload once more, the chip should still be there.
If using a Project, open a new chat in that Project and confirm it can see the file too.

Long-term prevention

Keep original files in cloud storage you control (Drive, Dropbox), not just inside ChatGPT.
For reusable references, upload to a Project once instead of into individual chats.
Run long workflows in one session, not across many reloads spaced over weeks.
On shared devices, sign out cleanly when finished so the next session is not stranded.
Save the model’s summary of any file at the end of a session as a safety net.

Common pitfalls

Assuming the chat history alone preserves the file content. It only preserves the answers about it.
Re-uploading and then asking a question that depends on what was extracted earlier, the model may not re-extract identically.
Trusting code interpreter outputs to persist, they do not.
Clearing browser cookies between sessions and being surprised that attachment chips break.
Mixing Project files and chat-level files, easy to lose track of which is which.

FAQ

How long does ChatGPT keep an uploaded file? No official number, but assume a rolling window measured in days to weeks, not months.
Does Plus or Team retain files longer? Marginally, but the policy can change. Treat all attachments as ephemeral.
Why is the chip greyed out but not gone? The reference exists but the underlying object was deleted or expired. Re-attach.
Can I download my old attachments via export? Data export usually includes uploads from recent windows but not generated files from code interpreter.
Does ChatGPT remember the file’s content after the file is gone? Only what was already in the chat as transcript. The raw bytes are not magically remembered.
Why does mobile show the file but web does not? Cross-device sync of attachment chips can lag, particularly after a session rotation.

Tags: #ChatGPT #Troubleshooting #web