How to Fix ERR_CONTENT_DECODING_FAILED in Chrome

By ErrorFix · Updated October 26, 2026 · 7 min read

What ERR_CONTENT_DECODING_FAILED means

ERR_CONTENT_DECODING_FAILED means Chrome received a web page in a compressed format and could not unpack it. To keep pages fast, servers shrink them before sending — usually with gzip, deflate, or Brotli compression — and your browser expands them back on arrival. This error appears when that deal breaks down: the data arrives damaged, compressed twice, or labeled with a compression format that does not match what was actually sent. Rather than display a garbled page, Chrome gives up and shows the error instead.

Think of it like receiving a zipped file that your unzip tool refuses to open. Either the file itself is damaged, it was zipped twice by mistake, or the label on the package says one format while the contents are another. Any of those three problems produces the same result: nothing opens. The useful question is where the damage happened — in your browser's stored copy, in an extension or VPN rewriting the traffic, or on the website's server — and the steps below narrow that down one layer at a time, starting with the easiest fixes first.

Common causes

• Corrupted browser cache or cookies: a half-saved compressed copy of the page makes Chrome fail every time it tries to reuse it.
• Extensions that modify web requests: ad blockers, privacy tools, and header-editing extensions can change what the browser asks for or what the server sends back, breaking the compression handshake.
• VPN or proxy interference: a VPN or proxy that rewrites headers on the way through can strip or alter the encoding information, leaving Chrome with data it cannot unpack.
• Misconfigured server compression: a site whose server compresses a page twice, or labels it with the wrong encoding, sends pages no browser can decode.
• Outdated browser or damaged network stack: an old Chrome version may lack support for a newer compression format, and stale DNS or socket state can corrupt the transfer.

How to fix ERR_CONTENT_DECODING_FAILED — step by step

Work through these fixes in order. Most cases are fixed by step 1, 2, or 3.

1. Hard-refresh and test the page in incognito and another browser. Start with the fastest checks, because a decoding failure is often a one-off glitch rather than a broken setting. Press Ctrl + F5 on Windows (Cmd + Shift + R on a Mac) to force Chrome to fetch a fresh copy of the page instead of reusing its stored one. Then open an Incognito window with Ctrl + Shift + N and load the same page there: incognito skips your cache, cookies, and extensions, so a page that loads there points the blame at your cached data or an extension. Finally, try the page in a different browser, such as Edge or Firefox. If it fails everywhere, the problem is almost certainly the website's server or your network, not Chrome.
2. Clear Chrome's cache and cookies. A corrupted cached copy is the most common cause of this error: Chrome tries to unpack a half-saved compressed file and fails. Press Ctrl + Shift + Delete on Windows (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Close Chrome completely, reopen it, and reload the page. Clearing cookies signs you out of websites, so keep your passwords handy, but it also removes any stored cookie that was telling the server to send a compression format your browser cannot handle.
3. Disable extensions, especially ones that modify requests. Extensions that touch web traffic — ad blockers, privacy tools, script blockers, download managers, and header-editing tools — can change what the browser asks for or what the server sends back, and that mismatch breaks decoding. Type chrome://extensions in the address bar and toggle every extension off, then reload the page. If it loads, re-enable the extensions one at a time, reloading after each, until the error returns and you have found the culprit. Pay special attention to any extension that edits headers or blocks content, since those are the ones most likely to interfere with compression.
4. Disconnect your VPN or proxy, then flush DNS and Chrome's socket pools. A VPN or proxy sits between Chrome and the website, and if it alters the compression headers on the way through, Chrome receives data it cannot unpack. Disconnect your VPN completely — not just pause it — and turn off any manual proxy: on Windows, open Settings, go to Network and internet, then Proxy, and turn off Use a proxy server; on a Mac, open System Settings, go to Network, select your connection, click Details, then Proxies, and uncheck every option. Next, flush DNS: open Command Prompt as Administrator and run ipconfig /flushdns, or on a Mac open Terminal and run sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. Finally, flush Chrome's socket pools by typing chrome://net-internals in the address bar, opening Sockets in the left menu, and clicking Flush socket pools. Restart Chrome and retest.
5. Check the page's encoding header and test with compression off. If the error survives the steps above, look at what the server is actually sending. Press F12 to open DevTools, go to the Network tab, reload the page, and click the failed request. In the Response Headers section, look for content-encoding: a value of gzip, deflate, or br is normal, but a page that claims one encoding while arriving in another — or that was compressed twice by a misconfigured server — cannot be decoded. As a visitor, you can confirm the diagnosis with a header-editing extension: add a request header named accept-encoding with the value gzip;q=0,deflate;q=0 to tell the server to send the page uncompressed, then reload. If the page loads, compression is definitely the trigger. Remove the test extension afterward, since running without compression permanently is only a workaround, not a fix.
6. Update Chrome, reset its settings, and check whether the site itself is at fault. An outdated browser can lack support for a newer compression format, so update Chrome first: open the three-dot menu, go to Help, then About Google Chrome, and let it install any pending update. If the error continues, reset Chrome by going to Settings, then Reset settings, then Restore settings to their original defaults — this clears extension configurations and custom settings without deleting your bookmarks or saved passwords. Finally, decide whether the fault is yours or the site's: if the error appears on one website only, on every device and network you try, that site's server is misconfiguring its compression, and only its owner can fix it. Contact the site's support team, mention the exact error name, and note that its content-encoding setup needs checking.

Did this fix it? Quick checklist

• The page loads without the decoding error
• The page loads in an incognito window
• The page loads with extensions disabled
• The page loads with the VPN disconnected

If the page loads with compression disabled but fails with it on, the trigger is confirmed as a compression mismatch — and if that happens on one site only, the fix belongs to the site's server team, not to your browser. If the error follows you across browsers, devices, and networks, check whether your internet provider or a network-level filter is altering traffic, and try your phone's mobile data as a clean comparison. And if the error appears on many different sites at once, a system-wide cause is likelier: a VPN, a proxy, or security software rewriting traffic is the first place to look.