Video hosting looks cheap until the first popular video. Then you find out that the price on the pricing page was only one of three meters: storage, bandwidth and encoding. Each of them scales with something different, and most surprises come from mixing them up. This guide gives you a method to estimate the real monthly cost of any video host, including ours, before you upload a single file. It deliberately contains no competitor prices: those change often, and the method works with whatever numbers you find.
The three meters and what drives them
| Meter | Grows with | Usually billed as |
|---|---|---|
| Storage | Hours of video in your library and how many versions of each are kept | A quota per plan, or a price per GB per month |
| Bandwidth (egress) | Views, how long people watch and at which quality | A monthly quota with overage, or a price per GB delivered |
| Encoding | Minutes of video uploaded, resolution and number of renditions | Included in the plan, or a price per minute of video |
Storage is predictable: it only grows when you upload. Encoding is a one-off cost per upload. Bandwidth is the wild card, because it depends on your audience rather than on you, and for a site with real traffic it is almost always the largest part of the bill.
Storage: bitrate times duration
A video file is, to a good approximation, its bitrate multiplied by its length. A one-hour video at 5 Mbit/s weighs 5,000,000 × 3,600 / 8 bytes, which is about 2.25 GB. That is the number to remember: one hour at 5 Mbit/s is roughly 2.25 GB, and everything scales linearly from there. Halve the bitrate and you halve the disk; double the length and you double it.
Two things change the arithmetic. First, an adaptive stream is not one file but several renditions of the same video. Some hosts count the original plus every rendition against your storage, others count only what you uploaded. Ask which one applies, because a full ladder from 360p to 1080p can take about as much disk as the original itself, sometimes more; the guide to adaptive bitrate ladders shows the exact sizes our converter produces. Second, units: some providers quote decimal gigabytes and others binary gibibytes. The difference is about seven percent, which is enough to matter near a limit.
On UFOLOAD the storage quota is counted by the size of the files you upload, so the encoded renditions do not eat into it. Uploading the same content again does not use the space twice: the API recognises the file by its SHA-256 hash and returns the existing entry. The quota, the maximum size of a single file and the highest video quality are set per plan and shown on the pricing page, where they are the same live numbers your dashboard uses.
Bandwidth: views times watch time times bitrate
Every second a viewer watches is a number of bytes leaving the host. That gives the formula below. It is simple, but the inputs are where estimates go wrong: people use the full video length instead of the average watch time, and they forget that quality depends on the viewer, not on the file.
storage_GB = library_hours x 3600 x total_bitrate_Mbps / 8 / 1000
traffic_GB_per_month = views x avg_watch_minutes x 60 x avg_streamed_bitrate_Mbps / 8 / 1000For the bitrate you can use the peak values our converter encodes to. They are upper bounds, because the encoder works to a constant quality target and only reaches the cap on complex scenes, so real traffic is usually lower. The table shows what 1,000 views of five minutes cost at each rendition, audio included.
| Rendition | Peak video + audio | Per second | 1,000 views x 5 min |
|---|---|---|---|
| 360p | 0.8 Mbit/s + 64 kbit/s | up to 108 KB | up to 32 GB |
| 720p | 2.8 Mbit/s + 128 kbit/s | up to 366 KB | up to 110 GB |
| 1080p | 5 Mbit/s + 160 kbit/s | up to 645 KB | up to 194 GB |
| 2160p (4K) | 16 Mbit/s + 192 kbit/s | up to 2.0 MB | up to 607 GB |
The spread between 360p and 4K is almost twentyfold, which is why the quality mix of your audience matters more than the raw number of views. A site where most viewers are on phones and watch 720p costs a fraction of one that serves 4K to desktop screens. As a rule of thumb, take the quality your viewers will mostly get, multiply, then add a third for headroom.
Two worked examples. A tutorial site with 10,000 views a month, six minutes of average watch time and mostly 720p: 10,000 × 360 s × 366 KB/s is about 1.3 TB at the cap, so plan for 1 to 1.3 TB. A catalogue where 2,000 views a month watch 40 minutes of 1080p each: 2,000 × 2,400 s × 645 KB/s is about 3.1 TB. Long watch time beats view count every time.
Measure instead of guessing as soon as you have traffic. The Traffic page in the UFOLOAD dashboard shows delivered bytes per day and per file, so you can replace the estimate with your own average bitrate after the first month.
Encoding: usually the smallest line, sometimes a trap
Encoding costs CPU time: more renditions, higher resolution and slower presets all take longer. Some platforms bill it per minute of source video, others include it in the plan and bound it indirectly by file size, quality caps or queue priority. If a host charges per minute, multiply the minutes you plan to upload per month by that price, and remember that re-encoding your library after changing settings is billed the same way.
UFOLOAD does not bill encoding by the minute. The limits that matter are the ones above: storage, monthly traffic, the largest single file and the highest quality of your plan, plus a priority queue on paid plans. Inside those limits, the Encoding studio lets you trade speed for quality: a fast profile gets a video ready sooner at a slightly larger size, a quality profile takes longer for a cleaner picture, and you can set the lowest rendition so small versions you do not need are never created, which saves both disk and encoding time.
Costs hidden outside the three meters
- Overage rules. What happens when you pass the monthly traffic limit: a warning, throttling, a hard stop or an automatic charge, and at which rate. Look for the rate per GB before you need it.
- Retention. Free plans commonly delete files nobody watches. On UFOLOAD the Free plan removes files without views after a number of days stated on the pricing page; paid plans have no such limit.
- Feature gates. Player customization, download buttons, API access, team seats and ads are often tied to a plan. Check that the plan you cost out includes everything you need.
- Payment terms. Periods, auto-renewal and currency. UFOLOAD plans are bought for 1, 3, 6 or 12 months at the same monthly price, with one payment and no automatic renewal.
- Your own time. Self-managed setups look free until you count maintenance. The comparison of self-hosting, YouTube and a video host puts numbers on that side.
Run the numbers in five steps
- Count library hours and pick the source bitrate you will upload at; compute storage with the formula, then add the renditions if the host counts them.
- Estimate monthly views, the average watch minutes per view and the quality most viewers will get; compute traffic.
- Add 30 percent to traffic for growth and spikes. A single video that gets shared can double a month.
- Look up the plan whose storage, traffic, file size cap and quality ceiling cover your numbers, and read the overage terms.
- Compare hosts on cost per delivered terabyte at your volume rather than on the headline plan price.
Extra capacity on UFOLOAD is a top-up rather than a plan change: traffic packs never expire, and extra storage is bought for a fixed term, both from your balance on any plan. The exact packs and prices are on the pricing page and in the dashboard. If you earn from ads, remember that traffic is an input to income too; the monetization guide explains how the two connect. When you compare candidates, the video hosting checklist lists the non-price questions worth asking.
Upload a video, get an HLS player and an API key in minutes. Plan limits are listed on the pricing page.