Skip to content
uncompressed.io

Storage and cost

Video storage for filmmakers.
Three tiers, and the mistake of running two of them as one.

Three different jobs all get called storage. Working storage runs the edit. Delivery storage is what a client opens. Archive is what you are glad you paid for the day someone asks for a re-cut two years later. Here is what belongs in each tier, what each one costs, and what breaks when a single product is asked to do two of them.

See the rate cards

Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month

Updated September 2026

One word, three jobs

A film library is not one thing.
It is three, and they price differently.

The moment storage stops being a one-off annoyance and starts being a structural problem is the moment you notice you are paying three separate bills for what you thought was one product. That is not a billing error. It is the shape of the work. A cut needs speed, a client needs a page that opens, and a finished film needs somewhere cheap to sit for a decade. No single product is good at all three, and the ones that claim to be are quietly bad at two of them.

Working storage

A fast local disk or a small array, attached to the machine that cuts. It holds camera originals, project files and renders in progress. It is judged on sustained read speed and on nothing else. Nothing that travels over the public internet is a substitute during an edit, and no cloud tier on this page pretends to be one.

Delivery and review

Where a client watches and downloads. Small, hot, seen by people who are not you, and judged on how it looks and how fast it opens. This is the tier that is allowed to be expensive per terabyte, because it is the only one anyone outside the building ever touches.

Archive

Cold, large, rarely opened, and the cheapest per terabyte of the three. It exists for the day someone asks for a re-cut two years later, or for the version of you who deleted the drive. Its job is to sit still, stay intact, and cost as little as possible while doing so.

Read the three descriptions again and notice that they disagree about everything: speed, audience, size, and what a good price looks like. That disagreement is why a filmmaker who buys one product for all three ends up either overpaying for an archive or underserving a client. The rest of this page is about what belongs where, and about the two specific collapses that cost people work.

The sorting

What lives in each tier,
and where it belongs.

Working storage
Delivery and review
Archive
What liveshere
Camera originals, projectfiles, renders in progress
The export a client watches,plus the master they download
Delivered masters and theselects that made the cut
Whotouches it
You and the machinedoing the cut
Clients, producers,festival programmers
Nobody, untilsomebody asks
How fast itmust open
Instantly, while scrubbing,at full bitrate
In a second, in a browser,on someone else's connection
Same day is fine
What it isjudged on
Sustained read speed
How it looks andhow fast it plays
Cost per terabyte, andwhether the file is intact
Right sizefor a workingshooter
Terabytes, on a desk
Hundreds of gigabytes,online
Terabytes, growing everyyear and never shrinking
The failuremode
An edit over the internetstalls at the first scrub
A daily transfer ceiling, ora preview the client judgesyour work on
A retrieval fee, a minimumstay, or a deletion policynobody read

The three columns disagree on speed, audience, size and price. That disagreement is the reason they are three tiers and not one.

The first collapse

A review host is an archive
until the invoice stops.

This is the common one. The film is delivered, the link works, the client is happy, and the project folder gets deleted off the array to make room for the next job. The platform is now the only copy. Every platform that sells delivery has a written policy for what happens when you stop paying, and none of those policies were designed with your master in mind.

60 days

Vimeo source files after a lapse

Vimeo: if a paid membership lapses to Basic, source files stored on Vimeo are deleted after 60 days and cannot be recovered. The HD and SD versions remain.

2 years

Google, over quota

Google: if you are over your storage quota for 2 years, Google might delete your content across Gmail, Drive and Photos. It is written as a might, not a guarantee.

20 GB

Dropbox free link, a day

Dropbox: Basic accounts and trials are capped at 20 GB of shared-link traffic and up to 100,000 file downloads per day.

Take Vimeo’s wording seriously, because it is unusually clear. The delivery copies survive a lapse and the source file does not. That is a rational design for a hosting product: the thing that keeps the page working is cheap to keep, and the thing that is only useful to you is not. It is also a precise description of why a delivery platform cannot be your archive. What you would want back in two years is exactly the file the policy removes.
Google’s clause is softer and slower, and worse in one way: it applies to the account, not to one file. Going over quota and staying over quota puts everything in the same account at risk after two years, which is a strange amount of blast radius for a storage decision made to avoid a $9 subscription. Neither policy is a scandal. Both are the published behaviour of products that were never sold as archives.

