ChatGPT “Something Went Wrong” Error? Fix It in This Order

 

ChatGPT shows “Something went wrong”, but that message does not tell you whether the problem is the current conversation, one feature, your browser, your network, your account, or the service itself.

The fastest fix is not to try random browser settings. First determine the scope of the failure: does one prompt fail, one conversation fail, one feature fail, or does ChatGPT fail everywhere?

This guide focuses specifically on the general “Something went wrong” error that appears after you are already signed in. Login loops and blank screens belong to a separate login guide, while file-upload failures and explicit upload-limit warnings have their own troubleshooting paths.

The same error message can come from a conversation problem, a feature-specific failure, a browser or network issue, or a service incident.

Quick Fix Order

Save your prompt → Retry once → Test the same prompt in a new chat → Test plain text without files or images → Check OpenAI Status → Compare browser, device, and network only if the error is broader.

First, Save Your Prompt Before You Troubleshoot

If you typed a long request, copy it before refreshing, changing chats, or closing the page.

This matters because troubleshooting can remove the unsent or failed prompt from the interface. Losing the prompt creates a second problem that has nothing to do with the original error.

If the request contains sensitive information, save it somewhere appropriate for that information rather than placing it in an insecure temporary location.

Step 1: Retry Once—Not Ten Times

A temporary request failure can sometimes clear on the next attempt.

1. Wait a few seconds.
2. Retry the same request once.
3. If it succeeds, continue normally.
4. If it fails again, stop repeating the same action and diagnose the scope.

Repeated clicking does not tell you whether the cause is the conversation, feature, network, or service. It can also create duplicate requests when the interface is delayed.

Use one retry as a test.

If the second attempt fails, change the test—not just the number of retries.

Step 2: Test the Same Prompt in a New Chat

This is one of the highest-value tests because it separates a conversation-specific problem from a broader ChatGPT problem.

1. Copy the failed prompt.
2. Open a new regular chat.
3. Paste the same prompt.
4. Send it once.

If it works in the new chat

The original conversation may have become unstable, unusually long, or affected by a temporary state tied to that thread.

You can continue in the fresh chat. If the old conversation contained important context, bring over only the information needed for the current task instead of copying the entire history.

If it fails in the new chat too

The problem is broader than one conversation. Continue to the next test.

A new-chat control test quickly tells you whether the error belongs to one conversation or affects ChatGPT more broadly.

Step 3: Test Plain Text With No File, Image, or Special Tool

If the failed request used a file, image, web search, data analysis, image generation, or another feature, strip the test down to ordinary text.

For example, send:

Please answer with one sentence: What is the capital of Canada?

The exact question is not important. The point is to test a simple text response.

If plain text works but the original feature fails

The problem is likely feature-specific rather than a complete ChatGPT outage.

Examples:

• text works, but file upload fails;
• text works, but image upload fails;
• text works, but image generation fails;
• text works, but one tool or integration fails;
• text works, but a particular model or mode fails.

Use the troubleshooting guide for that feature instead of applying every general browser fix.

If the problem is attaching a file, use ChatGPT File Upload Not Working? Fix It in This Order. If ChatGPT explicitly says you reached an upload limit, use the dedicated upload-limit guide instead.

If plain text also fails

You now know that the failure is not limited to the original feature. Check service status and the local environment.

Step 4: Check OpenAI Status

Visit the official OpenAI Status page.

Look for an active incident affecting ChatGPT, conversations, responses, or the feature you were using.

If a relevant incident is active, stop making disruptive local changes. Clearing cookies, reinstalling apps, converting files, or changing account settings will not repair a service-side outage.

After the incident is resolved, repeat one simple text test before changing anything else.

Use This Scope Test Before Changing Browser Settings

