What does ERR_CONTENT_DECODING_FAILED mean?

The short answer

ERR_CONTENT_DECODING_FAILED means your browser received data from a website but couldn’t decode it properly, usually because the data was compressed incorrectly or got corrupted during transfer.

Why does it happen?

When you visit a website, the server often compresses the page data (using gzip or similar methods) to make it load faster. Your browser then decompresses it on arrival. This error shows up when that process fails. Common causes include:

  • Broken compression — the server says the data is compressed, but it actually isn’t, or it’s compressed in a different format than advertised
  • Corrupted data — something went wrong during the transfer between the server and your browser
  • Bad browser cache — your browser is trying to load a corrupted cached version of the page
  • Firewall or antivirus interference — security software sometimes modifies page data in transit, breaking the encoding
  • Faulty proxy or VPN — a middleman between you and the website altered the compressed data

How to fix it

Try these steps in order:

  1. Clear your browser cache — this is the most common fix. Go to your browser settings, clear cached images and files, then reload the page
  2. Disable your antivirus temporarily — if clearing the cache didn’t work, your security software might be interfering. Turn it off briefly and try again
  3. Turn off your VPN or proxy — if you’re using one, disable it and reload the page to see if that was the problem
  4. Try incognito mode — this loads the page without cache or extensions, helping you narrow down the cause
  5. Flush your DNS cache — open your terminal or command prompt and run ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on Mac

When should you worry?

  • If it only happens on one site, the problem is likely on that website’s server. Not much you can do except wait
  • If it happens on many sites, something local is interfering — your antivirus, VPN, or network setup is the most likely culprit
  • If you see it on your own website, check that your server’s compression settings (gzip or Brotli) are configured correctly and that no caching layer is serving mismatched content