416 HTTP Origin: Network Last updated 14 Oct 2026

HTTP 416 Range Not Satisfiable

The client asked for a byte range (Range: bytes=…) that lies outside the file — usually a resumed download of a file that changed or is already complete.

Exact message you may see 416 Range Not SatisfiableRequested Range Not SatisfiableRange Not SatisfiableThe requested range is not satisfiable
Explore the map of this error Full error map →
Seen on: REST API

Meaning

Download managers, video players and resumable uploads use Range headers to fetch parts of a file. If the requested start is beyond the file’s size — the file shrank, was replaced, or the download is already finished — the server answers 416 with Content-Range: bytes */size.

Common causes

  • Resuming a download of a file that was replaced or truncated
  • Partial local file already complete or larger than the remote file
  • Wrong range math in custom code (off-by-one, end beyond size)
  • CDN cached a different version than the origin

⚡ Quick fix

  1. Delete the partial file and download again
  2. Request a range within Content-Length
  3. Purge the CDN cache if versions differ

Detailed fix by platform

curl

  1. bash
    curl -I https://example.com/file.zip                 # check Content-Length
curl -C - -O https://example.com/file.zip           # resume correctly (or rm the partial file)

wget

  1. rm file.zip && wget https://example.com/file.zip

How to diagnose

  1. Sizes — Local partial size vs remote Content-Length
  2. Header — Range sent vs Content-Range returned
  3. Version — ETag/Last-Modified changed?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

100 — HTTP 100 Continue (HTTP)100103 — HTTP 103 Early Hints (HTTP)1031040 — Cloudflare Error 1040 / 1041: Invalid request header modification (Cloudflare)1040411 — HTTP 411 Length Required (HTTP)411412 — HTTP 412 Precondition Failed (HTTP)412413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413417 — HTTP 417 Expectation Failed (HTTP)417428 — HTTP 428 Precondition Required (HTTP)428416

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.