What Fails?	Most Useful Interpretation	Next Step
One prompt fails once	Temporary request failure is possible	Retry once
One conversation fails	Thread-specific problem is possible	Test the same prompt in a new chat
One feature fails, plain text works	Feature-specific problem	Troubleshoot that feature
Every chat fails in one browser	Browser-profile issue becomes more likely	Try private mode or another browser
Every browser fails on one network	Network path may be involved	Compare another trusted network
Multiple devices and networks fail	Service or account-level issue becomes more likely	Check Status and prepare Support details

Step 5: If Every Chat Fails in One Browser, Try Private Mode

Open a private, incognito, or InPrivate window and sign in to ChatGPT. Then send one simple text prompt.

If private mode works

Your account and the service may be fine. Focus on the normal browser profile.

Possible causes include:

• stale ChatGPT site data;
• an extension conflict;
• privacy or script blocking;
• browser-profile corruption;
• security software integrated with the browser.

If private mode also fails

Try another current browser before clearing large amounts of browser data.

If another browser also fails, the problem is less likely to be a single browser profile.

Step 6: Clear ChatGPT Site Data Only When the Browser Is the Suspect

If private mode works and the normal browser consistently fails, targeted site-data cleanup is reasonable.

1. Open the browser’s Privacy, Cookies, or Site Data settings.
2. Find ChatGPT or OpenAI entries.
3. Remove data for the affected site.
4. Close all ChatGPT tabs.
5. Restart the browser.
6. Sign in again.
7. Test one simple text prompt.

This may sign you out of ChatGPT.

Do not start by clearing all cookies and browser history unless targeted cleanup fails and you understand the impact. A full wipe can sign you out of many unrelated sites.

Step 7: Test Extensions One at a Time

Extensions can alter scripts, requests, privacy behavior, page content, or security checks.

Relevant categories include:

• ad blockers;
• script blockers;
• privacy extensions;
• browser-based VPNs;
• security extensions;
• content filters;
• tools that modify webpage requests or forms.

Disable one likely extension, reload ChatGPT, and run the same simple test.

If the error disappears, re-enable other extensions and isolate the specific conflict.

Do not permanently disable security protections just to make ChatGPT work.

Identify the conflict and restore protections that are not responsible.

Step 8: Compare Another Device

If ChatGPT works normally on another trusted device using the same account, the problem probably belongs to the original device, browser, or app environment.

Check:

• browser version;
• ChatGPT app version;
• operating-system updates;
• security software;
• device storage problems;
• network configuration;
• managed-device restrictions.

This comparison can prevent unnecessary account changes.

Step 9: Compare Another Network

If the error appears across browsers on one network, compare a different trusted connection if practical.

For example:

• home Wi-Fi versus mobile data;
• office network versus personal hotspot;
• VPN connected versus disconnected, if you control the VPN and testing is allowed.

If ChatGPT works on another network, investigate:

• VPN;
• proxy;
• Secure DNS;
• firewall;
• router filtering;
• antivirus web protection;
• company or school network policies.

OpenAI provides network recommendations for ChatGPT that may help administrators diagnose filtered traffic.

Do not bypass workplace or school security controls. Ask the administrator to review the network.

If “Something Went Wrong” Appears Only After a Long Prompt

A long or complex request can make diagnosis confusing because the failure may come from the request itself, the conversation state, or a transient service problem.

Do not immediately assume the prompt is “too long.” Instead, compare:

1. the same prompt in a new chat;
2. a shorter version that preserves the same core task;
3. a simple plain-text control prompt.

If the simple test works but the long request fails repeatedly, split the task into logical stages rather than blindly deleting important instructions.

For example:

Stage 1: Read the material and identify the structure only.

Stage 2: Analyze sections 1–3 using the criteria below.

Stage 3: Continue with sections 4–6.

Stage 4: Produce the final synthesis.

This preserves the task’s meaning while reducing the amount of work requested in one operation.

If the Error Happens in Only One Conversation

When the same prompt works in a new chat, do not continue forcing the old thread to behave.

Before moving:

• copy the latest approved output;
• save essential instructions;
• write a short summary of the current task state;
• carry over only the context needed for the next step.

