ChatGPT Web and the “Unable to load GPT conversation” error: what the OpenAI Community thread is about

⚡ The gist of the discussion

On OpenAI Community there is a thread titled “ChatGPT Web frequently shows "Unable to load GPT conversation" after the recent UI update”: 83 comments with 11,878 views, started by a member under the nickname tgelser. There is no opening text, only the title, so the discussion has to revolve around the symptom itself: after another update, the ChatGPT web interface fails to open some conversations. This primarily affects those who keep their work chats in the browser rather than in the app.

🗣 What participants are saying

An important caveat, without which this piece would be dishonest: the comments on this thread are not accessible to our editorial team. So below there are no quotes and no breakdown by positions — only the thread author and what can be seen from the thread itself. We will not attribute arguments to developers, researchers, or users that we haven’t read.

What is verifiable: the title, the author’s nickname (tgelser), 83 replies, 11,878 views, and zero votes. The ratio is telling — people come here to read, not to vote. This is what a support thread typically looks like when people arrive via a search for the exact error text and need a working workaround, not an opinion ranking. That is our interpretation of the counters, not a statement from the community.

The second verifiable fact is the claim in the title itself: the failure is tied to a recent UI update. This is the thread author’s assertion, and nothing in the data we received confirms or refutes the causal link. The word “frequently” is also unmeasured: the title contains no browsers, no share of broken chats, and no start time of the failure.

It’s also worth keeping in mind that “Unable to load GPT conversation” is a client-side message. It only tells you that the frontend didn’t receive the conversation data, and says nothing about the cause: network, cache, an expired session, an API error response, or a broken route after the UI migration. Judging by the thread’s existence and length, people there are trying to separate these cases — but which specific hypotheses they tested, we don’t know.

⚖️ Where they agree and where they diverge

The common denominator is one and it’s minimal: the symptom is reproducible for a large enough group of people to rack up 83 replies and nearly twelve thousand views. That makes the topic practical rather than theoretical — people need to open their conversations today. Everything else, including the link to the UI update, remains at the level of the title’s wording.

We don’t see a real point of conflict because we can’t see the actual replies: it’s unknown whether people there argue about the cause, about browsers, or simply collect “me too” confirmations. The honest answer is that there is no consensus in the materials we received, and presenting 83 replies as community agreement would be a substitution.

🧪 What to check yourself

• Open DevTools → Network, retry loading the broken conversation, and see what exactly fails: a backend request, static assets, or a response with a 4xx/5xx status.
• Compare three scenarios: a regular window, incognito without extensions, and a different browser. If it works in incognito — extensions or cache are to blame.
• Clear site data for chatgpt.com and log in again: an expired session produces similar symptoms while the interface still works.
• Check whether it’s specifically old long chats that break, or any chat in a row — these are different diagnoses with different workarounds.
• Before posting in the thread, record your browser, version, time, and conversation ID — without this, a bug report is nearly useless.

🔗 Sources

OpenAI Community — ChatGPT Web frequently shows “Unable to load GPT conversation” after the recent UI update

Disclaimer: this is a summary of a discussion, not facts verified by the editorial team. Opinions belong to the participants; the numbers belong to those who cited them.