What 206 means
The server is sending just part of the file, the byte range the client asked for in its Range header. The Content-Range header says which part and how big the whole file is.
When servers send it
For video and audio seeking, resuming a broken download, and download managers fetching a file in several pieces at once.
Why you might see it
- A request with a
Rangeheader that the server could satisfy.
Using it as a developer
- Send
Accept-Ranges: byteson normal responses so clients know ranges work. - Each 206 must include
Content-Range(or be a multipart/byteranges response). - If the range is outside the file, reply 416 Range Not Satisfiable, not 206.
- Safari won’t play video from a server that ignores range requests, so make sure your server or CDN supports them.
If you’re visiting a website
- Nothing. It’s how video scrubbing and resumable downloads work.
Related codes
- 200 OK: The request worked and the response contains the result.
- 416 Range Not Satisfiable: The byte range asked for is outside the file.
- 304 Not Modified: Your cached copy is still up to date, so use that.
Where it’s defined
206 Partial Content is defined in RFC 9110, section 15.3.7. It’s a 2xx code, the success class: the request worked.
Other 2xx codes
200 OK · 201 Created · 202 Accepted · 204 No Content
Or search them all in the HTTP status code list.