If a conversation has started mixing instructions or pulling in old context incorrectly, use the dedicated guide on when to start a fresh chat rather than treating that as a general service error.

If the Error Appears Only With Files

If ordinary text works but attaching a file triggers the error, this general guide has already done its job: it identified a feature-specific failure.

Do not keep clearing cookies or changing networks unless the file-upload guide gives you evidence to do so.

Separate two cases:

• File upload not working: the attachment process fails.
• Upload limit reached: ChatGPT explicitly reports a rate, storage, Project, or file restriction.

Those problems need different fixes.

If the Error Appears Only With Images or Image Generation

Test plain text first. If text works, check whether the problem occurs when:

• uploading an image;
• analyzing an image;
• generating a new image;
• editing an existing image.

Do not diagnose a feature-specific image failure as a complete account outage when ordinary conversations still work.

If the Error Appears Only in the App

If the web version works but the mobile or desktop app fails, focus on the app.

1. Fully close the app.
2. Reopen it and run a simple text test.
3. Check for an app update.
4. Restart the device.
5. Compare another network.
6. Check the operating system for updates.
7. Reinstall only after simpler tests fail.

Reinstalling first removes useful diagnostic information and may not address a network or service problem.

Do Not Confuse This Error With a Login Problem

If you cannot stay signed in, are repeatedly returned to the login page, or see a blank page immediately after authentication, use ChatGPT Login Loop or Blank Screen? Fix It in This Order.

This article assumes you can reach ChatGPT and the failure occurs while trying to use it.

Do Not Confuse This Error With an Interrupted Answer

If ChatGPT began answering normally and then stopped partway through, your main goal may be to continue the unfinished response without duplication.

That is different from diagnosing a generic “Something went wrong” message before a usable answer is produced.

Why Refreshing Can Help—But Is Not a Diagnosis

A page refresh can recover a temporarily stuck interface. It does not tell you why the error happened.

Use refresh after you have copied your prompt. If the problem immediately returns, move to a controlled comparison such as a new chat or private window.

Repeatedly refreshing without changing the test gives you little information.

Why Clearing Cookies Is Not Step One

Many troubleshooting lists recommend deleting cookies immediately because it is easy to describe. That does not make it the best first test.

A new-chat test and private-window test are less disruptive and reveal more:

• new chat tells you whether the problem is conversation-specific;
• plain text tells you whether the problem is feature-specific;
• private mode tells you whether the browser profile is involved.

Only then does targeted site-data cleanup become a logical next step.

Why Switching Models Is a Test, Not a Guaranteed Fix

If your account offers more than one model or mode, switching can help identify whether the error is limited to one option.

But do not treat model switching as a universal fix. If every model and ordinary text request fails, continue diagnosing the service, browser, network, or account environment.

Common Mistakes That Waste Time

Common Mistake	Why It Is Weak	Better Action
Clicking Regenerate repeatedly	You do not learn whether the problem is broader	Retry once, then change the test
Clearing every cookie immediately	It is disruptive and may be unrelated	Test a new chat and private window first
Changing the prompt, browser, and network at once	You cannot tell which change mattered	Change one variable at a time
Treating a file-only error as a general outage	The feature may be the only problem	Test plain text
Treating a login loop as “Something went wrong”	Authentication requires a different troubleshooting path	Use the login-loop guide
Reinstalling the app first	It removes evidence before easier tests	Restart, update, and compare networks first
Bypassing company security	It may violate policy	Ask the administrator to review the network

Use a Simple Diagnostic Matrix

Test	If It Works	If It Fails
Retry once	Likely temporary failure	Continue diagnosis
Same prompt in new chat	Original thread may be the problem	Broader than one conversation
Plain text only	Original feature may be the problem	General ChatGPT path may be affected
Private window	Normal browser profile is suspect	Try another browser or environment
Another browser	Original browser is suspect	Compare device or network
Another network	Original network is suspect	Compare device and check service
Another device	Original device is suspect	Service or account issue becomes more likely

