What it means
The Range header asks for bytes outside the size of the resource.
Common causes
- Resuming a download whose file changed or shrank
- A range beyond the end of the file
- Corrupted partial download state
How to fix it
As a client or visitor
Restart the download without a Range header, or request a range within the size given by Content-Range.
As the site or API owner
Return Content-Range: bytes */<size> so clients can recover.
Example response
HTTP/1.1
HTTP/1.1 416 Range Not Satisfiable
Date: Tue, 07 Oct 2025 09:30:00 GMT
Server: nginx
Content-Range: bytes */146515
Content-Length: 0Specification
FAQ
› Why does wget or curl fail with 416 when resuming?
The local partial file is as large as or larger than the remote file. Delete it and download again.
› Is 416 a server bug?
Usually not; it means the requested range is invalid for the current file.