{"id":16076,"date":"2025-07-24T16:48:43","date_gmt":"2025-07-24T14:48:43","guid":{"rendered":"https:\/\/surver.nl\/?post_type=kennisbank&p=16076"},"modified":"2025-07-30T09:47:09","modified_gmt":"2025-07-30T07:47:09","slug":"status-code-206","status":"publish","type":"kennisbank","link":"https:\/\/surver.nl\/en\/kennisbank\/statuscode-206\/","title":{"rendered":"What does status code 206 Partial Content mean?"},"content":{"rendered":"
\"Status<\/figure>\n\n\n\n

You have status codes like 200 that say: all good, here's the full content. But sometimes you don't want to retrieve everything at once. Think of a video you start halfway through. Or a large download that was momentarily interrupted. In those cases, the server only sends back a portion. So then you don't get a 200, but a 206.<\/p>\n\n\n\n

It sounds like an edge case, but it is not. The 206 appears regularly in modern websites and applications, especially those working with media files or smart loading methods.<\/p>\n\n\n\n

Specifically, what does 206 mean?<\/h2>\n\n\n\n

In short, the 206 status indicates that the request succeeded, but only part of the requested data was returned. And this is done that way on purpose. The client itself requested a piece, and the server says: fine, here's only that part.<\/p>\n\n\n\n

Technically, this is done with a Range header. The browser (or tool) then says something like: give me byte 1,000 to 2,000 of this file. And if the server supports that, a 206 Partial Content comes back nicely, with exactly that piece of data.<\/p>\n\n\n\n

Where do you see this reflected?<\/h2>\n\n\n\n

You won't encounter it when opening a regular web page. There, you'll just get a 200 back. But as soon as you work with large files, or with media you can flush, that changes.<\/p>\n\n\n\n

For example:<\/p>\n\n\n\n