Large File Optimization

Large File Optimization (LFO) provides better performance and reliability for delivering large files.

Features and options


What it does



Enables or disables the behavior.

LFO Type

Set the implementation type: whether to cache chunks (partial objects), or require caching of whole objects only. NetStorage always applies partial object caching when serving large objects. When caching partial objects, there is some risk of content corruption if the chunks come from a different version of the same file, for example, from different servers containing different versions. The origin needs to support byte range requests to cache partial objects.

  • Cache partial objects
  • Cache whole objects only

Minimum Filesize

Use optimization only on files larger than the specified value. Expressed as a number suffixed with a unit string such as MB or GB.

Maximum Filesize

The maximum size of files to be optimized. Expressed as a number suffixed with a unit string such as MB or GB.

Filename Policy

Select a filename policy that you want to apply. It is strongly recommended that you version or rename files when they change.

  • Files renamed when changed
  • Files not renamed when changed

Tips and best practices

  • Best practice is to use LFO only for objects larger than 100 MB. LFO is required for files over 1.8 GB in size that you serve through ​Akamai​. It is strongly recommended that you use NetStorage to serve objects larger than 1.8 GB.
  • You should apply LFO only to the specific content to be optimizedβ€”for example, to the .gz files in a particular subdirectory.
  • It is strongly recommended that you rename versions when you modify the file (use versioning) as the file name policy.
  • For more information on versioning, using your own origin rather than NetStorage and other LFO topics, see your product implementation or integration guide on the ​Control Center​ documentation pages.

Did this page help you?