CDN Products
Two delivery products on one network and one account: Anycast CDN and Video CDN. HLS Streaming runs on Anycast, Files on Demand runs on either one, and Cloud Storage is the object storage you can point any of them at. They differ in where your files live and how they are served, not in the price per terabyte.
Not sure which one fits? An engineer replies within 3 business hours · See pricing
Two products, four ways to deliver, one network
Anycast CDN
Video CDN
HLS Streaming CDN
Files on Demand
Anycast CDN
Classic pull caching for static assets: images, scripts, styles, downloads. Point a zone at your origin and we cache at the edge, answering with a 96%+ average hit rate, so your origin serves each file roughly once per TTL per region instead of once per user.
- Files from 20 KB icons to 50 GB installers, on the same tiers and with no size surcharge.
- On-the-fly image resizing is included, so a single source image serves every layout.
- 27 ms in Europe and 24 ms in North America, measured June 2026, with purge across the network in seconds.
Video CDN
Your video library is replicated inside the CDN and served from the closest, least-loaded node. After import your origin can leave the delivery path entirely, which is what separates Video CDN from a plain pull cache.
- Replicated across Europe, Asia and America, so playback does not depend on which continent the viewer sits on.
- 97%+ segment cache hit sustained on production VOD libraries.
- Permanent Cache pins the library at the edge for $0.02/GB a month, first 500 GB included.
- Auto import from S3, Swift, Rsync, Wasabi, Cloud Storage or any HTTP origin.
- MP4, MKV, WebM, MOV and more, up to Full HD and 4K.
Cloud Storage for CDN
Not a delivery product: replicated object storage you point a delivery zone at. Use it when you would rather not keep your own storage online just to feed the CDN.
- Use it as the origin for any delivery zone, so your own storage does not have to stay online.
- Replicated across regions, with content held on SSD-based storage.
- Signed URLs and token authentication apply to stored content the same way they apply to delivery.
Files on Demand
Import your catalogue once and the CDN holds the copies. Anycast pulls and caches while your origin stays the source of truth; Files on Demand imports and holds, so the origin can go quiet.
- Lazy import fetches a missing file from a proxy URL you nominate, so the catalogue fills as it is used.
- Signed URLs with an expiry, IP binding and referrer checks on every zone.
- Documents, archives, executables and media up to 50 GB per file.
HLS Streaming CDN
Delivery for streams you have already encoded: HLS, LL-HLS and DASH from your own media server, with manifests and segments cached on separate rules. Typical latency our layer adds is 2-4 seconds, where standard HLS sits at 20 to 40.
- You bring the media server or packager: we deliver HLS and DASH output, we do not transcode or generate manifests.
- Live manifests run on near-zero TTL while segments are cached as immutable, so freshness and cache hit stop fighting each other.
- Works with Wowza, NGINX RTMP, FFmpeg and players supporting LL-HLS.
Image optimization, included
Not a separate product and not a separate line on the invoice. Image resizing and compression run on the delivery layer you are already paying for: one source image, resized on the fly to whatever the layout asks for, so you ship fewer bytes without keeping a second copy of anything.
- Resize on the fly to match any screen size or layout, from one source file.
- Compression that cuts transferred bytes, which shows up directly in the terabytes you are billed for.
- Included with Anycast CDN delivery at no extra charge.
Questions buyers ask about BlazingCDN products
BlazingCDN runs two delivery products on one network and one account: Anycast CDN for pull caching and Video CDN for replicated video libraries. HLS Streaming CDN and Files on Demand CDN run on top of them, Cloud Storage can act as the origin, and image processing is included. Every product uses the same price per TB.
How much do Anycast CDN and Video CDN cost at 200 TB?
BlazingCDN charges the same per-TB rate for Anycast CDN and Video CDN, so 200 TB a month costs $765 on either product (as of October 2026). Tiers are progressive: $5 per TB up to 5 TB, $4.50 up to 25 TB, $4.00 up to 100 TB and $3.50 up to 500 TB. The products differ in where files live, not in the delivery price.
Video CDN adds one optional storage line. Permanent cache includes the first 500 GB, then costs $0.02 per GB per month. For example, a 3,000 GB library pinned at the edge adds 2,500 billable GB, or $50 a month. Cloud Storage used as an origin costs $0.015 per GB per month. There are no request fees, no regional multipliers and no setup fee on any product.
What is the difference between Anycast CDN and Video CDN?
BlazingCDN Anycast CDN is a pull cache, while Video CDN replicates the whole library inside the network, so the origin can leave the delivery path. Anycast CDN fetches a file from your origin on the first request, caches it at the edge and answers repeat requests with a 96%+ average cache hit ratio. Your origin stays the source of truth and must stay online.
Video CDN imports the library from S3, Swift, Rsync, Wasabi, Cloud Storage or any HTTP origin. Copies are replicated across Europe, Asia and America and served from the closest, least-loaded node. Permanent cache costs $0.02 per GB per month after the first 500 GB (as of October 2026). Choose Anycast CDN for images, scripts, styles and mixed downloads. Choose Video CDN for MP4, MKV, WebM and MOV catalogs up to 4K. For example, a 4 TB film archive that rarely changes fits Video CDN.
Does BlazingCDN transcode video or generate HLS manifests?
No, BlazingCDN does not transcode video or generate manifests: the HLS Streaming CDN delivers HLS, LL-HLS and DASH output that your own media server or packager has already produced. Edge compute, WebSockets and HTTP/3 are not offered either. The products are delivery layers for files and segments that already exist.
Within delivery, the streaming setup is specific. Live manifests run on a near-zero TTL, while segments are cached as immutable. With LL-HLS, the delivery layer typically adds 2 to 4 seconds, where standard HLS sits at 20 to 40 seconds. The HLS Streaming CDN works with Wowza, NGINX RTMP, FFmpeg and players that support LL-HLS. For example, a broadcaster encoding four renditions in FFmpeg points the CDN at that packager output. Billing follows the same tiers as every product, from $5 down to $2.50 per TB (as of October 2026).
Should I use Files on Demand or Anycast CDN for downloads?
BlazingCDN Files on Demand CDN imports and holds your files, while Anycast CDN pulls and caches them, and both deliver files up to 50 GB at the same per-TB rate. Files on Demand runs on either delivery product. Lazy import fetches a missing file from a proxy URL you nominate, so the catalog fills as users request it. After import, the origin can go quiet.
Anycast CDN keeps the origin as the source of truth, which suits catalogs that change often. Files on Demand suits large, stable catalogs such as installers, archives, executables and documents. Every zone supports signed URLs with an expiry, IP binding and referrer checks. For example, a game studio shipping a 40 GB build can import the build once and stop serving it from origin. Pricing starts at $5 per TB and reaches $2.50 per TB at volume (as of October 2026), with no size surcharge.
Is image resizing a separate charge on BlazingCDN?
No, BlazingCDN includes image processing with Anycast CDN delivery at no extra charge, and the invoice shows only delivered terabytes. Image resizing and compression run on the delivery layer. One source image is resized on the fly to whatever the layout requests, so you never store a second copy of each size.
Compression reduces transferred bytes, and fewer bytes means fewer billed terabytes. Every gigabyte saved is a gigabyte not billed at the $5 to $2.50 per TB rate (as of October 2026). Resized variants are cached like any other file, so repeat requests come from the edge. Files from 20 KB icons to 50 GB installers sit on the same tiers. For example, a store serving four image sizes for each product keeps one source file per image at origin, and the CDN produces the other three on request. Purge clears outdated variants when the source image changes.