Affordable Video Hosting: How to Work Out What It Will Actually Cost You

Two plans with similar monthly prices can produce different totals for the same library because their allowances may be attached to storage, delivery, video count, seats or extra services. Start with your own workload so the comparison reflects the service you will actually use.

This guide shows how to estimate storage and delivery, include add-on services and operating effort, and compare two quotes on the same inputs. Use the current pricing page for DynTube plan figures, then place each shortlisted provider beside the same typical-month and launch-month scenarios.

Two numbers decide the plan you need

On DynTube, plans are priced on two dimensions, and they behave differently. Storage is the retained library your account is accounted for: it grows as you publish, holds steady when you do not, and falls when counted media is deleted or retired. Delivery is how much video is actually streamed to viewers in a month: it moves with a launch, a cohort or a campaign, and it is the number that surprises people. When you look at any other provider, work out which dimensions their bands are actually attached to before you compare — storage, delivery, a video count, a seat count, or some combination — because that is what decides your bill rather than the headline.

Because they move independently, the shape of your workload matters as much as its size. A large back catalogue watched occasionally and a small set of videos watched constantly can cost the same on one provider and quite differently on another. Work out which of your two numbers is the one that grows, because that is the dimension you are really buying.

• Library larger than the audience — archives, course back catalogues, long recordings kept in case you need them. Storage is your constraint.
• Audience larger than the library — a modest set of videos watched a lot, launches, campaigns, marketing pages. Delivery is your constraint.
• Both growing at once — worth checking whether the published bands fit at all before you commit to one that only just does.

Estimating the storage you need

Storage is the easier of the two to predict, because it is a property of your library rather than your audience. Count the hours of finished video you expect to be holding twelve months from now, not what you have today. Then check what your provider actually counts toward the storage it bills you on: adaptive streaming turns one upload into several renditions at different qualities, and whether the original upload is kept alongside them, and whether either is counted, is a question to put to the provider rather than to assume. The figure your account already reports as storage today is the honest starting point for the projection.

• How many hours of finished video will exist in a year, at your real publishing rate rather than your intended one?
• Ask what is retained after processing, and what of it counts toward your storage figure. Keeping an original upload can be useful insurance if you ever move providers — find out whether it is kept, whether you can retrieve it, and whether it is billed.
• Does anything get deleted, or does everything stay? If you have no retirement rule, your estimate should assume the library keeps growing, because nothing will stop it.
• Is there an existing archive to migrate in on day one? That is a step change in storage, not a gradual climb.

Estimating the delivery you will use

Delivery is the number worth spending ten minutes on, because it is the one that decides your band and the one that moves when something goes well. The arithmetic is simple and worth doing by hand once so you trust it: bitrate in kilobits per second divided by eight gives kilobytes per second, times sixty gives the data in a minute of watching. Multiply by the average watch time and then by the number of monthly viewers, and divide by 1,000,000 for decimal gigabytes.

You need three inputs, and none has to be precise: the quality you publish at, the plays you expect in a typical month, and how much of a video a typical viewer finishes. Estimate a launch month separately from a typical one. Our bandwidth calculator does this arithmetic for you, and shows its working so you can check it against your own spreadsheet.

Read that table as a top-rendition baseline: what a straight run of watching costs if every viewer holds the top rung. It is not a ceiling. Adaptive streaming prepares a ladder and each viewer receives the rendition their connection can hold, which pushes real delivery below the baseline; seeking and replays deliver the same bytes more than once, and protocol overhead and player behaviour add to it, which pushes it back above. So the figure can land either side of the arithmetic. Treat it as a planning estimate, and choose a band with room in it.

Add the services your workflow will use

Build a complete estimate by adding the services and plan features your workflow needs. Check each item against the exact plan or quote you are considering.

