The Range HTTP request header indicates the parts of a resource that the server should return. Several parts can be requested at the same time in one Range header, and the server may send back these ranges in a multipart document. If the server sends back ranges, it uses the 206 Partial Content status code for the response. If the ranges are invalid, the server returns the 416 Range Not Satisfiable error.

A server that doesn't support range requests may ignore the Range header and return the whole resource with a 200 status code. Ignoring the Range header is equivalent to Accept-Ranges: none, so the Accept-Ranges response header is rarely used for this purpose.

Currently only bytes units are registered which are offsets (zero-indexed & inclusive). If the requested data has a content coding applied, each byte range represents the encoded sequence of bytes, not the bytes that would be obtained after decoding.

The header is a CORS-safelisted request header when the directive specifies a single byte range.

Header type Request header
Forbidden header name no


Range: <unit>=<range-start>-
Range: <unit>=<range-start>-<range-end>
Range: <unit>=<range-start>-<range-end>, <range-start>-<range-end>
Range: <unit>=<range-start>-<range-end>, <range-start>-<range-end>, <range-start>-<range-end>
Range: <unit>=-<suffix-length>



The unit in which ranges are specified.


An integer in the given unit indicating the start position of the request range.


An integer in the given unit indicating the end position of the requested range. This value is optional and, if omitted, the end of the resource is used as the end of the range.


An integer indicating the number of units at the end of the resource to return.


The following examples show how to make requests using the Range header for CORS-safelisted requests, and for requesting multiple ranges. Other examples can be found in the HTTP range requests guide.

Single byte ranges and CORS-safelisted requests

The Range header is a CORS-safelisted request header when the value is a single byte range. This means that it can be used in cross-origin requests without triggering a preflight request, which is useful for requesting media and resuming downloads.

The following example requests the first 500 bytes of a resource:

Range: bytes=0-499

To request the second 500 bytes:

Range: bytes=500-999

Omitting the end position requests all remaining units of the resource, so the last 100 bytes of a resource with a length of 1000 bytes can be requested using:

Range: bytes=900-

Alternatively, if it's unknown how large a resource is, the last n bytes can be requested using a suffix range of -n:

Range: bytes=-100

Requesting multiple ranges

Given a resource with a length of 10000 bytes, the following example requests three separate ranges; 200-999 (800 bytes), 2000-2499 (500 bytes), and finally 9500-. The ranges-specifier value 9500- omits an end position which indicates that all bytes from 9500 onward are part of the third range (500 bytes).

Range: bytes=200-999, 2000-2499, 9500-

This example requests the first 500 and last 500 bytes of the file. The request may be rejected by the server if these ranges overlap (if the requested resource was less than 1000 bytes long, for instance).

Range: bytes=0-499, -499


HTTP Semantics
# field.range

Browser compatibility

BCD tables only load in the browser

See also