(⌐■_■) NOBODY DELETED IT. IT RENTED.
ChatGPT never loses your file. It hands you a printout of a room that gets cleaned every half hour.
Five downloads, six minutes, one file — and not one of them said what broke.
I have spent 35 years building software, systems and networks, and the smallest part still wins: getting the file out of the chat.
you ask
│
▼
┌───────────────────────────────┐
│ a throwaway room, 30 min old │
│ the file is built in here │
└────────────────┬──────────────┘
│ a link to it
▼
┌───────────────────────────────┐
│ 15-30 minutes, nobody clicked │
│ same room, swept clean │
│ link: opens │
│ file: not inside │
└───────────────────────────────┘
The link outlives the file. That is the whole bug.
Five ways back, quickest first
Ask for the text, not the file — this one never expires. Give me the complete file again as one code block, no truncation, same code. Paste it, save as name.html, double-click.
Regenerate, then click inside seconds. The sandbox expired — write the file again, run the code, send the link. No refresh between the link and the click.
Open the link in a clean window. Private window, ad blockers off. It lands there → the gate was in your own browser.
Look in Library. Left sidebar → Library keeps uploaded and generated files, up to 20 GB on Plus, apart from the chats. Deleting a chat leaves the file.
Export the lot. Settings → Data controls → Export. The archive arrives by email with your conversations inside, even when the interface will not show them.
Six rules keep it out of the chat — the drawer below, and page one of the card.
Take the card with you
chatgpt-file-rescue-card.pdf — one A4 page: the five ways, both prompts, the six rules
Print it, drop it on the desktop, mail it to yourself. A copy a chat cannot reach.
🔍 Why the room gets swept, and the six rules I build now
One design decision explains all four.
1. The room is a machine, not your account. A sandbox is recycled after roughly 15–30 quiet minutes. The link keeps looking permanent while the file behind it is gone: a 404, a spinner that never ends, a download of 0 bytes. The 10:12 link that refused at 10:16 was this one.
2. A refresh builds a new room. Files made in the old one stay in the old one. The link that worked before the refresh refuses after it.
3. The code never ran. No python block, no Analyzed under the reply → the download link is decoration. Ask for a real run, then compare the file.
4. Your browser said no first. Downloads arrive from files.oaiusercontent.com, not openai.com. Ad blockers, proxies and antivirus refuse that host without a word. Private window works, yours does not → the gate is on your side.
Linux · Firefox · ChatGPT Plus · one browser, unedited screenshots below.
The six rules, so it stops happening. Works once, cannot be found again? That is a demo, not a deliverable.
- One permanent door — every app opens from a fixed place, never a link inside a conversation
- Old versions stay — a new build never overwrites the last one that worked
- It files itself — a new app registers on arrival
- Tested restore — a recovery path that was actually walked, not hoped for
- Survives a reboot — it opens again after the machine restarts
- No chat in the loop — built once, it runs with the conversation closed
🧾 The six minutes, and how to add yours
October 25, 2026, 10:12–10:18 AM Eastern. One file, BCBC-Network-Topology-V01-20261025.html, one browser, five failures:
10:12:46 "An error occurred inside
the visualization"
preview broke, file lived
10:15:09 "Failed to download file.
Please try again later."
the download lost its handle
10:16:29 "Couldn't load this file"
and a Retry button
the room was already swept
10:18:21 download fails,
then it will not open
no room left by the click
10:18:41 both errors again,
on repeat
nothing left to click
Add your case: the seven lines that make the record useful.
- What failed — the file, the download, or the conversation?
- When did it happen?
- Which browser and operating system?
- The exact error text?
- Did you get the file or the conversation back, and how?
- How much work did it cost you?
- Screenshots, or the steps that reproduce it?
No API keys, passwords, session tokens or private network details in the thread.
I am not claiming to know the cause. Whether this is widespread, intermittent or environment-specific is what an investigation is for, and a factual record is where it starts.
What would end this for everyone
- A generated file that still opens a week later
- Conversation and project history that stays reachable
- A recovery path when a download dies mid-click
- Errors that name the part that broke
- Storage for build output, not only chat text
- A workflow that survives a long build
I want ChatGPT to succeed. I want to trust what it hands me.
Two copies, one of them offline. That is the whole system.
William James
BCBC Technologies
Human-Designed. AI-Assisted. Independently Conceived.
!