Frame.io storage
Frame.io storage is full.
Most of what is in there is already delivered.
Frame.io storage is an account-level pool, and a project you mark inactive keeps consuming it unless the account has archival storage. Frame.io has documented that archival storage will not be supported going forward. So the standard advice to archive finished projects inside Frame.io no longer describes the product. Here is what the plan actually holds, what happens at the cap, and where finished work can live instead.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
Updated September 2026
The mechanism
Storage is one pool now,
and finished projects still sit in it.
The reason the account filled up is not that you shot too much. It is that a review tool measures storage at the account level, and nothing you did to a finished project moved it out of the way.
Two documented behaviours combine here, and reading them together explains the whole problem. First, Frame.io storage is pooled at the account: licenses purchased through Adobe grant the account pooled storage, and cancelling licenses reduces that pool. Frame.io states plainly that, depending on how much storage you are already using, that reduction can put the account over its storage quota and result in it becoming locked. Storage is therefore a single number for the whole account, not an allowance each project carries around with it.
Second, and this is the part most workflow advice has not caught up with, marking a project inactive does not release its bytes on its own. Frame.io’s own documentation says that if your account does not have access to archived storage, inactive projects will use up your active storage space, and that accounts with archival storage have them counted toward that type instead. Then the V4 update guidance for Free, Pro and Team accounts closes the escape hatch: Archival Storage will not be supported going forward, and storage will be just one source now, with the ability to set active and inactive projects.
Put those two sentences side by side and the conclusion is unavoidable. Every article that tells you to solve a full Frame.io account by archiving old projects inside Frame.io is describing a tier that is documented as not supported going forward. The active and inactive setting is still worth using to keep a workspace legible. It is no longer a storage strategy. If you have been marking delivered jobs inactive and wondering why the number in Settings never moves, that is why.
Why it fills faster than you expect
Frame.io accepts any file type uploaded to a project, and only some of them get the review tooling. Deliverable exports, masters, stills, decks and PDFs all land in the same pool as the cuts you are actually reviewing.
The asset ceiling is not the constraint
Frame.io states you can upload and share assets up to 5 TB in size. Individual files are rarely what breaks an account. The accumulated residue of finished jobs is.
Two allowances, not one
Cloud storage and Mounted Storage are listed separately per plan on the pricing page. Read the banner carefully before you start deleting, because it names which limit you hit.
The bytes are not the problem, the meter is
A delivered project is inert. It gets watched occasionally and edited never. Paying for it inside a tool priced around members and review rounds is paying the wrong rate for a file that only needs to sit still and stream.
What the plan holds
The published numbers,
and what happens at the ceiling.
Before deciding what to move, it helps to see exactly how much room the plan gives you and what the documented consequence of exceeding it is. Everything in this table is from Frame.io’s own pages, fetched today.
All figures from frame.io/pricing and the Frame.io help center, fetched 7 September 2026. Frame.io publishes no currency next to its prices, so they are shown exactly as published. Paying annually is advertised as saving 13 percent, but no annual dollar figure is published for any plan. Storage add-ons are available in 250 GB increments with no published price, and adding a member increases the account's storage at the plan's per-member rate. Frame.io states that assets up to 5 TB can be uploaded and shared. The archival line is from the V4 update guidance written for Free, Pro and Team accounts.
What the cap actually does
The triage
Three piles,
only one of them belongs in a review tool.
Open Settings and read the Usage tab
Overages are shown there to the account owner, and the banner names which limit you hit. Do this before deleting anything, because a member or workspace limit is a different problem from a storage one and deleting media will not fix it.
Split live rounds from finished work
A project is live if someone is still leaving notes on it. Everything else is finished, whatever its active or inactive setting says. On most accounts that have been running for a year or more, the finished pile is the larger one by a wide margin.
Move the finished pile to flat storage
Deliverable exports and the masters beside them go somewhere priced by the byte, where the client link keeps working and no seat is consumed. Upload the export that clients play, and put the master beside it as a download when the job warrants one.
Send the new link, then delete the old project
Confirm the new page plays for the client before you reclaim the space. Once the delivery lives somewhere that is not competing with your review rounds, the Frame.io pool only has to hold work that is actually in progress.
The one step worth slowing down on is the third. A delivery link is a promise with a long tail: the client, their agency, their new marketing hire eighteen months later. Moving it somewhere the link survives is the whole point of the exercise, which is why the last step is to verify the new page before deleting the old one. If the cut changes after delivery, you can replace the file without changing the link, so the address you handed out stays correct.
Side by side
A delivered project,
in each of the two places.

