Cloudflare range requests for large downloads

On 23 October 2026, Cloudflare introduced its new implementation of Origin Range Requests. According to the announcement, the feature is available on all plans and can be enabled through a Cache Rule. For companies distributing large files, this is a useful reason to review how downloads reach their customers. It is not a promise that every portal will become faster or every hosting bill will shrink.

What changes?

A range request asks for a particular part of a file. Cloudflare can retrieve missing, cache-aligned blocks from the origin server to fulfil that request. Those blocks may be larger than the exact range requested by the browser, while the client receives the requested portion. The announcement explains the implementation.

There are boundaries to consider. Enabling the feature does not automatically make an otherwise uncacheable response cacheable. File-size limits apply to the complete object, and Cache Reserve currently does not support Origin Range Requests. Cloudflare documents these restrictions in its Cache Rules settings.

The relevant question is how your files are used. A portal dominated by small pages may have more pressing bottlenecks. Slow application queries, for example, need a different investigation from large file transfers.

What does this mean for your company?

Consider a hypothetical manufacturer offering public maintenance videos and large software packages. A field technician skips to a particular repair step in a video. Another employee resumes an interrupted download while travelling. These are examples to investigate, rather than evidence of results achieved for a particular customer.

Start with three questions. Which files account for substantial traffic? Do people usually download them completely or request selected parts? Do reported problems occur during these transfers? A trial becomes useful when the answers point to a specific issue that your team can measure.

The commercial context matters as well. Lower origin traffic does not necessarily reduce a fixed-price hosting bill. A service that charges for requests may also make the number of individual fetches relevant. Compare transferred bytes, request counts and actual contract terms together before estimating savings.

Customer portals often contain confidential material alongside public resources. Access controls must remain a prerequisite for caching decisions. Public product files are a more suitable starting point than customer-specific contracts or invoices. Cloudflare's default cache behaviour considers factors such as Cache-Control and cookies; custom rules need to remain consistent with the intended access model.

Recommended next steps

We recommend a small trial with a documented baseline and a clear owner:

Choose representative files. Start with a few public, versioned resources under a narrowly defined path. Involve both the business team and the person responsible for operations.
Record the baseline. Measure download start times, interruptions, errors, origin bytes and request counts. Record the device, connection and file version used for each comparison.
Check the prerequisites. Have your technical team verify byte-range support at the origin. Cloudflare's range request reference describes the relevant request and response paths.
Limit the configuration change. Apply it only to the selected resources. Keep the previous configuration and document how to restore it.
Reproduce ordinary usage. Test first-time and repeated requests, simultaneous downloads, interrupted transfers, resumption and replacement with a new file version.
Test permissions separately. Include both authorised and unauthorised requests. A successful download alone does not demonstrate that access checks are correct.
Evaluate comparable conditions. Compare similar traffic and network conditions, then ask users whether the difference helps their work. Retain the change only when the benefit is demonstrable.

Include maintenance in the decision. Who checks the rules after a portal release? Who investigates transfer errors? Which measurements should trigger an investigation? Recording these responsibilities makes the result easier to sustain when staff or suppliers change.

Also distinguish the location of the origin server from the processing performed by other services. Hosting in Germany alone does not answer every question about the wider delivery architecture. Review the actual setup against your organisation's existing data-location requirements before expanding the trial.

How Sadeem helps

Sadeem can assess download delivery, portal permissions and hosting as one connected system. We can prepare a limited trial, evaluate its measurements and incorporate suitable monitoring into ongoing operations. The objective is a useful improvement for your staff and customers, supported by evidence from your own workload.

A free initial consultation is an opportunity to identify suitable files, agree on success criteria and decide whether a technical trial is proportionate to the problem.

Sources

Information checked on 26 October 2026.