HTTP 206 Partial Content — What It Means & How to Fix It

What Does This Error Mean?

HTTP 206 Partial Content means the server is returning only a portion of the requested resource, not the full file. This is completely normal and intentional — video players, download managers, and streaming services use 206 to request specific chunks of a file. 206 is a success code, not an error — it powers the ability to seek video, resume downloads, and stream content efficiently.

Affected Models

All web browsers
All web servers
REST APIs
Mobile apps
Desktop applications

Common Causes

Video player is requesting a specific portion of a video file for streaming
Download manager is resuming a partially completed file download
Browser is using range requests to load large files in chunks
Audio player is seeking to a specific timestamp in a large audio file
CDN or media server is delivering content via adaptive bitrate streaming

How to Fix It

If you are a regular user, seeing HTTP 206 in developer tools means video streaming or file downloads are working correctly.

YouTube, Netflix, Spotify, and virtually all media streaming services use 206 for every video or audio play.
If a video cannot be seeked forward (clicking ahead in the timeline does not work), the server may not support Range requests.

Range request support is required for seek functionality — a 200 response to a range request forces the full file to load.
If a download cannot be resumed after interruption, check that the server returns 206 and includes the Accept-Ranges header.

A server that does not support range requests will restart downloads from the beginning after interruption.
If you are a developer, add the Accept-Ranges: bytes header to responses for large files to advertise range support.

When a client sends a Range: bytes=X-Y request, respond with 206 and the Content-Range header specifying what portion is included.
For video streaming servers, ensure the server correctly handles Range requests with overlapping or out-of-order chunk requests.

Adaptive bitrate streaming (HLS, DASH) requests many small ranges simultaneously — the server must handle concurrent range requests.
If serving partial content from a CDN, confirm the CDN correctly passes Range headers to the origin server.

Some CDN configurations strip Range headers, causing 200 responses instead of 206 and breaking video seeking.

When to Call a Professional

HTTP 206 is a normal success code — no action or professional help is needed. Developers should implement Range request support (Content-Range header) if their server delivers large media files. A server that returns 200 for range requests instead of 206 prevents video seeking and download resumption.

Frequently Asked Questions

Why do video streaming sites use HTTP 206 instead of 200?

Videos are large files — downloading the entire file before playing would cause huge delays. HTTP 206 allows the player to request only the part it needs right now, and seek to other parts on demand. This is what allows you to skip to any point in a YouTube video instantly.

Can HTTP 206 cause video buffering problems?

206 itself is not a cause of buffering — it is the mechanism for delivering video efficiently. Buffering is caused by slow internet connection, server overload, or poor CDN performance. If your video buffers frequently, the issue is bandwidth or server capacity, not the 206 response code.

What is the difference between HTTP 200 and HTTP 206 for file downloads?

A 200 response delivers the entire file from the beginning, every time, with no resume capability. A 206 response delivers the specific byte range requested, allowing downloads to resume from where they left off. For large file downloads, 206 support dramatically improves the user experience.