Frame.io figures from frame.io/pricing and the Frame.io help center, fetched 7 September 2026, shown with the dollar sign exactly as published since no currency is stated. uncompressed.io figures are our own published plan rates. Read the last row honestly: Frame.io accepts a far larger single asset than we do, and 50 GB per file is a real ceiling here.
Two rows deserve to be read carefully rather than skimmed. The third row is the one this site is built on, and it is easy to overstate, so here it is exactly. Frame.io does not discard your master. Its documentation says it encodes the files into HTML5 videos to play seamlessly on the web while still storing the original file available for download, and that the MP4 proxy bitrates are variable based on resolution. That is a sound design for review, where instant scrubbing beats fidelity. Our difference is narrow and specific: we make no second copy at all, so the bytes the client receives are the bytes you exported.
The last row runs against us and stays in the table for that reason. Frame.io states that assets up to 5 TB can be uploaded and shared. Our ceiling is 50 GB per file. For a delivery export that is not a constraint, because a delivery export is an H.264 or HEVC file. For an uncompressed or lightly compressed camera master of feature length, it is a real one, and you should know that before you plan a migration around this page.
What the other side costs
Flat storage,
and no seat inside the price.
$9
Lite, a month
100 GB, or $90 a year. Enough for a working year of delivery exports on most small shops.
$25
Pro, a month
500 GB, or $250 a year. The same figure as one Frame.io Team member, except that here it is the entire bill.
$75
Max, a month
1.5 TB hot and 1 TB cold, or $750 a year, with 3 seats.
$250
Studio, a month
2 TB hot and 2 TB cold pooled, or $2,500 a year, with 5 seats.
The shape of the bill is the argument, not the size of it. Frame.io charges per member and grows your storage as the member count grows, which is a rational way to price a room where several people work every day. A delivered project has no members. It has bytes and it has plays. Here, storage is the only meter: there are no bandwidth caps, and the pricing page states plainly that there is no per-view charge and that external client viewers do not require a paid team seat. A delivery page watched once and a delivery page watched by an entire marketing department cost the same.
Storage blocks beyond a plan are $40 per TB hot and $20 per TB cold, a month, at the same price on every paid plan. Cold storage is included on Max, at 1 TB, and on Studio, at 2 TB. That gives the finished pile somewhere to go that is neither a review seat nor a deletion. There is also a free Starter plan holding 5 GB and one film at a time, with no credit card, which is enough to test whether a client link behaves the way you want before you move anything real.
Honest framing
Frame.io is the better review product,
and this page is not trying to change that.
This is not a courtesy sentence placed here to sound balanced. It is the reason the page is scoped the way it is. If you take the advice above and move your live rounds along with your finished work, you will have made your week worse to save a monthly rate.
Review is a real product, not a feature
Comment threads anchored to frames, versions stacked against each other, approvals with a trail, notes from four people that have to be reconciled before a grade locks. Frame.io has years of refinement on exactly that, and a hosting product does not replace it by adding a comment box. If your day is review rounds, your account is doing the job it is priced for.
The members you already pay for are buying something
If five people are in projects every day, the per-member rate is not waste. Keep it. The case for moving finished work is strongest precisely when the seats are justified and the storage is being consumed by jobs nobody has opened in months, because then the two costs are pulling against each other inside one number.
Move the residue, not the workflow
The correct outcome of this page is a Frame.io account that holds current work and fits inside its plan again, plus a separate flat-rate library holding deliveries and masters. Two tools, each on the meter that matches what it does. Not a migration.
What is actually being claimed
Questions
Frequently asked
Does marking a Frame.io project inactive free up storage?
Not on its own. Frame.io states that if your account does not have access to archived storage, inactive projects will use up your active storage space, and that accounts with archival storage count them toward that type of storage instead. Frame.io also states, in its own V4 update guidance for Free, Pro and Team accounts, that Archival Storage will not be supported going forward and that storage will be just one source now, with the ability to set active and inactive projects. On a current account, an inactive project is still sitting in the same pool as the work you are reviewing today.
Any advice telling me to archive finished projects inside Frame.io is out of date, then?
Yes, if it is describing a separate archival tier you can move things into to reclaim space. That tier is documented as not supported going forward. The active and inactive setting still exists and is still useful for keeping a workspace tidy, but tidiness and storage are now two different problems. Check the date on any article that tells you otherwise.
What actually happens when I go over the Frame.io storage cap?
Frame.io shows a banner at the top of the page naming the limit you hit, and the banner types it lists include storage limits, member limits, guest member limits, workspace limits and, on the Free plan, a project limit. Overages are visible to the account owner under Settings, in the Usage tab. Frame.io's stated remedy is to remove or delete the overage, and if it is not resolved after a grace period the account can be locked, with affected users directed to support. No Frame.io page publishes a per-GB overage charge, so this is a wall rather than a meter that keeps running.
How much does extra Frame.io storage cost?
Frame.io publishes that storage add-ons are available in 250 GB increments and that adding a member also increases the account's storage at the plan's per-member rate. It does not publish a price for the increment on any page. Figures for it circulate in search results and are not on Frame.io's own pages, so ask Frame.io for the number rather than budgeting from something you read elsewhere.
Is Frame.io throwing away my original file when it makes a preview?
No, and any page that says so is wrong. Frame.io's own upload documentation states that it encodes the files into HTML5 videos to play seamlessly on the web while still storing the original file available for download, and that MP4 proxy bitrates for streaming are variable based on resolution. The original survives. The difference here is narrower: we make no encode at all, so the file the client plays is the file you uploaded.
Should I move everything out of Frame.io?
No. Move the finished pile and keep the live rounds where they are. Frame.io is the better product for active review, and a hosting product does not replace comment threads and approvals. The argument on this page is only that a review tool's storage is an expensive and fragile place to park work that nobody is reviewing.
What happens to a delivery link when the cut changes after all?
Replace the file and the link stays the same. The film keeps its row and its slug, so every link, embed and share card you already sent keeps working. That matters most for the delivered pile, because those are the links you no longer control the distribution of.
Give finished work a flat rate
Lite is $9 a month or $90 a year for 100 GB. Pro is $25 or $250 for 500 GB. Storage is the only meter: there are no bandwidth caps, and no viewer needs a seat.
Sources
- 1.Frame.io pricing: Free, Pro, Team and Enterprise plans, member counts, cloud and mounted storage, annual discount, storage add-ons, share links and the free trial (fetched 7 September 2026)
- 2.Frame.io Help Center: what to expect when updating to V4 (Archival Storage will not be supported going forward; storage is one source; V4 base storage per plan) (fetched 7 September 2026)
- 3.Frame.io Help Center: managing active and inactive projects (inactive projects use active storage unless the account has archival storage) (fetched 7 September 2026)
- 4.Frame.io Help Center: plan limits in Frame.io (banner types, the Usage tab, removing the overage, grace period and account locking) (fetched 7 September 2026)
- 5.Frame.io Help Center: Frame.io cloud storage (pooled account storage; going over the quota can lock the account) (fetched 7 September 2026)
- 6.Frame.io Help Center: adding storage to my account (250 GB increments, per-member rates, adding a member increases storage) (fetched 7 September 2026)
- 7.Frame.io Help Center: uploading your media (5 TB asset ceiling, any file type accepted, HTML5 encodes with the original still stored and available for download, variable proxy bitrates) (fetched 7 September 2026)
- 8.Frame.io Help Center: getting started, what are the pricing plans you offer (Free plan project limit, unlimited projects on Pro) (fetched 7 September 2026)
- 9.uncompressed.io pricing: plans, hot and cold storage, storage blocks, no bandwidth caps and no per-view charge
- 10.uncompressed.io Terms: storage is the only meter, there are no bandwidth caps, and the file is streamed byte for byte