The test

Ask one question about whichever product currently holds your finished work: if the card on file failed and nobody noticed for three months, what would still exist? If the honest answer is a compressed viewing copy, you do not have an archive. You have a delivery tier with sentimental value.

The second collapse

An archive is not, and never was,
is a delivery platform.

The opposite mistake is quieter and happens to more technical filmmakers. The archive is solved, correctly and cheaply, and then it starts getting used as the place clients are pointed at. A folder link goes out, a producer forwards it to eleven people, and the tier that was priced to sit still is suddenly doing the one job it was never priced for.

Dropbox Basic and trials
Plus, Family, Professional, Essentials, Standard, Business
Advanced, Business Plus, Enterprise
Shared-linktraffica day
20 GB
1 TB
4 TB
Filedownloadsa day
Up to 100,000
Unlimited
Unlimited

Dropbox's published daily ceilings for shared links, fetched 9 September 2026. A file-storage product has delivery limits because delivery is not what it is for. One 40 GB master forwarded around a client's team is already past the free ceiling for the day.

Raw object storage has the same shape of problem in a different currency. The cold rate is genuinely low, and then the bill for people watching arrives as egress, per gigabyte, priced per download rather than per month. Pay-as-you-go cold object storage bills the gigabytes you keep, and it bills the gigabytes that leave the bucket as well. That is a fair deal and a completely sane design. It is also a design in which the more your work gets watched, the more your archive costs, which is the opposite of what a delivery tier should do.
The cold tier here is explicit about this rather than clever about it. A cold master does not stream, does not embed and does not appear in a review room. It has to be re-hydrated first, which is a straight copy at your connection speed, size-verified on arrival, inside a monthly allowance of twice your cold pool that resets on the 1st. That restriction is the honest version of the same trade every archive makes. The tier is cheap because it is not doing delivery, and pretending otherwise would just move the cost somewhere you cannot see it.

The arithmetic

An archive is a bucket,
or a button next to the film.

Here is the comparison stated the way it should be stated, which is against us. Four terabytes of delivered masters and selects, kept for a year, with a project pulled back once. One column is a bucket you operate, billed by the gigabyte you keep and the gigabyte you move. The other is a switch inside the library that already holds the film you delivered.

uncompressed.io
Pay-as-you-go object storage
How itis priced
$20 per TB a month,in whole terabytes
By the gigabyte stored,with no tier to buy
4 TB keptfor a year
$960 at list; $720 on Max,where the first TBis included
Four terabytes billed at theprovider's per-gigabyte rate,month after month
Bringing oneproject back
Included, at your connectionspeed, up to twice your coldpool each calendar month
Billed as egress, by thegigabyte, each time a fileleaves the bucket
What ittakes to run
A switch next to the filmyou already delivered
A bucket, a lifecycle policy,a restore script anda bill to read
Who shouldpick it
A shop whose editor's timecosts more than its storage
Anyone comfortable owningthe plumbing

Our list prices in US dollars, fetched 9 September 2026 from our own pricing page. Our cold tier is on Max and Studio; Max includes 1 TB of cold and Studio 2 TB, then $20 per TB a month in whole terabytes. The other column describes how pay-as-you-go object storage is billed rather than any one provider's rate.

A bucket you run yourself will come in under that, and the gap is not going to be argued away. A filmmaker who is comfortable with a bucket, a lifecycle policy and a restore script will pay less running their own archive, and should. Nothing on this page is worth a markup to someone who already has the skill and does not mind the console. If that is you, the correct answer is a bucket, and the correct use of a hosting product is the delivery tier only.
What the higher rate buys is that archiving is a button beside the film you already delivered, in the same library, with no second account, no lifecycle rule, no restore job, no egress line and no separate invoice to reconcile at year end. Restores come back at line speed inside an allowance you never have to calculate. That is worth paying for when the hour it saves is billable, and it is not worth paying for when it is not. Both readers are right about their own situation, and only one of them is our customer.

Putting it in place

Splitting one library
into three, in an afternoon.

1

