Google Chrome Error Code ERR_RESPONSE_HEADERS_TRUNCATED: How to Fix It

Easy 10-30 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_RESPONSE_HEADERS_TRUNCATED
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_RESPONSE_HEADERS_TRUNCATED error in Google Chrome means the browser received an incomplete or cut-off set of HTTP response headers from the web server, so it could not properly load the page. This typically happens due to corrupted cache data, misconfigured network settings, conflicting browser extensions, or an issue on the server side. In most cases you can resolve it yourself in a few minutes by following the steps below.
Ad

Tools You'll Need

How to Fix Error Code ERR_RESPONSE_HEADERS_TRUNCATED

  1. Hard-Reload the Page

  2. Clear Chrome's Browsing Cache and Cookies

    Clearing cookies will sign you out of websites. Make sure you know your login credentials before proceeding.

  3. Disable All Browser Extensions

  4. Test in Chrome Incognito Mode

  5. Flush DNS Cache and Reset Network Settings

    Running network reset commands will temporarily disconnect you from the internet. Save any open work before proceeding.

  6. Disable VPN or Proxy Settings

  7. Change Your DNS Server

  8. Reset Chrome Flags to Default

  9. Update Google Chrome

  10. Reset Chrome to Default Settings

    This will disable all extensions and clear startup pages, pinned tabs, and search engine preferences. Note your customizations before resetting.

  11. Check if the Problem is Server-Side

Ad

When to Call a Professional

If the error persists on multiple websites after completing all steps, and also appears in other browsers, contact your Internet Service Provider (ISP) because the issue may be with your modem, router firmware, or ISP-level traffic inspection (deep packet inspection) that is stripping response headers. If the error affects only one website and your browser is fully updated and reset, the website's server administrator or hosting provider needs to investigate and fix the server-side header configuration — this is beyond what any end user can resolve.

Frequently Asked Questions

What does ERR_RESPONSE_HEADERS_TRUNCATED mean in Chrome?
It means Chrome received HTTP response headers from the web server that were cut off or incomplete before they finished transmitting. Chrome cannot safely interpret the response without complete headers, so it blocks the page and shows this error instead of displaying potentially broken or unsafe content.
Is ERR_RESPONSE_HEADERS_TRUNCATED caused by my computer or the website?
It can be either. Common causes on your side include corrupted Chrome cache, a conflicting browser extension, a VPN or proxy modifying traffic, or misconfigured network settings. On the server side, the website may be sending headers that are too large, malformed, or cut off due to a misconfigured web server or CDN. Testing in multiple browsers helps you determine which side is responsible.
Why does ERR_RESPONSE_HEADERS_TRUNCATED only happen on one website?
If the error appears on only one specific site, it is almost certainly a server-side issue. That website's server (Apache, Nginx, IIS, or a CDN in front of it) is likely sending HTTP response headers that exceed Chrome's header size limit, are malformed, or are being cut off mid-transmission. You should report the problem to the website owner or check whether the issue appears in other browsers as well.
Can a VPN cause the ERR_RESPONSE_HEADERS_TRUNCATED error?
Yes. VPN software and VPN browser extensions route your traffic through an intermediary server, and some VPNs modify or compress HTTP headers in ways that can truncate them. Try disabling your VPN completely and reloading the page. If the error goes away, try switching to a different VPN server location or contact your VPN provider's support team.
Will clearing my cache fix ERR_RESPONSE_HEADERS_TRUNCATED?
Clearing Chrome's cache and cookies is one of the most effective first steps and resolves this error in many cases, especially if Chrome has stored a corrupted cached response for that URL. Go to Chrome settings, clear cached images, files, and cookies for all time, restart Chrome, and try the page again. If the error returns immediately after clearing, the cause is likely on the server or network level rather than in your cache.

Related Error Codes