ERR_CONTENT_DECODING_FAILED — What It Means & How to Fix It

What Does This Error Mean?

ERR_CONTENT_DECODING_FAILED means your browser received data from the server but could not decode (uncompress) it. Websites compress their content before sending it to speed up loading. Your browser then decompresses it to display the page. If the compressed data is corrupted, the encoding type is mismatched, or the server sent garbled data, the decompression fails and you see this error.

Affected Models

Google Chrome
Microsoft Edge
Firefox
All modern browsers
Windows
macOS

Common Causes

The server sent content encoded in a format (like gzip or Brotli) that does not match its Content-Encoding header
Your browser's cached version of the page is corrupted or uses a different encoding than the current version
A proxy, firewall, or CDN is modifying the compressed data in transit, corrupting it
The web server has a misconfiguration — such as double-encoding content or sending wrong encoding headers
A browser extension is modifying the response data in a way that breaks decompression

How to Fix It

Clear your browser cache completely. In Chrome, press Ctrl+Shift+Delete, select All time, check Cached images and files (and Cookies), and click Clear data. Then reload the page.

A corrupted cached response is the most common cause. Clearing it forces Chrome to download a fresh, clean copy.
Try a hard refresh with Ctrl+F5 (or Ctrl+Shift+R). This bypasses the cache entirely and fetches everything fresh from the server.

If the page loads after a hard refresh, the cached data was definitely corrupted.
Open the page in Incognito mode (Ctrl+Shift+N). Incognito has no cache. If the page loads in Incognito, your regular cache has a corrupted copy.

Incognito also runs without extensions, helping to rule out extension interference.
Disable browser extensions, especially privacy or network-modifying extensions. Go to chrome://extensions and toggle all extensions off. Reload the page.

Some extensions modify server responses in ways that break the encoding.
If you use a VPN or proxy, disconnect it and reload the page. Network middlemen can corrupt compressed data as it passes through them.

This is particularly common with low-quality VPNs that do not handle compressed HTTP traffic correctly.

When to Call a Professional

If this error is on your own website, check your web server's compression settings. Look for double-encoding issues — for example, if both Nginx and your application are compressing the same response. Your web host's support team can review server logs and configuration.

Frequently Asked Questions

What is content encoding and why do websites use it?

When a server sends a web page to your browser, it first compresses the data — often using gzip or Brotli compression. This makes the file smaller, so it downloads faster. Your browser then automatically decompresses it. When this compression/decompression cycle breaks down, you see ERR_CONTENT_DECODING_FAILED.

Is this always a server problem or can it be on my end?

It can be either. A corrupted browser cache is a client-side (your end) problem and is easy to fix by clearing the cache. A server misconfiguration sending wrong encoding is a server-side problem only the webmaster can fix. Start by clearing your cache — if the problem persists on all browsers and devices, the server is at fault.

Can a VPN really corrupt web content?

Yes, some low-quality VPN services can. VPNs sometimes intercept and re-compress HTTP responses, or strip compression headers. If the VPN's modification results in mismatched encoding information, the browser cannot decode the response. A reliable, paid VPN service is much less likely to cause this than a free or low-quality one.