Cloud Storage for CDN
Object storage inside the BlazingCDN panel. Create a bucket, upload your files and point a CDN resource straight at it, so there is no separate origin server to keep running.
Works as the origin for Anycast CDN and Video CDN resources · Delivery billed on the usual progressive tiers · Engineer reply within 3 business hours
Your Files Live in a Bucket, the CDN Pulls Them from There
Cloud Storage is object storage you create and manage in the BlazingCDN panel. Instead of keeping a separate origin server for your static content, you upload the files into a bucket and use that bucket as the origin for an Anycast CDN or Video CDN resource.
- Created in the panel, in the Resource origin section of a CDN resource.
- Bucket name: 3 to 63 characters, lowercase letters, numbers, periods and hyphens.
- Works as an origin for both Anycast CDN and Video CDN resources.
1. Create a bucket
In the CDN resource, open the Cloud Storage tab and press Create new bucket. Give it a name and a type.
2. Upload your files
Put the static content you want to deliver into the bucket: images, video, installers, documents.
3. Point the resource at it
Select the bucket as the resource origin. Import of small and mid-size files usually finishes in 5 to 10 minutes.
Test CDN Speed Across Top Regions
Avg. Download Speed
Latency
Test link
What it costs
Storage: $0.015 per GB. Delivery out of the bucket is billed on the usual progressive tiers, $5/TB down to $2.50/TB as volume grows, so 100 TB a month works out at about $415 with one rate across regions.
Full pricing → · Running a large library? Talk to a CDN Engineer →
What the storage feeds
Anycast CDN
Video CDN
HLS Streaming CDN
Questions buyers ask about BlazingCDN Cloud Storage
BlazingCDN Cloud Storage is object storage inside the CDN panel that works as the origin for Anycast CDN and Video CDN resources. Storage costs $0.015 per GB per month, delivery is billed on the normal tiers from $5 per TB down to $2.50, and no separate origin server is needed.
What does storing 200 GB and delivering 50 TB cost?
On BlazingCDN, storing 200 GB in Cloud Storage costs $3 a month, and delivering 50 TB from it costs $215 (as of October 2026). Storage is billed at $0.015 per GB per month. Delivery out of the bucket is billed on the same progressive tiers as any CDN traffic: $5 per TB for the first 5 TB, then $4.50 and $4.00 per TB as volume grows. The rate is the same in the US, Europe and Asia.
The bucket is the origin, so there is no egress charge between storage and the CDN. Only the traffic delivered to users counts. For example, at 100 TB of delivery the traffic line is $415 whatever the library size. Requests are not billed. A larger library scales linearly at the same per-GB storage rate, so a 300 GB library costs $4.50 a month to store.
How do I connect a BlazingCDN bucket to a CDN resource?
BlazingCDN Cloud Storage connects in three steps inside the panel, and import of small and mid-size files usually finishes in 5 to 10 minutes. First, open the Cloud Storage tab in a CDN resource and press Create new bucket. Bucket names use 3 to 63 characters: lowercase letters, numbers, periods and hyphens. Second, upload the static content: images, video, installers or documents. Third, select the bucket as the resource origin.
Files can also arrive by import from an HTTP(S) server, S3, Swift, Wasabi and S3 compatible buckets, FTP, rsync over SSH or rclone. Import can be manual, by API, pull or push, and pre-import or lazy. A callback URL reports each import result. For example, a software vendor can keep installers in a bucket and retire the separate origin server it used to maintain. Onboarding with an engineer takes about one hour.
Is BlazingCDN Cloud Storage a good fit for backups?
No: BlazingCDN Cloud Storage is built as a CDN origin, not as backup or archive storage. Each bucket feeds an Anycast CDN or Video CDN resource, and the files are meant to be delivered to users. The pricing reflects that design: $0.015 per GB per month for storage (as of October 2026), with delivery billed per TB on the CDN tiers.
The platform keeps at least three geographic copies of each file, validates checksums in the background and heals itself after a drive failure. Those protections serve delivery. For example, a library of product videos, installers and documents fits well, because users download those files every day. Database dumps and compliance archives that nobody downloads belong in a dedicated backup service. Files up to 50 GB are supported. Transcoding is not offered, so upload video that is already encoded. An engineer replies within 3 business hours if you are unsure which side a dataset belongs on.
Can I move my S3 origin into BlazingCDN Cloud Storage?
Yes: BlazingCDN imports from S3, Swift, Wasabi and other S3 compatible buckets over three parallel streams, and files go live within five minutes of import. Import can run once as a pre-import, or lazily as users request files. Lazy import filters by file size and type, so only the paths that matter are copied. Auto import scans the source for changes, and a callback URL reports each result.
The main difference from a separate S3 origin is the billing path. Storage costs $0.015 per GB per month (as of October 2026), and there is no egress charge between the bucket and the CDN. For example, a team paying an outside cloud for both storage and egress to its CDN removes that egress line entirely. The S3 bucket can stay as the source of truth while Cloud Storage serves traffic. An engineer replies within 3 business hours during the migration.
Should I use Cloud Storage or Video CDN permanent cache?
BlazingCDN offers both, and the difference is price and purpose: Cloud Storage costs $0.015 per GB per month, while Video CDN permanent cache costs $0.02 per GB per month after 500 GB included (as of October 2026). Cloud Storage is a bucket you manage, used as the origin for Anycast CDN or Video CDN resources. Permanent cache is the Video CDN’s own replication: files replicate inside the CDN and stay there, with no origin dependency after upload.
Cloud Storage suits mixed static content such as images, installers and documents. Video CDN permanent cache suits large VOD libraries, and the Video CDN is not meant for files under 10 MB. For example, a 400 GB video library fits inside the 500 GB included with the Video CDN, so permanent cache adds nothing to the bill. Delivery from either option is billed on the same tiers, from $5 per TB down to $2.50 per TB.