FIX ChatGPT Network Error in Chrome: 3 Fixes (2026)

Key takeaways

• ChatGPT’s mid-generation “Network Error” is Chrome discarding the tab and killing the WebSocket. Not a ChatGPT outage.
• When Chrome discards the tab, the server sees a dropped heartbeat and terminates the stream. The response is gone when you reload.
• Fix it by adding chatgpt.com and chat.openai.com to chrome://settings/performance → “Always keep these sites active”.

You switch tabs while ChatGPT is generating a long response, come back a minute later, and find a red “Network Error” mid-sentence. The response is gone and you have to reload. This is not a ChatGPT outage — it is Chrome’s Memory Saver discarding the tab while you were away, which kills the WebSocket connection streaming the response. The AI server sees the connection drop and terminates the generation.

Quick Diagnosis

Fix 1: Add the AI Domain to Chrome’s Active Sites List

Chrome has a native exception list for Memory Saver. Adding AI chat domains here tells Chrome to never discard these tabs even under memory pressure:

1. Navigate to chrome://settings/performance
2. Under Memory Saver, click Add next to “Always keep these sites active”
3. Enter chatgpt.com and chat.openai.com
4. Repeat for any other AI tools you use: claude.ai, chat.deepseek.com, gemini.google.com

Expected result: Chrome will not discard these tabs even under memory pressure. Note that Chrome’s native list is less reliable than extension-level whitelisting under severe memory pressure.

Fix 2: Keep the AI Tab in a Separate Window

Chrome is less aggressive about discarding tabs that are the only tab in a visible window.

1. Right-click the ChatGPT tab
2. Select Move tab to new window
3. Position the window on a second monitor or keep it minimized (not closed)

This is a partial mitigation — it does not fully prevent discarding but reduces the likelihood.

Fix 3: Disable Chrome Memory Saver Globally (Not Recommended for General Use)

Disabling Memory Saver entirely prevents tab discards but allows all tabs to consume RAM freely, which can cause system slowdowns on machines with limited RAM.

1. Navigate to chrome://settings/performance
2. Under Memory Saver, toggle it off

This trades the network error problem for potential system performance degradation. Only recommended if you have 16 GB or more of RAM and keep fewer than 20 tabs open.

Keeping Background Tabs From Suspending Unexpectedly

Fix 1 using Chrome’s native list works for most people. SuperchargePerformance offers a more reliable alternative: its per-site whitelist operates at the extension level, which is not overridden by OS memory pressure the way Chrome’s native list can be.

When you add chatgpt.com or claude.ai to the whitelist:

• The tab is never passed to chrome.tabs.discard() by the extension
• The WebSocket connection stays alive throughout the generation
• All your other inactive tabs are still suspended to free RAM — the AI tab gets more resources, not fewer

The extension is not required to fix this — Chrome’s native list (Fix 1) handles it for most setups. It is worth adding if you find that Fix 1 still occasionally fails under heavy memory pressure, or if you want the RAM savings on other tabs as a bonus.

Technical Background

AI chat interfaces like ChatGPT use WebSockets or Server-Sent Events (SSE) to stream responses token-by-token. These are persistent connections: the server sends data continuously until the response is complete.

When Chrome discards a background tab, it terminates the renderer process. This kills the JavaScript engine running in that tab, which drops the WebSocket’s keep-alive heartbeat. The AI server detects the missed heartbeat, assumes the client disconnected, and terminates the stream. The next time you focus the tab, Chrome reloads it from scratch — the in-progress response is gone.

Chrome’s background timer throttling (aligning JavaScript timer wakeups to once per minute in background tabs) can also delay heartbeat pings enough to trigger a server-side timeout on long-running generations, even without a full tab discard.

Related Articles

• Keep ChatGPT Running in Chrome Background Tabs — broader guide to keeping AI sessions alive
• Prevent Chrome from Suspending the OpenClaw Web UI — same fix for local AI tools over localhost
• Disable Chrome Efficiency Mode for Specific Tabs — target throttling settings per tab