Cut your video bill with your own S3 or R2 bucket
See what a video streaming bill is made of, and how storing and delivering video from your own bucket and CDN changes it.
By the Chunkify team
A video bill has three parts: preparing each video for streaming, storing the files, and delivering them to viewers. You prepare a video once. You store it for as long as you keep it. You deliver it every time someone presses play.
That is why delivery is usually the part that grows as your app does. It is also the part where you have a choice: you can pay a video platform for it, or you can pay a storage and CDN provider directly. This guide shows how each option is billed, with worked numbers, so you can run the comparison for your own workload.
Where a video bill comes from
Each part has its own meter:
| Meter | What drives it | When you pay |
|---|---|---|
| Preparation | Minutes of video you upload | Once per video |
| Storage | How much you keep, and for how long | Every month |
| Delivery | How much your viewers watch | Every playback |
Hosted video platforms usually bundle the three and bill by the minute. Cloudflare Stream is a clear example: $5 per month for each 1,000 minutes of storage capacity, and $1 per 1,000 minutes delivered, with ingress and encoding free (Cloudflare Stream pricing, checked November 17, 2026). Storage there is prepaid and based on a video's duration, not its file size.
Per-minute pricing is easy to predict. You do not need to know bitrates, file sizes, or request counts. The trade-off is that the storage and delivery rates are the platform's, and they apply to every minute watched.
What changes when the bucket is yours
With Chunkify, the files are written to your own S3-compatible bucket and served through your own CDN. That splits the bill in two.
Chunkify charges for preparation. Streaming preparation is billed once per video, by the original video's duration and resolution. On Pay as you go, an HD input (up to 1920 × 1080) costs $0.03 per input minute; on Team it costs $0.02 (Chunkify pricing). All automatic streaming quality levels and per-title optimization are included. More views do not repeat the charge.
Your providers charge for storage and delivery, at their own rates and in their own units, which are bytes and requests rather than minutes.
Cloudflare R2 is the usual example because of how it prices delivery. R2 Standard storage costs $0.015 per GB-month. Class A operations (writes) cost $4.50 per million and Class B operations (reads) cost $0.36 per million. The monthly free tier covers 10 GB of storage, 1 million Class A operations, and 10 million Class B operations. Cloudflare states that "there are no charges for egress bandwidth for any storage class" (Cloudflare R2 pricing, checked November 17, 2026).
Amazon S3 with CloudFront is priced differently. S3 Standard storage in US East (N. Virginia) costs $0.023 per GB-month for the first 50 TB (Amazon S3 pricing, rate read from the AWS Price List published November 16, 2026, checked November 17, 2026). For delivery, CloudFront sells flat-rate plans per distribution. Pro costs $15 per month and includes 50 TB of data transfer and 10 million requests; Business costs $200 per month with 50 TB and 125 million requests (CloudFront pricing, checked November 18, 2026). AWS states that these plans have no overage charges. The allowances are not hard limits, but AWS may adjust how traffic is served if you stay well above them, so pick the plan that matches your requests as well as your bytes. A delivered minute of HLS is roughly 10 to 15 segment requests plus playlist refreshes, depending on segment length.
Without a plan, CloudFront's pay-as-you-go pricing includes 1 TB of data transfer out per month, then costs $0.085 per GB for the next 9 TB in the United States, Canada, and Europe (CloudFront pay-as-you-go pricing, checked November 17, 2026). For a video site with real traffic, the flat-rate plan is the one to use.
Chunkify's output transfer allowance
One Chunkify charge depends on your provider: transferring the prepared files into your bucket. Pay as you go includes 50 GiB of output transfer each month and Team includes 100 GiB, shared across your Projects. Beyond that, transfer to Cloudflare R2 or other S3-compatible storage costs $0.09 per GiB. Transfer to Amazon S3 is free and does not use the allowance.
This covers publishing files from Chunkify to your bucket. It is not a playback charge. See Data transfer costs.
Converting minutes to gigabytes
Your providers bill bytes, so you need a bitrate to compare them with per-minute pricing:
GB = minutes × Mbps × 0.0075
At an assumed average of 4 Mbps for video and audio together, 250,000 delivered minutes is 7,500 GB. The bitrate is your assumption to make. It depends on your content, your quality ladder, and the screens your viewers use, so measure it from your own traffic when you can.
Worked examples
These three workloads are the ones used on Chunkify's public comparison pages. They are modeled list prices for one 30-day month, not benchmarks or measured bills.
| Lightly watched library | Education | Heavy playback | |
|---|---|---|---|
| Stored minutes | 50,000 | 10,000 | 1,000 |
| New minutes this month | 1,000 | 1,000 | 100 |
| Delivered minutes | 20,000 | 250,000 | 500,000 |
| Chunkify + R2 | |||
| Preparation | $30.00 | $30.00 | $3.00 |
| R2 storage | $35.85 | $7.35 | $0.68 |
| R2 requests | $0.00 | $0.00 | $0.00 |
| Output transfer | $3.88 | $0.53 | $0.00 |
| Total | $69.73 | $37.88 | $3.68 |
| Cloudflare Stream | |||
| Storage | $250.00 | $50.00 | $5.00 |
| Delivery | $20.00 | $250.00 | $500.00 |
| Total | $270.00 | $300.00 | $505.00 |
Assumptions behind the Chunkify + R2 column:
- Pay as you go, 1080p input at $0.03 per input minute, with no plan fee or credit applied.
- Stored output of 2,400 GB, 500 GB, and 55 GB. These sizes are inputs to the model, not measurements of your library. R2 Standard at $0.015 per GB-month after the 10 GB free tier.
- 250,000, 125,000, and 20,000 writes, and 100,000, 375,000, and 750,000 reads from the bucket. All fall inside R2's free operation tiers, assuming you do not use those tiers for anything else.
- 100 GB, 60 GB, and 10 GB published to the bucket during the month, charged at $0.09 per GiB above the 50 GiB allowance.
- Delivery through a Cloudflare custom domain on the R2 bucket, with no egress charge. If you connect other metered Cloudflare services to the bucket, those are billed separately.
The Stream column uses the rates quoted above, with storage rounded up to 1,000-minute blocks. It includes encoding, which Stream does not charge for.
Two things stand out. In the first workload, storage is most of the bill either way. In the other two, delivery is, and the difference comes from the delivery tariff. Stream's $1 per 1,000 delivered minutes works out to about $33 for each TB at the assumed 4 Mbps, charged on every minute watched. R2 charges nothing for the same traffic. Chunkify's preparation charge is paid once per video, so in all three workloads the total stays below the per-minute bill.
The same holds on AWS if you choose the right CloudFront pricing. Take the education workload with S3 and CloudFront. On the Pro flat-rate plan, 7,500 GB of delivery fits inside the 50 TB allowance: $15 for delivery, about $11.50 for 500 GB in S3 Standard, and $30 of Chunkify preparation, with output transfer to S3 free. That is about $57 for the month, against $300 on Stream. On pay-as-you-go pricing instead, the same delivery is about 6,500 GB beyond the free 1 TB, or roughly $550 at $0.085 per GB. Owning the bucket lets you pick the tariff, so pick it deliberately.
Change every input in the calculators on the comparison pages: Chunkify vs Cloudflare Stream and Chunkify vs Mux.
Storing fewer bytes
When you pay per GB, the number of bytes you keep matters. Two Chunkify mechanisms affect it. They are separate, and neither changes the preparation price.
Per-title ladder selection. Chunkify analyzes each video and selects the resolutions and bitrates that are useful for it, instead of applying one fixed ladder to every upload. A simple screen recording and a fast sports clip do not get the same set of files.
Just-in-time encoding. Chunkify uploads the first renditions to your storage while they are still encoding, so playback can start before the whole video is processed. A planned production rendition starts encoding when a player first requests it, and that request encodes the whole rendition. If nobody ever requests the planned 1080p rendition of a video, it is never encoded or stored.
What still exists: the preparation charge for every upload, the fallback output, and every rendition that has been requested once, which stays in your bucket afterward. Source files you keep are stored too.
We are not quoting a savings figure, because it depends on your content and on how much of your library is watched. Fewer renditions also do not by themselves mean lower delivery cost. Delivery depends on the bytes your viewers actually pull, and with a zero-egress provider there is no bandwidth charge to reduce in the first place. On a per-minute platform, a smaller file does not lower a duration-based storage charge either.
When a hosted platform is the better deal
Owning storage is not always the cheaper or the easier choice. A hosted platform can be the better fit when:
- Your library is small. At a few thousand stored minutes and light viewing, either bill is small, and the setup time costs more than the difference.
- You upload a lot and few people watch. Chunkify charges preparation for every input minute. A platform with free encoding charges nothing until the video is stored and watched. Compare both on your real upload volume.
- You do not want a storage and CDN account of your own. Setup takes a few minutes with the guides, and guided Cloudflare setup configures the R2 playback domain and browser access for you. The bucket, its usage, and its bill still belong to you.
- You would pay your CDN per GB with no plan. As the CloudFront pay-as-you-go example shows, heavy playback on a per-GB tariff can cost more than per-minute delivery. Use a flat-rate plan or an egress-free provider.
- You want one invoice and one support contact for encoding, storage, delivery, and the player.
How to set it up
- Connect storage. Add your Amazon S3, Cloudflare R2, or S3-compatible bucket to your Project. See the storage overview.
- Add a CDN. Serve the bucket through a CDN and save its base URL on the storage connection. See CDN delivery. For R2, guided setup in the dashboard can attach the playback domain for you.
- Configure CORS. Allow your website's origin for browser uploads and playback. See Configure CORS.
- Create a video. Follow the video streaming quickstart, then test the CDN URL in a browser on your actual website.
FAQ
Is R2 egress really free?
Cloudflare's pricing page states that there are no charges for egress bandwidth for any R2 storage class (checked November 17, 2026). Storage and operations are still billed beyond the free tier, and other metered services you connect to the bucket are charged by those services.
Do I need a CDN in front of my bucket?
For ongoing playback, yes. Chunkify builds playback URLs from the CDN base URL on your storage connection. With R2, a Cloudflare custom domain on the bucket fills that role; Cloudflare's r2.dev URL is intended for development traffic. With S3, follow the CloudFront guide.
What does Chunkify charge for?
Preparation, the optional outputs you request such as static MP4 renditions, captions, and extra thumbnails, and output transfer beyond your monthly allowance. Chunkify does not charge for storage or views. See video streaming pricing.
Can I start without a bucket?
Yes. Chunkify temporary storage lets you test without connecting your own bucket. Files stored there are deleted after 24 hours, so connect your own storage before production. Pay as you go has no monthly fee; create an account to try it.