Google Chrome ERR_CONTENT_DECODING_FAILED: 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_CONTENT_DECODING_FAILED
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_CONTENT_DECODING_FAILED error in Google Chrome means the browser received a web page response that it could not properly decode or decompress. This usually happens when the server sends corrupted, misconfigured, or conflicting encoding headers — but it can also be caused by local browser issues like a bad cache, interfering extensions, or misconfigured network settings. The good news is this error is almost always fixable in a few minutes without any technical expertise.
Ad

Tools You'll Need

How to Fix Error Code ERR_CONTENT_DECODING_FAILED

  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 Chrome Extensions

  4. Disable Data Saver or Compression Proxy Settings

  5. Flush DNS Cache and Reset Network Settings

    Running network reset commands will disconnect any active VPN sessions and may reset custom network configurations. Document any custom settings before proceeding.

  6. Reset Chrome's Internal Network Settings (QUIC / SPDY Flags)

  7. Reset Chrome Settings to Default

    This step will disable all your extensions and reset personalized settings. Your bookmarks and saved passwords are preserved, but note down any custom settings you want to restore afterward.

  8. Test in a Different Browser or Device

  9. Reinstall Google Chrome

    Before uninstalling, make sure your Chrome data is synced to your Google account so you don't lose bookmarks or saved passwords.
Ad

When to Call a Professional

You generally do not need professional help for this error. However, if you are a website owner or developer seeing this error reported by your users, you should contact your web hosting provider or a backend developer to investigate your server's Content-Encoding and Transfer-Encoding HTTP headers — particularly misconfigured gzip or Brotli compression settings. If you are an end user and the error only appears on one specific website and all other websites work fine, the problem is on the website's server side and you should report it to the site owner.

Frequently Asked Questions

What does ERR_CONTENT_DECODING_FAILED mean in Chrome?
It means Chrome received data from a web server but could not decode or decompress it correctly. This is usually caused by the server sending incorrectly configured compression headers (like broken gzip or Brotli encoding), a corrupted local browser cache, or an interfering browser extension or proxy tool.
Why does ERR_CONTENT_DECODING_FAILED only happen on one website?
If the error only occurs on a single website and works fine everywhere else, the problem is almost certainly on the website's server side. The server is likely misconfiguring its Content-Encoding response header or sending corrupted compressed data. You can report the issue to the website owner, but there is little you can do to fix it as a visitor.
Does clearing cache fix ERR_CONTENT_DECODING_FAILED?
Yes, in many cases clearing Chrome's cache fixes this error immediately. If Chrome has stored a corrupted or outdated version of a page that contains bad encoding metadata, clearing the cache forces it to download a fresh copy from the server. This is always the first thing to try after a hard reload.
Can a VPN or ad blocker cause ERR_CONTENT_DECODING_FAILED?
Yes. VPN extensions, proxy tools, and some ad blockers can intercept and modify HTTP responses in a way that corrupts the encoding. Try loading the page in an Incognito window (where extensions are disabled by default) to confirm if an extension is the cause, then disable extensions one by one to find the culprit.
Is ERR_CONTENT_DECODING_FAILED a virus or security risk?
No, this error is not a sign of a virus or security threat. It is a technical communication error between Chrome and a web server related to data compression. It does not indicate that your computer is infected or that your data has been compromised. You can safely follow the troubleshooting steps above to resolve it.

Related Error Codes