Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud CDN
    • Overview
    • Points of presence
    • Resource
    • Origins and origin groups
      • Overview
      • Host header
      • Content segmentation
      • Origin shielding
      • Following request redirects
      • Hiding of origin headers
    • Request redirect
    • Content caching
    • Secure tokens
    • IP-based access policy
    • Dedicated IP addressing
    • Location rules
    • Log export
    • Labels
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Request logs
  • Audit Trails events
  • Release notes
  • Troubleshooting
  1. Concepts
  2. Data exchange between the CDN and origins
  3. Content segmentation

Content segmentation

Written by
Yandex Cloud
Updated at July 9, 2026
View in Markdown

You can segment CDN content: request it from origins and store it on servers in parts. Segmentation is enabled in the resource settings.

If the setting is enabled:

  • Files with a size of 10 MB or more are requested from origins in parts. The maximum size of each part is 10 MB.

    For example, a 42 MB file will be split into four 10 MB parts and one 2 MB part.

    All parts are requested in parallel, each in its own thread. This enables you to download the entire file and start sending it to the client faster.

    Warning

    For segmentation to work correctly, origins must support partial GET requests with the Range header. Regardless of which origin within a group a file part is requested from, responses containing this file part must have the same Content-Length and ETag header values.

  • To send a whole file to the client, all the parts are combined back into one file before sending.

  • If caching on CDN servers is enabled, the file parts will continue to be stored on the server.

Useful linksUseful links

  • Instructions for enabling file segmentation.

Was the article helpful?

Previous
Host header
Next
Origin shielding
© 2026 Direct Cursus Technology L.L.C.