Storage
Video hosting for large libraries
Keep the whole archive online. Storage and monthly delivery are priced as separate dimensions here, so a big library that is watched at a steady rate costs what a big library should cost — not what a busy streaming service costs. Published plans run to 2 TB, and beyond that you buy storage by the terabyte at a rate you can read before you ask anyone.
The key idea
Storage and delivery are not the same allowance
Understanding this is what stops a large-library owner overpaying. The two numbers move independently, and they are priced independently.
Without control
Storage — what you keep
The total volume of source and streaming video held on the platform.
- Grows when you publish, and stays flat when you do not
- Unaffected by how many people watch
- Published bands to 2 TB; larger shapes use USD 23 per terabyte in the estimator
- Archive footage you will never publish does not need to sit here
On your own terms
Delivery — what gets watched
The volume streamed to viewers in a month.
- Moves with launches, cohorts and campaigns
- Unaffected by how much you have stored
- Published bands to 4 TB a month; larger shapes use USD 20 per terabyte in the estimator
- This is the number a bandwidth calculator exists to estimate
Sizing
What actually consumes a storage allowance
A library is rarely the size people first guess, because more than the original file is being kept. Here is what to count.
- The adaptive renditions, not just the sourceEvery video
- One upload becomes a set of renditions so playback can adapt to each viewer’s connection. That set is the thing being stored and delivered, so estimate from what is published rather than from the size of the file on your desktop.
- Running time at the bitrate you deliverThe core arithmetic
- Minutes multiplied by bitrate is the honest basis for a storage estimate. Long-form recordings — lectures, webinars, panel sessions — dominate a library’s footprint far more than the number of videos does.
- Everything you keep, including the unpublishedHousekeeping
- Drafts, superseded cuts and archived material all occupy the allowance while they are on the platform. Deciding what genuinely needs to stay online is usually the cheapest capacity you will ever find.
- Captions, thumbnails and chaptersMarginal
- Text tracks and images are small next to video and will not move your band. Worth knowing so they are not a source of anxiety in a sizing exercise.
- Projects keep it navigableOrganisation
- Group videos into projects that carry shared configuration, so a library of thousands stays manageable and a new video inherits the right settings instead of being configured from scratch.
- The API keeps the inventory honestEvery plan
- List videos, read per-video status and pull storage and content reports through the REST API, so your own systems can track what is held and flag what should be retired.
The numbers
What a terabyte-scale library costs
Published bands first, then the rate for anything larger. No quote required to work out either.
| Plan | Price | Storage | Monthly delivery |
|---|---|---|---|
| Starter | USD 24 / month, billed monthly | 300 GB | 1 TB |
| Plus | USD 50 / month, billed monthly | 1 TB | 2 TB |
| Pro | USD 100 / month, billed monthly | 2 TB | 4 TB |
| Custom shape | USD 23 per TB stored + USD 20 per TB delivered | Your figure | Your figure |
Because the two rates are separate, an archive-heavy shape is cheap to express. A five-terabyte library delivering three terabytes a month works out at five times 24 plus three times 22 — 120 plus 66, or USD 186 a month — and the custom plan builder shows that figure before you send anything. The same arithmetic works in reverse for a small library with a large audience, which is exactly the point of pricing the two dimensions apart.
- Estimate storage from total running time at your delivery bitrate, not from the size of your source files.
- Estimate delivery from monthly views multiplied by average minutes watched — the bandwidth calculator does it.
- If both numbers sit outside the published bands, build the shape in the custom plan builder and send it as a request.
- If a commercial term affects your decision, ask for it in writing and rely on the written answer.
Who it suits
Where a large library belongs here
Course and training archives
Years of lessons kept online because learners still work through them, with delivery that reflects real cohort sizes rather than the size of the catalogue.
Recorded webinars and events
Long recordings are the heaviest thing most organisations store. Chapters make them navigable and separate pricing keeps them affordable to keep.
Corporate video libraries
Briefings, policy and induction material accumulating over years, held behind an origin allowlist and organised into projects by department.
Back catalogues
Content kept because it may be needed rather than because it is watched weekly — the classic case for storage-heavy pricing.
Systems-managed libraries
Where a CMS or LMS owns the catalogue, the REST API can create, publish, caption and retire video so the inventory never drifts from your own records.
Libraries that need pruning
Storage and content reports show what is held and what earns attention, which is the evidence you need to retire material with confidence.
Questions
What large-library owners ask
How much storage can I have?
Published plans include 300 GB, 1 TB and 2 TB. The custom estimator uses USD 23 per terabyte stored and USD 20 per terabyte delivered, so a five- or ten-terabyte library is a number you can work out yourself before contacting anyone.
How do I estimate the size of my library?
Multiply total running time by the bitrate you deliver at, and remember you are storing the adaptive rendition set rather than only the source file. Long-form recordings dominate the total far more than the number of videos does, so start with your longest content.
Do I have to pay for bandwidth I do not use?
No, and that is the main reason large libraries suit this pricing. Storage and monthly delivery are separate dimensions with separate published rates, so an archive watched at a steady rate is not charged as though it were a busy streaming service.
Can I upload very large source files?
Yes. Use resumable upload sessions through the REST API for large files, so a dropped connection resumes rather than restarting the transfer. For a bulk migration, script the uploads and use webhooks to be told when each video is ready.
How do I keep thousands of videos manageable?
Group them into projects, which carry shared configuration so new videos inherit the right settings. The REST API can list videos, read per-video status and pull storage and content reports, so your own systems can maintain a reliable inventory.
How do I decide what to retire?
Use the reporting. Plays, watch time and completion show which parts of the archive still earn attention, and the storage report shows what they cost to keep. Retiring material you can prove nobody opens is the cheapest capacity available.
Can I choose where my library is stored?
Region selection is not exposed as a customer setting today. If your case depends on the library being held in a particular jurisdiction, raise it with us before you plan around it and get the answer in writing.
Bring us both numbers
Total running time at your delivery bitrate, and a normal month of viewing. With those two figures a large library is a five-minute pricing exercise rather than a negotiation.