How to Confirm That the Problem Is Really Fixed

Do not stop at “the page loaded.” Reproduce the type of action that originally failed.

1. Send one simple text prompt.
2. Send the original prompt again if appropriate.
3. If the original failure involved a feature, test that feature once.
4. Confirm that the response completes normally.
5. Refresh or open another chat to make sure the fix is stable.

If simple text works but the original feature still fails, return to the feature-specific troubleshooting path.

When to Contact OpenAI Support

Contact Support when the error continues after you have narrowed it carefully and there is no relevant active incident.

Useful details include:

• exact error wording;
• date, local time, and time zone;
• ChatGPT plan or workspace;
• browser or app version;
• operating system;
• whether the same prompt fails in a new chat;
• whether simple text works;
• whether the problem is tied to one feature;
• whether private mode works;
• whether another browser works;
• whether another network works;
• whether another device works;
• request or Ray ID if one is displayed.

If Support requests a HAR file or browser-console information, follow its current instructions carefully. Diagnostic files may contain sensitive information, so review and sanitize them before sharing.

Support summary template

ChatGPT shows “Something went wrong.”

Date, local time, and time zone: [details]

Browser or app: [version]

Operating system: [OS]

Plan or workspace: [details]

Same prompt fails in a new chat: Yes / No

Simple text also fails: Yes / No

Only one feature fails: [feature or No]

Private window also fails: Yes / No

Another browser also fails: Yes / No

Another network also fails: Yes / No

Another device also fails: Yes / No

Exact error message: [message]

Request or Ray ID: [if shown]

Steps already tried: [list]

Final “Something Went Wrong” Checklist

Use this order

□ Copy your prompt before refreshing.

□ Retry once.

□ Test the same prompt in a new chat.

□ Test a simple plain-text request.

□ Decide whether one feature or all of ChatGPT is failing.

□ Check OpenAI Status.

□ Try private mode if every chat fails in one browser.

□ Clear ChatGPT site data only if the browser profile is implicated.

□ Test extensions one at a time.

□ Compare another browser.

□ Compare another device.

□ Compare another trusted network.

□ Use the login guide for login loops or blank screens.

□ Use the file-upload guide for attachment failures.

□ Record diagnostic details before contacting Support.

The Bottom Line

The message “Something went wrong” is too broad to tell you the cause by itself.

The fastest route is to determine the scope:

• one conversation;
• one feature;
• one browser or device;
• one network;
• or ChatGPT more broadly.

New chat → plain text → status → browser → network → device is a more useful diagnostic sequence than randomly clearing settings.

Frequently Asked Questions

Why does ChatGPT keep saying “Something went wrong”?

The message can appear because of a temporary request failure, one conversation, one feature, a browser profile, a network path, or a broader service problem. Use controlled tests to identify the scope.

Should I keep clicking Regenerate?

No. Retry once. If the error returns, test the same request in a new chat or use a simple plain-text control prompt.

Why does a new chat fix the error?

The original conversation may have entered a temporary bad state or accumulated context that contributes to the failure. A new-chat test isolates that possibility.

Why does text work but file upload fails?

That points toward a feature-specific upload problem rather than a complete ChatGPT failure. Use the dedicated file-upload troubleshooting path.

Will clearing cookies fix “Something went wrong”?

Sometimes, but it should not be the first step. A private-window test can tell you whether browser site data or extensions are likely involved before you clear anything.

Why does ChatGPT work on mobile data but not Wi-Fi?

The Wi-Fi path may include a VPN, proxy, DNS filter, firewall, or network policy that interferes with ChatGPT requests.

When should I contact Support?

Contact Support when the error persists across controlled tests, no relevant service incident is active, and you can provide details showing where the failure occurs.

ChatGPT interfaces, models, tools, error behavior, and troubleshooting guidance can change. Check current official OpenAI documentation and service status when an error persists.