HTTP 416 Range Not Satisfiable — What It Means & How to Fix It

The HTTP 416 Range Not Satisfiable status code indicates the server cannot satisfy the byte range specified in the Range header of the request. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Previously known as "Requested Range Not Satisfiable.". This occurs when the requested byte range is outside the size of the resource.. The response includes a Content-Range header showing the actual size of the resource.. Common when resuming downloads with an incorrect byte offset.. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: The Range header specifies bytes beyond the end of the resource.. A download resume attempt uses an offset larger than the file size.. The file was modified or replaced since the last partial download.. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Check the Content-Range header in the response to see the actual resource size.. Restart the download from the beginning if the file has changed.. Verify the byte range in your Range header is within the resource bounds.. Handle this error gracefully in download managers by falling back to a full download.. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.