Video hosting costs: storage and bandwidth
Video costs money in two places: keeping it and sending it. Both can be estimated from numbers you already have. This guide shows the arithmetic and where the surprises hide.
Video hosting cost comes from two things. Storage is the source plus every rendition, and together they are usually bigger than the original. Bandwidth is the bitrate times the minutes watched, across all viewers. You can estimate both with simple sums, from how long your library is and how much it will be watched.
Two numbers decide what a video library costs: how many gigabytes sit on disk, and how many gigabytes leave the building. Everything else is small or fixed by comparison: transcoding compute, thumbnails, the player and the dashboard. What makes video unusual is that both numbers are easy to underestimate. The file you uploaded is not the file that gets stored. And the file that gets stored is not the file that gets watched.
This guide works through the arithmetic with concrete assumptions. Then it shows how a flat subscription changes the picture and where the bill can surprise you. None of the figures below are statistics. They are worked examples from stated bitrates, so you can swap in your own. The video hosting hub explains the pipeline these costs come from.
Bits, bytes and the one conversion that matters
Video bitrate is quoted in megabits per second (Mbps); storage and transfer are quoted in megabytes and gigabytes. There are 8 bits in a byte, so a stream at 8 Mbps consumes 1 megabyte per second, 60 MB per minute and 3.6 GB per hour. Keep that conversion at hand and the rest of this guide is multiplication. Mixing the two units is the most common estimating error, and it is always off by a factor of eight in one direction or the other. The bitrate guide explains what bitrates are sensible at each resolution. Here we only need them as inputs.
Storage: the source is only the beginning
When you upload a file, the host keeps it as the source and then produces a ladder of renditions from it. On VideoBB that ladder is 144p, 240p, 360p, 480p, 720p and 1080p for every upload. When the source is large enough, 1440p and 2160p are made too, for Premium members to watch. Each rendition is a complete copy of the video at its own bitrate. Add them up, and the stored size of a video is larger than the file you uploaded. The gap can be wide if the source was efficiently encoded and the ladder is generous.
The exact multiplier depends on the encoding settings each host chooses. These are not usually published, so treat any figure as a rule of thumb. The pattern, though, is reliable: the top two rungs dominate, the bottom four together add a modest amount, and the source sits alongside all of them. Video transcoding explained describes why every rung has to exist.
Worked example: one hour of 1080p footage
Illustrative bitrates per rung; substitute the ones your host or encoder actually uses. Sizes are bitrate multiplied by 3,600 seconds, divided by 8.
| Item | Assumed bitrate | Size for one hour |
|---|---|---|
| Uploaded source (1080p, editor export) | 12 Mbps | 5.4 GB |
| 1080p rendition | 5 Mbps | 2.25 GB |
| 720p rendition | 2.5 Mbps | 1.1 GB |
| 480p rendition | 1.2 Mbps | 0.54 GB |
| 360p rendition | 0.8 Mbps | 0.36 GB |
| 240p rendition | 0.4 Mbps | 0.18 GB |
| 144p rendition | 0.2 Mbps | 0.09 GB |
| Total stored | About 9.9 GB |
Bandwidth: bitrate times minutes watched
Delivery cost is the sum, over every view, of the bitrate the viewer received multiplied by how long they watched. With adaptive streaming the bitrate varies within a single view, so use a blended figure. If most viewers land on the 720p and 1080p rungs, a blended 3.5 Mbps is a fair planning number for a 1080p library. For a mostly mobile audience it will be lower. At 3.5 Mbps, an hour watched is about 1.6 GB transferred. A thousand viewers each watching ten minutes is roughly 260 GB. Unlike storage, this number is not bounded by the size of your library. A single popular video can generate more transfer in a week than the whole library takes up on disk. That is why bandwidth, not storage, is the line item that surprises people. Adaptive bitrate streaming explained shows how the player's rung choice drives this figure.
What a CDN changes, and what it does not
A content delivery network caches segments at edge locations close to viewers. When a second viewer in the same region requests a segment the first one already fetched, it is served from the edge rather than from origin storage. This cuts the cost of reading from storage and the latency the viewer sees, and it is essential for handling a spike. It does not reduce the total bytes delivered to viewers. Each viewer still receives their own copy. Whether that transfer is charged to you depends entirely on the host's plan structure. CDN for video delivery covers the mechanics and the hit-rate arithmetic.
Metered plans vs flat subscriptions
Two pricing models handle the same underlying costs in different ways.
Metered (pay per GB)
- Cheap when the library is small and quiet
- Cost tracks usage exactly
- A successful launch or viral clip produces a large bill
- Requires forecasting to budget
- Common for infrastructure providers and APIs
Flat (subscription)
- Same cost in a quiet month and a busy one
- Usage limits set by the plan rather than by the bill
- A spike costs nothing extra
- Simple to budget annually
- VideoBB Premium: $9.99 a month or $79 a year
Reducing the numbers without reducing quality
Storage is reduced by uploading efficient sources and by not keeping duplicates. An H.264 export at a moderate CRF is much smaller than a mezzanine-grade file and looks the same after transcoding, because the host re-encodes anyway. To shrink an oversized export without an editor, the free video compressor offers light, medium and strong settings. Use the lightest one that gets the file where you need it. Do not upload a heavily compressed low-bitrate file just to save space. The renditions inherit its artefacts, and why video looks blurry after upload is the result. Prepare video for upload gives export settings that are small without being lossy in a visible way.
Bandwidth is reduced mostly by the player. Adaptive streaming already delivers each viewer only the bitrate they can use. Beyond that, avoid autoplaying video that most visitors will not watch, and use a poster image rather than loading the first segment on page load. Autoplay rules in browsers explains why autoplay is often blocked anyway. 4K vs 1440p vs 1080p helps you decide whether the top rungs earn their transfer for your audience.
Estimating your own library in four steps
- Total the duration of everything you will host, in hours. Multiply by the sum of the source and rendition sizes per hour from the table (about 10 GB per hour of 1080p with these assumptions) for stored footprint.
- Estimate monthly minutes watched: views per month multiplied by average watch time. Be generous; people underestimate views on a launch.
- Multiply minutes watched by a blended bitrate (3.5 Mbps for a desktop-heavy 1080p audience, lower for mobile), convert to GB, and that is monthly transfer.
- Compare both totals against the plan you are considering. If a metered plan's worst month exceeds a flat plan's annual price, the flat plan is the cheaper insurance.
Frequently asked questions
Why is my stored size bigger than my upload?
Because the host keeps your source and adds a full rendition at every rung of the ladder. Each rendition is a separate encoded copy of the whole video. Six rungs plus the source will exceed the original, particularly if your upload was efficiently encoded. This is normal and is what makes adaptive streaming possible.
Does a CDN make bandwidth free?
No. A CDN serves repeated requests from cache close to the viewer, which reduces reads from origin storage and improves latency. Every viewer still downloads their own segments, so the total delivered to viewers is unchanged. Whether you pay for that transfer depends on your host's plan, not on the presence of a CDN.
Is 4K much more expensive to host than 1080p?
Yes, on both sides. A 2160p rendition at a sensible bitrate is several times the size of a 1080p one, so storage grows. Viewers on fast connections will receive it, so transfer grows too. It is worth it for content where detail matters. For talking heads or screen recordings, 1080p is usually the better trade.
How do I find the bitrate of a file I already have?
Use ffprobe, which ships with FFmpeg: ffprobe -show_format yourfile.mp4 prints a bit_rate value in bits per second. Divide by 1,000,000 for Mbps. Most video editors also show the average bitrate in the export dialog or file information panel. Once you have it, size per hour is bitrate in Mbps times 450 megabytes.
Sources
- FFmpeg documentation — ffprobe and encoder settings that determine file size.
- RFC 8216: HTTP Live Streaming — Why a rendition ladder is stored in full.
- YouTube Help: Recommended upload encoding settings — A published reference for sensible bitrates per resolution.
- MDN: HTTP caching — How edge caches decide what to keep.
Related guides
Self-hosting vs a video hosting platform
Serving your own mp4 is simple, cheap and works until it doesn't. This is a clear account of what you are taking on when you self-host, and what a platform is really doing for you.
Video bitrate guide
Bitrate is the budget an encoder spends on every second of picture. Here is how to read it, how to set it, and how much to give a file before you upload.
CDN for video delivery
Video is the most cache-friendly traffic on the internet and the most punishing when caching fails. How content delivery networks serve segments, what to cache for how long, and where the costs hide.
Video transcoding, explained
Transcoding turns one source file into a set of aligned versions ready for adaptive streaming. Here is what happens at each stage, and which settings decide the result.