“ChatGPT is not working” can describe a blank page, a failed sign-in, one conversation that will not continue, a network error or a usage-limit notice. Those situations need different responses.
Note the exact stage that fails and whether a new conversation behaves the same way. That quick comparison can separate a service or account issue from a problem limited to one browser session or conversation.
Copy any unsent prompt first. Then use one short prompt and one browser or network comparison to narrow the problem without losing useful work.
Guide reviewed: October 8, 2026. Interface labels may vary by version, account and device.
Name the exact failure before changing the browser
| Symptom | Useful comparison | Next action |
|---|---|---|
| One conversation stalls | Short prompt in a new chat | Preserve the old chat and test only needed context |
| Blank page or sign-in loop | Fresh browser session | Check extensions and the correct login method |
| Usage-limit notice | Account and exact notice | Follow the displayed reset or plan information |
| Network error during a reply | Same browser on another permitted network | Ask the network administrator if the failure follows that connection |
| App fails but browser works | Account and app version | Update and restart the app |
Start with the service and the symptom
OpenAI’s status page can show a reported interruption. Check whether the incident concerns ChatGPT and the function you are using. A status page describes reported service conditions; it does not establish that every account or feature is working normally.
Also distinguish a technical error from an account notice. A message about a usage limit, unavailable feature or sign-in requirement calls for reading that notice and checking the account. Clearing browser data does not reset an account’s usage allowance.
If one conversation will not complete
- Save the unsent text outside the chat.
- Open a new conversation and send a short ordinary prompt without attachments.
- If it succeeds, add only the material needed for the task.
- Compare text-only and attachment attempts separately; record the feature that fails.
When a reply stalls, a new conversation with a short, ordinary prompt is a useful comparison. If that works, the original conversation may be the place to focus. This is especially helpful when it contains many turns or large attachments.
Preserve the original conversation and bring only the information needed for the next task into the new one. For example, a short summary and the relevant paragraph may be easier to test than resubmitting a long history and every uploaded file.
An error during response generation does not tell you that your prompt was incorrect. Record whether the same problem happens with a simple prompt, an attachment or a particular feature. Those differences give support a clearer picture.
If the page is blank or sign-in fails
Read the account notice first. A private window is a session comparison, not a way to bypass an account limit. If a different login method opens another account, its history and subscription may differ.
Compare the usual browser session with a private window, a fresh profile or another current browser. A successful comparison suggests that local session data or an extension may matter. Some extensions can run in private windows, so check which ones are enabled there.
If you clear site data, expect to sign in again. Use the login method associated with your account and confirm the resulting account before assuming that a subscription or conversation has disappeared.
Changing passwords is not a general solution to a loading problem. Account recovery belongs with an actual access or security problem and should be completed through OpenAI’s official account flow.
If the error mentions the network
A browser can load the page yet fail to maintain the connection used by a response. The distinction is similar to a video call that starts normally but disconnects during the conversation.
Compare another permitted network while keeping the device and browser the same. If the issue follows only one network path, a proxy, VPN or managed filter may be involved. On a work or school connection, ask the administrator about the symptom rather than changing organizational protections.
If the browser works but a desktop or mobile app does not, check the app’s version and account, and restart it. That comparison helps separate an app issue from a service-wide problem.
If a generated file will not download
A download failure is separate from the quality of the answer. Generated-file links can stop being available, so a fresh file may be needed. Check whether the problem affects a recent file as well as an older link.
After downloading, open the file and verify its contents. A successful transfer does not establish that the document contains the requested work, just as a failed transfer does not prove that generation itself failed.
Make the support request easy to investigate
For a persistent issue, describe the approximate time and time zone, the error text, browser or app version, the feature involved and the comparisons that changed the result. A conversation identifier may help when support requests it.
Diagnostic recordings can contain cookies, tokens, conversation text and other private information. Follow official support instructions and review what you share. Never publish a raw diagnostic file in a public comment simply to demonstrate the problem.
The official troubleshooting guide below is the right place to check changing product-specific steps. Your own comparison notes make those steps easier to apply to the problem you actually have.
Official OpenAI status and support resources
Verify recovery with the task that failed
A page loading again is only the first check. Send the short test, then repeat the original operation with the necessary context. For a file task, download and open the new result. Record the error text and time if the same operation fails again.