Video CDN
Your video library, replicated inside the CDN and served to viewers without touching your origin. Built for media companies that move large files at scale.
From $5/TB down to $2.50/TB, one rate across all regions · 14-day testing period on real traffic · $25 monthly minimum waived · Engineer reply within 3 business hours
Built for teams that deliver heavy media
OTT & VOD platforms
Segment-aware delivery for HLS/DASH libraries. In production workloads, VOD segment cache hit rates consistently exceed 97%.
Short-video & UGC apps
Millions of 1-30 MB MP4s with algorithmic traffic spikes. Cache warming API lets your trending system pre-position viral clips; production libraries sustain 95%+ hit rates end to end.
Software & Game distributors
Installers, patches, DLC: the same in-CDN replication keeps origin load under 3% of total demand during peak patch windows.
Video CDN Keeps the Files. Your Origin Gets a Rest.
Files are replicated across the network rather than cached on demand, so delivery no longer depends on your origin being awake, and two familiar lines drop off the invoice.
Watch the ladder switch, served straight from Video CDN
Served fromSix files in one folder
One URL for the whole ladder
/media=hls/multi=…/_TPL_.mp4.m3u8 returns a multi-variant playlist; the player picks the rendition. Segments cut at request time
https://vcdn10002491.blazingcdn2.net/media=hls4/multi=640x360:360p:YXZjMS42NDAwMjg=,960x540:540p,1280x720:720p,1920x1080:1080p,2560x1440:1440p,3840x2160:2160p/_TPL_.mp4.m3u8 · Footage: Pexels, free licence 
How Video CDN differs from a regular pull CDN
- Origin offload by design. After import, your origin can leave the delivery path entirely, and it also stays shielded from public traffic.
- Auto import. Provide the origin link once; missing files are fetched automatically from your storage or a fallback proxy URL.
- Full range-request support (RFC 7233), so downloads resume and multi-GB files fetch in parallel chunks.
- Purge in seconds across the full network, plus a cache warming API for pre-positioning content before a release.
Anycast CDN
Video CDN | VOD
HLS Streaming CDN
Things you would otherwise build yourself
Multi-bitrate streaming
Clipping
Track selection
Also on the same zone: delivery rate control to cap how fast a single client drains a file, intensity limits per resource, and a defined answer for requests to files that do not exist.
Five requests your player can make, answered at the edge
- «Give me the 720p rendition» · multi-bitrate ladders are served straight from the edge, the player switches without your origin.
- «Give me seconds 90 to 120» · clipping returns just that fragment, no second encode and no extra copy in storage.
- «Give me the Spanish audio track» · track selection picks the audio or subtitle stream at request time.
- «Do not let one client drain the file at full speed» · delivery rate control and per-resource intensity limits.
- «The file is gone, what now?» · a defined answer for requests to files that do not exist, instead of a random error.
Playback on one side, control on the other
Playback
- Multi-bitrate streaming, every rendition from the edge
- Track selection: audio language and subtitles per request
- Clipping: any time range without a second encode
- MP4, MKV, WebM, MOV, up to Full HD and 4K
- HLS and DASH delivered as you produced them
Control
- Delivery rate control per file and per client
- Intensity limits per resource
- Defined behaviour for requests to missing files
- Force a download instead of in-browser playback
- CORS headers managed per zone
Seamless Video Playback on Any Device
BlazingCDN Video CDN is optimized for streaming across multiple devices, so playback stays smooth whatever the viewer is using.
- Cross-Device Support: desktop, mobile and smart TV. Files are delivered in MP4, WebM and MOV containers, up to Full HD and 4K.
- Streaming Protocols: HLS and DASH, so the player picks the right rendition for current network conditions.
Three ways to get your library in
Pre-import
Lazy import
Import API
Sources we import from today: S3, Swift object storage, Rsync daemon, Wasabi, BlazingCDN Cloud Storage and any HTTP origin. Import documentation →
Moving a 200 TB library, step by step
- Day 0 · You give us read access to the bucket. S3, Swift, Rsync, Wasabi or Cloud Storage, whichever you already run.
- Day 1 to 3 · We replicate the catalogue inside the CDN. Your origin serves the import, not your viewers, so nothing changes for them yet.
- Day 3 · You point the player hostname at us and watch both CDNs side by side for as long as you want.
- After that · Origin leaves the delivery path. New titles arrive through the import API with a callback per file.
Whatever your storage is, we already read it
Sources we pull from
- Amazon S3 and S3-compatible buckets
- Swift object storage
- Wasabi, with a step-by-step guide
- Rsync daemon
- BlazingCDN Cloud Storage
- Any HTTP origin you already serve from
How the import runs
- Pre-import: the whole catalogue lands before launch
- Lazy import: the first request brings the file in
- Import API: your pipeline pushes new titles
- Callback per file, so your system knows when it is ready
- Manual import from the panel for one-off uploads
- Import script for bulk migrations
Eleven locks, three layers
The link itself
- Signed URLs, validated at the edge
- Partial signing, when only part of the path is secret
- URL encryption, so the real path never leaves your app
- URL TTL, the link dies on schedule
Who is asking
- URL bound to a single IP address
- Referer check, so the link only works on your pages
- Cookie check, plus an extended mode for stricter sessions
- Geoblocking by country, and HTTPS-only enforcement
How much they take
- Limit how many IPs may use one URL
- Uniquing downloads protection against mass ripping
- Delivery rate and intensity caps per resource
- Googlebot bypass, so SEO still sees what it should
Five ways paid video leaks, and what stops each one
- Someone pastes the link into a forum · signed URL with a TTL, dead within minutes.
- Someone shares their session with ten friends · URL bound to one IP, plus a cap on how many addresses may use it.
- Another site embeds your player and sells your content · referer check, so the file only plays on your own domains.
- A script rips the whole catalogue overnight · uniquing downloads protection with delivery rate and intensity caps.
- Content must not play in some countries · geoblocking at the edge, with HTTPS enforced and the real path encrypted.
The full protection stack
- URL signature, full or partial
- URL encryption
- URL TTL protection
- URL to IP binding
- IP per URL limitation
- Referer check
- Cookie check, standard and extended
- Uniquing downloads protection
- Geoblocking by country
- HTTPS enforced, insecure requests refused
- Googlebot bypass for indexable content
- Secrets managed per resource
What you get
Content protection
Signed URLs (HMAC + expiry), token auth, referrer/UA filters, geo restriction, delivery of DRM-encrypted segments.
Permanent Cache
Keep your library pinned at the edge: $0.02/GB per month, first 500 GB included.
Spike resilience
Request coalescing and origin shield absorb premiere-night bursts without manual scaling.
It fits what you already run
KVS platforms
Players, storage, domains
Coming from Bunny?
There is a step-by-step migration guide from Bunny Video CDN, written for teams that want to move without a delivery gap. Read the guide →
You can see what the edge is doing
- Raw logs · every request line, delivered for your own pipeline instead of a dashboard you cannot query.
- Statistics API · traffic, hits and misses per resource, pulled straight into your monitoring.
- Resource observability · see what each zone is doing right now, before a viewer tells you.
- Traffic calculation · work out what a month costs from your own numbers, not from an estimate.
Test CDN Speed Across Top Regions
Avg. Download Speed
Latency
Test link
Four teams, written up in full
OTT provider, multi-region
Playback quality drifted between regions and buffering followed the time zone. In-CDN replication put the same library in every region, so playback stopped depending on which continent the viewer sat in. Read the case →
Short-video platform
Millions of small clips, and the first second of each one decided whether the viewer stayed. The write-up covers what happened to startup delay and buffering once files were served from inside the CDN. Read the case →
Live sports streaming
Concurrency triples at kickoff and every buffering second costs an ad break. The case covers how the edge absorbed the spike and what it did to ad delivery during the monetised moments. Read the case →
E-learning platform
Paid courses were being shared outside the paywall. Signed URLs, IP binding and referer checks closed the leak without changing the player or the checkout. Read the case →
What the network gives you
No Speed Limits
Enterprise-Grade Network
Single Price for All Regions
Cloud-Scale Architecture
Pricing that drops as you grow
Permanent Cache $0.02/GB per month, first 500 GB included. Same price in every region. 100 TB+/month? You get a personal quote. Full pricing →
| Monthly traffic | Price per TB | Full tier cost |
|---|---|---|
| 0-5 TB | $5.00 | $25 for 5 TB (monthly minimum) |
| 5-25 TB | $4.50 | $115 per 25 TB |
| 25-100 TB | $4.00 | $415 per 100 TB |
| 100-500 TB | $3.50 | $1,815 per 500 TB |
| 500-1000 TB | $3.00 | $3,315 per 1000 TB |
| 1000-1500 TB | $2.50 | $4,565 per 1500 TB |
Example: 100 TB/month costs $415, which is (5 × $5.00) + (20 × $4.50) + (75 × $4.00).
Straight answers
Do I need to keep my origin running?
Only as the import source. After replication, delivery runs from inside the CDN; you can pre-warm new releases via the cache warming API. Learn more.
Do you transcode or package video?
No. Video CDN stores and delivers your files exactly as you upload them. Encoding and packaging happen on your side, or on our separate Video Content Processing Servers. If you already produce a multi-bitrate ladder, every rendition is delivered as-is.
How do I protect paid content?
Signed URLs with expiry validated at the edge, plus referrer, user-agent and geo filters, IP binding and cookie checks. Entitlement logic (sessions, subscriptions) stays in your application. Learn more.
Questions buyers ask about the BlazingCDN Video CDN
The BlazingCDN Video CDN replicates a video library inside the network and serves HLS, DASH and MP4 files to viewers without touching the origin after import. Delivery costs from $5 down to $2.50 per TB, and permanent cache adds $0.02 per GB a month after the first 500 GB (as of October 2026). Encoding stays on your side.
How much does a video CDN cost for 200 TB a month?
On the BlazingCDN Video CDN, 200 TB of monthly delivery costs $765 (as of October 2026), plus permanent cache for the stored library. Delivery bills on progressive tiers that start at $5 per TB and reach $3.50 per TB at that volume. Permanent cache includes the first 500 GB, then costs $0.02 per GB a month.
For example, a 3 TB library pinned at the edge adds 2,500 billable GB, or $50 a month. The storage line stays separate from delivery, which remains $765. BlazingCDN charges no request fees and no regional multipliers, so viewers in the US, Europe and Asia cost the same. Enterprise terms start from 100 TB a month, and a quote never raises the published price. Raw logs cost $50 a month for teams that need every request line in their own pipeline. Real-time statistics and Prometheus metrics come included.
How does a Video CDN differ from a regular pull CDN?
BlazingCDN Video CDN replicates files inside the network instead of caching them on demand, so after import the origin can leave the delivery path entirely. A regular pull CDN fetches a file on the first miss and lets the copy expire after the TTL. Cold titles then go back to the origin.
With the Video CDN, files are imported once through pre-import, lazy import or the import API, with a callback per file. Playback no longer depends on the origin staying online. Sources include Amazon S3, Swift, Wasabi, an Rsync daemon, BlazingCDN Cloud Storage and any HTTP origin. Full range-request support (RFC 7233) lets multi-GB files resume and download in parallel chunks. For example, a 20 GB 4K master can be fetched in segments, well within the 50 GB per-file limit. Purge runs in seconds across the network, and a cache warming API pre-positions new releases.
Does BlazingCDN Video CDN transcode or package my videos?
No, BlazingCDN Video CDN does not transcode or package video: the network stores and delivers files exactly as uploaded, in MP4, MKV, WebM and MOV up to 4K. Encoding and packaging stay in your own pipeline. BlazingCDN offers separate Video Content Processing Servers for teams that want dedicated encoding hardware.
The Video CDN suits teams that already produce a multi-bitrate ladder. Every rendition is delivered as produced, in HLS or DASH. At the edge, the Video CDN can still serve the requested rendition, return a clip such as seconds 90 to 120 without a second encode, and select an audio or subtitle track per request. For example, a 200 TB monthly VOD catalogue costs $765 for delivery (as of October 2026). Teams with no encoder at all should set one up before moving, because BlazingCDN delivers bytes and does not create them.
How long does it take to move a 200 TB video library?
BlazingCDN plans a 200 TB library move to the Video CDN as about three days of replication, then a cutover at your own pace. On day 0, the customer grants read access to the bucket on S3, Swift, Rsync, Wasabi or Cloud Storage. From day 1 to day 3, BlazingCDN replicates the catalogue inside the CDN.
During import, the origin serves the replication, not viewers, so nothing changes for the audience. On day 3, the player hostname points at BlazingCDN, and both CDNs can run side by side for as long as needed. A weighted DNS split lets traffic move in steps, for example 10% first. After cutover, new titles arrive through the import API with a callback per file. Onboarding with an engineer takes about one hour, and a 14-day testing period on real production traffic comes before any commitment. A step-by-step migration guide from Bunny Video CDN also exists.
How does BlazingCDN stop paid video links from leaking?
BlazingCDN Video CDN stops leaks with signed URLs that expire on a TTL, plus checks on three layers: the link, the requester and the volume taken. Signed URLs are validated at the edge, partial signing covers only the secret part of a path, and URL encryption hides the real path.
A URL can be bound to one IP address, with a cap on how many IPs may use one link. Referer and cookie checks keep files playing only on your own pages. Geoblocking by country and HTTPS enforcement apply per resource. Uniquing downloads protection, plus delivery rate and intensity caps, stops scripts that rip a catalogue overnight. For example, a link pasted into a forum stops working once its TTL expires, often within minutes. Entitlement logic, such as subscriptions and sessions, stays in your application. The Video CDN also delivers DRM-encrypted segments, and the keys stay with the customer.