One file, one client, one deadline
How to send a 50 GB video to a client
and let them watch it, not just wait for it.
A single very large master breaks the assumptions of every transfer tool: the link expires, there is no player, and the client has to complete a blind download before they can see whether the grade is right. Hosting the file answers a different question. Here is the arithmetic, the honest limits on both routes, and the one distinction that decides which one you need.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
Updated September 2026
The shape of the problem
There are two routes,
and they answer different questions.
You have one file of about 50 GB and a client waiting on it. Route one moves the bytes and stops. Route two puts the file somewhere permanent and sends an address. Almost every argument about large-file delivery is really an argument about which of those two things the job needs.
The transfer route is honest about what it is. It is a courier. The bytes arrive intact, the recipient gets a download, and the service is finished. That is a good product when the delivery is a single event, and it should not be talked down.
It has three costs that only show up at this size. The link expires, because expiry is how a courier reclaims its shelf, so the client who comes back for the master in four months finds a dead page. There is no player, so nothing about the film is visible from the link itself. And the download is blind: your client has to commit to pulling 50 GB, in full, before they can see whether the third act works or whether the grade shifted. If the answer is a note rather than an archive, you have made them buy an hour of bandwidth to give it.
The hosting route inverts that. The file sits at a permanent address, the client opens a page and presses play, and the original is a button on the same page when they want to keep it. The cost of that route is a storage bill you carry between jobs, and a per-file ceiling. Both are real, and both are below.
Sanity check
What 50 GB actually holds
depends entirely on the data rate.
Before choosing a tool it is worth knowing whether your file is really 50 GB or really 200 GB. File size is data rate multiplied by running time, and nothing else. This table is arithmetic you can check, not a claim about any codec.
Arithmetic, not a vendor figure. Gigabytes are counted as 1,000,000,000 bytes and megabits per second as 1,000,000 bits per second; times are rounded to the nearest minute. Read the table in both directions: it tells you how long a film can run before it crosses 50 GB, and it tells you that an eight-minute piece can cross it on its own if the master is rich enough.
Two conclusions fall out of it. The first is that 50 GB is a lot of delivery export and not much finishing master. A 10 Mbps web file would have to run eleven hours to reach it; a 400 Mbps finishing master reaches it in seventeen minutes. If your file is 50 GB, it is almost certainly the second kind.
The second is that the bottom half of that table is where storage plans in this industry start to bite. A feature-length finishing master is not a 50 GB problem. It is a several-hundred-gigabyte problem, and the honest answer for it is at the end of this page.
The routes side by side
The difference is not the transfer,
what the client can do with it.
All three of these move a large file successfully. What separates them is what exists at the other end once it has moved, and what the meter is counting while it sits there.
Frame.io figures read from frame.io/pricing and the Frame.io Help Center on 7 September 2026; full citations in the sources below. The transfer-link column is deliberately written without numbers: no individual transfer service was fact-checked for this page, so quoting a cap, a price or an expiry window here would be inventing one. The per-gigabyte arithmetic has its own page, with its rates cited there.
Frame.io deserves the middle column and deserves to be taken seriously in it. It accepts assets up to 5 TB. It preserves the file you uploaded and offers it for download, alongside a smaller proxy, so nothing is destroyed by the encode. And it is the better review product: Shares exist to send media out for review, with viewer permissions that gate commenting and downloading, and an expiration date when a link should not outlive the round. If review workflow is the centre of the job, that is where the job belongs.
The difference worth understanding is what the client watches. Frame.io encodes a separate HTML5 version for web playback and keeps the original beside it. We do not make a second version at all. There is no transcode at upload, no transcode at playback and no rendition ladder, so what streams is the object you uploaded. The honest consequence of that is a real trade against us: with no lower rendition to fall back on, a thin connection buffers rather than quietly switching your client to a softer version of the film.
The accuracy point most pages skip
Host both files.
A 50 GB master is a download, not a stream.
This is the single most important thing on this page, and it is the thing large-file guides routinely get wrong. Hosting a file and streaming a file are not the same promise.
A file at 50 GB is almost certainly ProRes, DNxHR or camera RAW. Browsers do not decode those. There is no codec allowlist here and no re-encode step, so a ProRes 422, ProRes 4444 or DNxHR master is stored byte for byte and served as a download at full fidelity, but it will not play in a tab. Camera RAW, meaning BRAW, R3D, ARRIRAW, N-RAW, X-OCN or ProRes RAW, is never uploaded raw at all: finish to HEVC or ProRes first.
So the workflow that actually delivers is two files, not one. Put the big master up so the client can pull the real thing. Put a browser-decodable HEVC or H.264 export up alongside it so they can press play, watch the cut and leave a note without committing to a 50 GB download. Both live under the same account, on the same page structure, and the client only ever gets one link.
Anyone who tells you that a ProRes master streams in a browser is describing a transcode they are not admitting to. We do not run one, which is exactly why we have to be blunt about this: the fidelity guarantee and the playback guarantee are two different promises, and only the first one covers a finishing master.
Export the screening file first
A high-bitrate HEVC or H.264 at the rate the film deserves. There is no platform ceiling to duck under, because nothing re-encodes it. This is the file the client presses play on.
Upload the master beside it
Up to 5 TB per file, in 10 MB parts, on lanes that adapt to your line. ProRes and DNxHR are stored and served at full size; the browser simply will not play them, and the page hands them over instead.
Decide who gets in
Five visibility modes sit on each film: Private, Password, Unlisted, Public and Embed only. Change the mode whenever you like; the address does not change with it, so a film can be gated until the invoice clears and opened afterwards without reissuing the link.
Leave it where it is
There is no expiry clock, so the months-later request for the master is a click rather than a drive hunt. Storage is the only meter; nobody is billed for the client pressing play again.
Our own limits, stated plainly
5 TB is the ceiling, and
the quota usually stops you first.
The per-file ceiling is the number people quote, and it is rarely the number that decides anything. Both are worth understanding before you plan a delivery around either one.
5 TB
Per file, every plan
The ceiling does not rise with the price of the plan. What rises is total storage.
In-browser
Where the check runs
The size test happens in your browser before the upload starts. It is a client-side check, not a server-side guarantee.
5 GB
Free Starter quota
One film at a time. A 50 GB file is refused by the quota long before the ceiling is relevant.
60
Attempts per 10 MB part
A dropped connection costs 10 MB, not the upload. It does not survive a reload or a closed tab.
Plan prices and storage caps verified in code on 7 September 2026 and published on the pricing page. Room beyond a plan is $40 per TB of hot storage and $20 per TB of cold storage, a month. Storage is the only meter: views, viewers and downloads are not counted on any plan, including the free one.
Be careful with the word ceiling
The 5 TB test lives in the uploader, in your browser, and it runs before any bytes move. That is good for you, because an oversized file is refused in a second rather than at 90 percent at three in the morning. It is not a server-side guarantee, and we are not going to describe it as one. What the server enforces is your plan quota: it checks the size of the incoming file against the space you have left and refuses it if it does not fit.
That is why the free plan is the wrong place to plan a 50 GB delivery. Starter is 5 GB and one film at a time. It is enough to check that the player does what this page says it does, and it is not a delivery plan for a master this size. Pro at 500 GB is the smallest plan that takes one without arithmetic; Max at 1.5 TB hot and Vault at 2 TB hot are the ones that take several.
Getting it up there
What the uploader survives, and
what it does not.
A 50 GB upload is a long one on any connection, so the failure behaviour matters more than the headline speed. Here is exactly what happens, with nothing rounded up in our favour.
A dropped line costs 10 MB
The file is cut into 10 MB parts and each part gets up to sixty attempts, backing off between them and waking the moment the browser reports the connection is back. Lanes run in parallel, widening on clean parts and halving when the line degrades.
Browsing the site is fine
The transfer runs above the page you are on, so moving around the app does not touch it. You can set up the next film while the master is still climbing.
A reload or a closed tab ends it
The browser throws the file handle away, and no amount of engineering gets it back. What is kept is the progress: a resume panel lists the interrupted file, you drop the same file in again, and it continues from the last finished part rather than from zero.
The claim we will not make is the one you have read elsewhere. An upload here does not survive a closed laptop. If the lid goes down mid-transfer, the transfer stops, and finishing it means re-dropping the same file so the completed parts can be recognised. Every other tool that promises otherwise is either running a desktop application or quietly restarting.
One related note if the master is destined for the archive rather than the shelf. Cold storage is available on Max and Vault, and the web dashboard moves masters up to 20 GB into it; anything larger goes through the macOS app, which moves the file part by part. A cold master does not stream, embed or appear in a review, so retire a delivery to cold once the client has what they need, not before.
When we are the wrong answer
For a one-off handoff,
pay the courier and be done.
There are deliveries this page does not win, and there is no version of this argument where pretending otherwise helps you.
The first is size. Above 5 TB in a single file, our uploader refuses it in the browser and the conversation is over. A camera-original haul or a card dump going to a post house can arrive as one object past that line, and no plan we sell takes it. A per-gigabyte courier is built precisely for that job.
The second is shape. If the file goes out once, to one person, who will ingest it into their own storage and never open it in a browser, then everything a host provides is overhead. Nothing in that job needs a player, a comment, a password page or a permanent address. It needs the bytes moved once and then forgotten, and paying for that single trip is cheaper than carrying a subscription between jobs.
The logic runs the other way just as hard, which is the whole reason this page exists. Deliveries that repeat, that get watched, that collect notes, that have to be re-sent to a second stakeholder in November, are exactly what a per-delivery meter punishes and a storage meter ignores. The same master pulled by five people twice each is ten billable deliveries on one model and one stored file on the other. If you want that arithmetic done properly, with real published rates, the MASV break-even page works it out plan by plan.
Four questions that settle it
Will anyone press play?
If the client needs to watch and respond, they need a player, and a blind 50 GB download is not one. If the file is going straight into someone else's ingest, a courier is enough.
Will anyone ask for it again?
A second request months later is free on a permanent address and a fresh delivery on an expiring one. Count how often that has happened to you in the past year, honestly.
Is the single file over 5 TB?
Then this is not the tool, and no plan changes that. Split the delivery, or use a service with no per-file ceiling and accept its own trade-offs.
What is the meter counting?
Match it to the shape of the work. One-off bulk handoffs belong on a per-delivery meter. Watched, revisited, re-sent deliveries belong on a storage meter.
The short version
Upload two files,
then send one address.
Send the 50 GB master to a place that keeps it and hands it back on demand, and put a browser-decodable export next to it so the client can watch the film instead of waiting for it. Pick a plan with room: Pro holds 500 GB, Max 1.5 TB hot, Vault 2 TB hot, and the free Starter plan’s 5 GB is not in this conversation. Expect the upload to want an uninterrupted tab, not an uninterrupted week. And when the job is genuinely one trip for one recipient who will never look at it in a browser, use a courier and spend the difference on the grade.
The rest of the handoff, including what belongs in a complete delivery package, is covered in delivering final video files to clients, and the quality argument behind all of it is in sending large video files without losing quality. Plan prices and storage caps are set out in full on the pricing page.
Questions
Frequently asked
What is the largest single file I can upload here?
5 TB, and the number is the same on every plan. The check runs in your browser before any bytes move, so an oversized file is refused immediately rather than halfway through the night. What the server enforces is your plan quota, and on the free Starter plan that quota is 5 GB, so a 50 GB file is stopped by the quota long before the per-file ceiling matters.
Can my client stream a 50 GB master in the browser?
Only if the browser can decode it, and a file that size is usually a codec no browser decodes. H.264, HEVC and AV1 stream at whatever bitrate you uploaded, because there is no transcode step anywhere. ProRes 422, ProRes 4444 and DNxHR are hosted for client download rather than played in a tab. Camera RAW is never uploaded raw at all: finish to HEVC or ProRes first.
So what do I actually upload for a 50 GB delivery?
Two files. The big master goes up so the client can download the real thing, and a browser-decodable HEVC or H.264 export goes up alongside it so they can press play and give a note without waiting for 50 GB. That is the honest workflow, and it is the same one studios have always used: an archive file and a screening file, under one link instead of two.
Which plan do I need for a 50 GB file?
One with room to spare. Pro holds 500 GB for $25 a month or $250 a year and takes a 50 GB master comfortably. Max at 1.5 TB hot and Vault at 2 TB hot are the ones that take several without thinking about it. Starter is free with 5 GB and one film at a time, which is enough to test the player and nothing like enough for a 50 GB master.
What happens if my upload drops halfway through?
The file goes up in 10 MB parts, and each part gets up to sixty attempts, backing off and waking the moment your connection returns. A dropped hop costs 10 MB, not the upload. Moving around inside the app does not interrupt it. Reloading the page or closing the tab does end it, because the browser throws the file handle away. Progress is remembered, so you drop the same file in again and it continues from the last finished part. Nobody here will tell you that you can shut the lid and walk away.
Is a transfer service ever the better answer for this?
Yes, and often. If the delivery is a one-off, if the recipient will ingest it into their own storage and never watch it in a browser, and if nobody will ever come back for it, then a per-gigabyte courier is cheaper and simpler than carrying a subscription. Above 5 TB in a single file it is the only answer we have, because our uploader refuses the file.
Does the link expire?
No. A hosted film is a library entry, not a timed transfer, so there is no expiry clock to beat and no dead link when the client comes back in November. You control access instead: Private, Password, Unlisted, Public or Embed only, changeable without changing the URL.
Room for the master, and a page that plays it
A 50 GB file needs a plan with space left over. Pro holds 500 GB, Max holds 1.5 TB hot, Vault holds 2 TB hot. Storage is the meter: views, viewers and downloads are not counted on any plan.
Sources
- 1.Frame.io pricing (fetched 7 September 2026: free plan $0 with 2 GB storage, up to 2 members and up to 2 projects; Pro $15 per member a month with 2 TB included; Team $25 per member a month with 3 TB included; passphrase-protected shares and share link expiration listed as Pro-tier features)
- 2.Uploading your media, Frame.io Help Center (fetched 7 September 2026: maximum asset upload up to 5 TB; Frame.io encodes files into HTML5 versions for web playback while still storing the original file available for download)
- 3.How can I download files, Frame.io Help Center (fetched 7 September 2026: a download offers the original file or a smaller proxy file)
- 4.Shares in Frame.io, Frame.io Help Center (fetched 7 September 2026: Shares are external links for sending media out for review; an expiration date removes access on a set date and time; viewer permissions gate commenting and downloading)
- 5.uncompressed.io pricing: plans, storage and unmetered views (product page; plan prices and storage caps verified in product code, 7 September 2026)
- 6.uncompressed.io terms: storage is the only meter (product page; no bandwidth caps and no per-view charge, verified 7 September 2026)