• Live streaming — ask what a live bill is driven by, and whether it is a published band or a quote. Ours is on its own pricing page: we price live on how many broadcasts run at the same time and how much video reaches viewers while they run, with kept recordings then becoming ordinary storage and delivery. We publish live bands there, read from the same billing catalogue as the hosting plans, and each one can be bought from its card; an event whose concurrency, storage or delivery sits outside them is sent as a request instead, and any terms come back in writing.
• Transcription and translation — ask what the meter counts and what a second language costs. Ours is metered by the minute of audio processed, per output language, monthly or yearly, as an add-on that requires a hosting plan underneath it. We publish no rate; it is quoted against the volume and languages you send.
• Where video is served from — regional coverage and edge delivery can differ between plan shapes, and that difference is a cost as well as a performance choice.
• Capabilities recorded against particular plans — read the inclusions on the plan you would actually buy, not the feature page. "Supported" and "included in what I am paying for" are two separate answers.
• What happens at the limit — ask the question directly, because the possible answers produce very different bills in a busy month. Is usage above the allowance charged? Topped up? Slowed? Stopped? Do not infer it from a policy page; get the answer for your plan in writing.

Include the operating effort around video hosting

Total cost includes the work required to migrate, integrate and operate the library. Estimate that effort in hours so a lower plan price is compared with the complete workflow.

• Migration in — moving an existing library, re-encoding it if formats differ, and updating every embed that points at the old home.
• Integration — whether your site, members area, learning platform or app can embed and gate video without engineering work, and how much if not.
• Operations — who uploads, who publishes, who fixes a failed encode, and how much of that lands on someone whose time is not free.
• Access rules — if you gate or sell access, whether the platform expresses your entitlement model or you build the missing half yourself.
• Migration out — whether source files are retrievable later. A provider you cannot leave has a price that is not on the pricing page.

Compare providers on the same workload

Once you have your own storage and delivery estimates, a comparison becomes mechanical. Take each shortlisted provider, find the plan that covers your estimate with headroom, and total the monthly cost of that plan plus everything metered separately that you know you will use. Compare those totals, not the entry-level prices, and do it again against your launch-month numbers rather than your typical ones.

1. Write down your storage estimate for twelve months out and your delivery estimate for a typical month and a launch month.
2. For each provider, identify the plan those numbers actually fit — not the cheapest one listed.
3. Add the separately metered items you know you will use: live, transcription, regional delivery, anything plan-gated that you need.
4. Write down the overage or limit behaviour for each, in the provider's own words.
5. Add your own estimated hours for migration, integration and operation on each platform.
6. Compare the totals, then sanity-check the winner by uploading one real video and running one real embed before you move anything else.

A percentage saving is useful only when both sides use the same storage, delivery, feature and billing assumptions. Keep those inputs beside the result so your team can update the comparison as the workload grows.

Use the current DynTube pricing and planning tools

DynTube keeps current plan figures in the pricing catalogue and provides separate planning pages for delivery, live streaming, subtitles and custom requirements. Use these destinations to complete the estimate:

• Current plans, their storage and delivery, and what each one includes — /pricing.
• Estimate your monthly delivery from quality, audience and watch time — /pages/bandwidth-calculator.
• How delivery is measured, and what adaptive streaming does to real usage — /pricing.
• Where video is served from and what that means for your audience — /pricing/edge.
• How live is priced — concurrency, delivery while broadcasting, and what a kept recording costs afterwards — plus the published live bands and the request path for an event shape they do not cover: /pricing/live-streaming.
• How subtitles and translation are metered — per minute of audio processed, per language, as an add-on to a hosting plan — and how to request current rates: /pricing/streamai.
• Our fair usage policy, which is what we publish about accounts using more than normal operation — /pages/fair-use.
• A library or audience the published bands do not fit — /custom-plan.
• Anything decisive that is not written on those pages — ask us, and get the answer in writing before you commit.

The best-value plan matches your projected storage and delivery with headroom for a strong month, includes the capabilities your workflow needs and keeps migration and operation practical. Revisit the estimate with real usage after launch so the plan continues to fit as the library grows.