Draw the line at the render

Everything that existed before the final render is working storage and stays on local disk or the array. Everything that exists after it is either delivery or archive. This single line removes most of the ambiguity, because it is the point at which files stop changing.

2

Put one file in the hot tier per project

The viewing export, at a high bitrate, is what a client opens. It is small relative to the master and it is the only thing that has to be fast. On the hot side that is 100 GB on Lite, 500 GB on Pro and 1.5 TB on Max, and bandwidth is not metered, so the number of people who watch it does not change the bill.

3

Send the master and the selects to cold

The delivered master and the selects that made the cut are the off-site copy of what a reshoot could not replace. They go cold the day the grade is approved. Archiving frees the hot space immediately, and a cold master is one re-hydration away from the review room when a re-edit becomes real.

4

Count your copies, not your terabytes

The Canadian Centre for Cyber Security puts it as three copies, one original and two backups, on two different media types, with one kept off site. The cloud archive is a strong candidate for the off-site copy. It is not, on its own, all three.

The two sentences worth remembering

A review host keeps working until the invoice stops, so it is never the only copy of a master. An archive gets cheaper the less it is touched, so it is never the link you send a client. Everything else on this page is arithmetic in service of those two lines. If you want the per-terabyte detail and the year-by-year numbers, the hot versus cold guide works the same example through in full.

Questions

Frequently asked

How much cloud storage does a filmmaker actually need?

Far less than you shot, because only one of the three tiers belongs in the cloud twice over. Camera originals and project files stay on the local disk or array the edit runs from. What goes online is the viewing export a client opens, the delivered master, and the selects that made the cut. For a shooter finishing a project a month that is a few hundred gigabytes of hot storage and a few terabytes of archive by year end: 100 GB hot on Lite, 500 GB on Pro, 1.5 TB hot plus 1 TB cold on Max.

Can I edit straight off cloud storage?

No, and no product should tell you otherwise. An edit needs sustained read speed and instant scrubbing, and nothing that travels over the public internet is a substitute during a cut. Working storage is a fast local disk or a small array attached to the machine doing the work. The cloud tiers exist for what happens after the render, not during it.

Is a review or hosting platform a safe place to keep finished work?

Only while you are paying. Vimeo states it plainly: if a paid membership lapses to Basic, source files stored on Vimeo are deleted after 60 days and cannot be recovered, while the HD and SD versions remain. That is a delivery product behaving exactly as designed. It is not an archive, and it should never be the only copy of a master.

Is it cheaper to run my own archive bucket?

Usually yes. Pay-as-you-go cold object storage bills by the gigabyte you actually store, with no tier to buy and nothing bundled around it, so a bucket you operate yourself comes in under a managed cold tier. Four terabytes on the cold tier here is $960 at list for a year, or $720 on Max where the first terabyte is included. If you are comfortable with a bucket, a lifecycle policy and a restore script, run your own archive and spend the difference on something else.

What actually happens when I archive a master here?

It leaves the live library. A cold master does not stream, embed or appear in a review room until you bring it back. The hot space it used is freed immediately, restores are size-verified on arrival, and the monthly re-hydration allowance is twice your cold pool, resetting on the 1st. Cold storage is on Max and Studio.

How large a file can I upload?

Up to 5 TB per file, subject to the storage available on your account. Moving masters between hot and cold has its own threshold: the web dashboard handles files up to 20 GB, and anything larger moves through the macOS app part by part, so a laptop that closes mid-transfer resumes instead of restarting.

What is the 3-2-1 rule, and does a cloud tier satisfy it?

The Canadian Centre for Cyber Security states it as three copies of your information, one original and two backups, saved on two different media types, with one copy kept off site. A cloud archive is a good candidate for the off-site copy. It is not the whole rule on its own, and a single provider holding your only master is the exact arrangement the rule exists to prevent.

Size the hot tier, then price the cold one

Storage is the only meter here. Lite is 100 GB hot at $9 a month, Pro 500 GB at $25, Max 1.5 TB hot plus 1 TB cold at $75, Studio 2 TB hot plus 2 TB cold at $250. Blocks beyond a plan are $40 per TB hot and $20 per TB cold, a month.