CDN for large files
Big objects need an edge, not a bigger origin pipe.
Datasets, zips, video masters and installers saturate origin bandwidth long before they saturate a distributed cache.
Cache large objects at Cloud CDN with long TTLs. Enable large-file optimisation and Origin Shield. Version objects so replacements do not require a global purge.
Why teams use Aptranet
How it works with Aptranet
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Built for large objects
The same CDN that serves websites is optimised for large-file delivery.
200+ Tbps behind the hostname
Concurrent downloads are absorbed at 210+ locations.
Origin Shield on first byte
Edges share the miss path instead of opening the origin independently.
How to set it up
Validate your setup before production changes.
Create your Cloud CDN distribution, test delivery on its Aptranet hostname, then update production DNS when the configuration is ready.
- 1Connect the object origin
Pull a files host or origin disk over HTTPS.
- 2Cache with long TTLs
Version filenames when content changes.
- 3Enable Origin Shield
Protect origin throughput on first-byte and popular objects.
- 4Optionally token-protect paths
Paid or internal objects should not be world-readable.
Outcomes
What changes once the hostname is on Aptranet.
- Large files are served from the edge
- Origin bandwidth is reserved for misses
- Versioned objects skip purge
- Private objects can require a token
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently asked questions
No. Any large HTTPS object — zips, datasets, installers, game depots — can use the same path.
Range requests are a normal part of large-file delivery. Validate behaviour on a test object.
Do not recompress already compressed binaries. Use Brotli/Gzip for text assets, not zips or media.
Purge the URL or, better, publish a new versioned URL and update the pointer.