Chrome network error · -320 · HTTP

ERR_INVALID_RESPONSE

The server sent an answer Chrome could not use as an HTTP response: broken headers, a wrong content length or garbage instead of a page.

Chromium's description

The server's response was invalid.

Chrome shows it as net::ERR_INVALID_RESPONSE, error -320. puppeteer and Playwright report the same name when a page fails to load in Chromium.

Common causes

A server or application error that writes output before or instead of the headers.
A PHP or other script that crashes halfway through.
A proxy or antivirus that alters the traffic.
A file served with broken compression or encoding.

How to fix ERR_INVALID_RESPONSE

Reload and clear the cache and cookies of the site.
Try another browser or network to rule out a local proxy.
Site owners: check the response with curl -v and the server error logs.

ERR_INVALID_RESPONSE in the screenshot API

When the page itself fails to load with ERR_INVALID_RESPONSE, the API answers 502 with the message The target website could not be loaded (ERR_INVALID_RESPONSE). (target_unreachable). Not billed.

Only the page's own load can fail a render. An image, script or frame of the page that fails with a network error does not: the page is captured as the browser shows it without that resource.

Check whether a website loads

Device

Format

Full page Block ads

Rendered in a real browser with cookie banners hidden. Takes 5–30 seconds.

Frequently asked questions

What does ERR_INVALID_RESPONSE mean?

The server sent an answer Chrome could not use as an HTTP response: broken headers, a wrong content length or garbage instead of a page.

How do I fix ERR_INVALID_RESPONSE?

Reload and clear the cache and cookies of the site.

Is a screenshot that fails with ERR_INVALID_RESPONSE billed?

No. Requests the screenshot API answers with an error are not billed.

Other common errors

ERR_CONNECTION_RESET ERR_CONNECTION_REFUSED ERR_CONNECTION_TIMED_OUT ERR_CACHE_MISS ERR_ADDRESS_UNREACHABLE ERR_TIMED_OUT ERR_SSL_PROTOCOL_ERROR ERR_CONNECTION_CLOSED ERR_QUIC_PROTOCOL_ERROR ERR_NAME_NOT_RESOLVED ERR_TOO_MANY_REDIRECTS ERR_NETWORK_CHANGED

All 249 Chrome network errors · Screenshot API errors

Screenshot API

Take screenshots from your code

screenshotbase renders any website in a real browser and returns the image: full page or viewport, any device size, retina, from 100+ countries, with cookie banners and ads hidden.

/v1/take documentation Screenshot API All documentation

300 free screenshots every month. No credit card required.

GET https://api.screenshotbase.com/v1/take?url=https://example.com&full_page=true

# Response: the image (PNG, JPG, WebP or GIF)
curl -G "https://api.screenshotbase.com/v1/take" \
  --data-urlencode "url=https://example.com" \
  -d viewport_width=1280 -d viewport_height=800 \
  -d format=png \
  -H "apikey: YOUR-API-KEY" \
  -o screenshot.png

More free tools

Website screenshot Capture any page as an image. Full page screenshot Capture a whole page, top to bottom. Mobile website screenshot See a site on iPhone, Android and iPad. URL to PDF Save any web page as a PDF. URL to markdown Turn a web page into markdown. HTML to PDF Print your own HTML as a PDF. HTML to image Render HTML and CSS as a PNG, JPG or WebP. HTML to markdown Turn HTML into clean markdown. URL to PNG Save a web page as a PNG image. URL to JPG Save a web page as a JPG image. Scrolling screenshot One long image of a page, no stitching. HTML to PNG Render HTML as a lossless PNG. HTML to JPG Render HTML as a compact JPG. Viewport sizesScreen sizes and pixel ratios of 46 devices. ErrorsChrome network errors and screenshot API errors, with fixes.