ERR_CONTENT_DECODING_FAILED: Fixes That Work

ERR_CONTENT_DECODING_FAILED is a Google Chrome error that appears when the browser cannot decompress a webpage it downloaded, often due to corrupted cache files, a faulty extension, or a network issue. You can usually fix it by clearing your cache, disabling extensions, or resetting the browser, and this article walks through every reliable solution.

What This Error Actually Means

When Chrome requests a webpage, the server often sends it compressed (usually with gzip or Brotli) to save bandwidth. Your browser then decompresses that data before rendering it. The ERR_CONTENT_DECODING_FAILED message means Chrome received data it expected to decompress, but the process failed—either the data was corrupted in transit, the cache stored a broken copy, or something on your system interfered with the decompression step.

This is not a virus warning or a sign your computer is broken. It is a transport-level failure, similar to a corrupted download. The error appears as a red page with the message “This webpage is not available” and the error code below it. It can affect any website, though it is more common on pages with heavy compression or large assets.

Most Common Causes

Understanding the root cause helps you pick the right fix. The most frequent culprits are:

• Corrupted cache: Chrome stored a compressed version of the page that is now incomplete or damaged.
• Browser extensions: Ad blockers, VPN extensions, or privacy tools that modify network requests can break decompression.
• Antivirus or firewall software: Some security suites scan HTTPS traffic and accidentally corrupt the data stream.
• Outdated Chrome version: Older builds may have bugs with newer compression algorithms.
• Network proxy or VPN: Intermediary servers can alter the compressed data.
• System date/time issues: Incorrect clock settings can cause SSL and compression handshakes to fail.

Fix 1: Hard Refresh and Reload

The simplest fix is often a hard refresh, which forces Chrome to ignore the cached version and re-download the page.

1. On Windows or Linux: press Ctrl + Shift + R.
2. On Mac: press Cmd + Shift + R.
3. Alternatively, open the page in an incognito window (Ctrl+Shift+N / Cmd+Shift+N). If it loads there, the issue is almost certainly cache or extension related.

If the page loads in incognito but not normally, proceed to the cache-clearing step below—it will resolve the majority of cases.

Fix 2: Clear Cache and Cookies

Corrupted cache data is the #1 cause of this error. Clearing it forces Chrome to download fresh copies of all files.

1. Click the three-dot menu in the top-right corner.
2. Go to More tools > Clear browsing data.
3. Set the time range to All time.
4. Check Cached images and files (and optionally Cookies and other site data if the problem persists).
5. Click Clear data.

After clearing, close and reopen Chrome completely. Test the problematic site again. If you do not want to clear all cookies, you can clear only cached files first—that often solves the issue without logging you out of websites.

Fix 3: Disable Extensions

Extensions that modify network traffic—ad blockers, privacy shields, download managers—are frequent triggers. To test this:

1. Type chrome://extensions in the address bar and press Enter.
2. Toggle off all extensions (or at least the ones related to ads, privacy, or VPN).
3. Reload the failing page.

If the page works, enable extensions one by one to find the culprit. Once identified, either remove it or check for an update. A particularly common offender is any extension that forces HTTPS or compresses images.

Fix 4: Check Antivirus and Network Settings

Security software can interfere with compressed content. If the error appears on multiple sites, try:

• Pausing your antivirus temporarily (do not disable it permanently) and reloading the page.
• If that fixes it, look in your antivirus settings for an option like “Scan HTTPS traffic” or “SSL inspection” and disable it.
• Disconnect from your VPN or proxy and test again.
• Flush your DNS cache: open Command Prompt (Windows) and run ipconfig /flushdns.

Corporate networks or school Wi-Fi with content filters are also known to cause this error. If you are on such a network, try a mobile hotspot to confirm.

Fix 5: Reset Chrome or Reinstall

If nothing above works, a deeper reset is needed. Chrome has a built-in reset that restores default settings while keeping your bookmarks and passwords.

1. Go to chrome://settings/reset.
2. Click Restore settings to their original defaults.
3. Confirm and restart Chrome.

If the problem persists after a reset, uninstall Chrome completely (choose to delete browsing data) and reinstall from the official Google Chrome download page. This is a last resort but is almost always effective.

Frequently Asked Questions

Why does this error only happen on some websites?

Websites differ in how they compress content. Some use Brotli, some use gzip, and some serve uncompressed data. If a specific site consistently triggers the error, it may be a server-side issue, but more often it means the cached copy of that particular site is corrupted. Clearing cache usually fixes it.

Is ERR_CONTENT_DECODING_FAILED a virus?

No. It is a standard Chrome network error. However, if you see it on a phishing site, it could be that the malicious server sent malformed data. If the error appears on trusted sites like Google or Wikipedia, it is almost certainly a local issue.

Will clearing cache log me out of websites?

Clearing only cached images and files will not log you out. Clearing cookies will. Start with cache-only, and only clear cookies if the error persists.

Does this error affect other browsers?

It is most commonly reported in Chrome, but Firefox and Edge (which is Chromium-based) can also show similar errors. The fixes are the same: clear cache, disable extensions, and check security software.

How do I prevent this error from happening again?

Keep Chrome updated, avoid installing too many network-modifying extensions, and periodically clear your cache. If you use a VPN, make sure it is up to date. Also ensure your system date and time are set to automatic—incorrect clocks cause many HTTPS-related failures.

Related

• Mouse That Keeps Scrolling? Fixes That Work
• Star Wars Galactic Racer on Luna: Prime Eligibility
• Why Opacity 0 Doesn’t Truly Hide an Element