What happens when you hit Vimeo's 2 TB bandwidth limit.
Notices, then outreach, then seven days, then embeds that stop playing.

The reason this matters more than a storage cap is timing. Storage fills up predictably, a little every week, and you see it coming. Bandwidth is spent by other people. It climbs when a festival links your film, when a client circulates a cut internally, when a case study lands on a homepage, when a reel gets picked up. The month you cross 2 TB is almost always the month the work is finally being watched, and the mechanism Vimeo has for that month ends, at its worst, with the work not playing.

What counts toward the number is broader than plays. Vimeo counts playing a video, loading the player and the thumbnail image, downloading a video, video traffic, and live streaming. A page that carries your embed and gets scrolled past spends a little bandwidth without a single view. A client pulling a large master down spends a lot.

One more clause worth knowing before anyone gets clever. Vimeo states that the limit applies to all jointly controlled accounts, so opening multiple accounts does not increase your bandwidth limit. Splitting a library across two logins to buy 4 TB is not a workaround; it is the thing the sentence was written to stop.

Studio is the interesting row. It trades the monthly cap for 36 TB of yearly bandwidth, which averages 3 TB a month but lets a single month spike without triggering anything, and it costs $400 a month billed annually. That is a real answer to a real problem, and if your delivery is genuinely in that range it is worth pricing out. It is also roughly five times the Advanced price, and it is not listed on the pricing page, so most people escalating through the self-serve tiers never learn it exists until Vimeo tells them.

Read the 4K row honestly, in both directions. It is the worst case and it is also the case a filmmaker cares about: 1,212 complete plays of a ten-minute film is not a viral hit, it is a good festival week or one decent newsletter placement. But a real audience is a mix. Vimeo serves several renditions per file, from 240p upward, most viewers are not watching on a 4K panel, and the published bitrates are ceilings rather than averages. So a typical account gets considerably more viewing out of 2,000 GB than the top row suggests. The top row is what you get when your audience is exactly the audience you wanted: people watching graded work at full resolution.

Downloads are the other way to spend a month quickly, because they are counted the same as plays. Vimeo allows up to 300 GB per file on every plan. A 60 GB ProRes master delivered to a client thirty-three times is 1,980 GB, which is the entire monthly allowance spent on file transfer, with nothing left for anyone to watch anything. If your Vimeo account doubles as a delivery mechanism, the cap arrives far sooner than any viewing figure would predict.

When Vimeo documents what to do about sustained overage, it names one route: upgrading to a Vimeo Custom or Enterprise account, where pricing depends on the expected bandwidth usage. The only pricing language published anywhere near it is that bandwidth is priced per GB and includes volume discounts. There is no per-GB figure, no table, no calculator.

That is worth stating plainly rather than guessing at, because plenty of pages on the open web will hand you a number. Vimeo has not published one. Anyone quoting a Vimeo overage rate to you is either repeating a figure from a specific negotiated contract or inventing it. The practical consequence for planning is simple: past a certain amount of delivery, Vimeo stops being a service with a price you can look up and becomes a service with a price you have to ask for. For a five-person production company, the meeting is the cost, before the invoice is.

Vimeo says it set the limit so that 99% of its users will never reach it, and that claim is credible. A portfolio with a dozen films and a few thousand views a month is nowhere near 2,000 GB. A wedding filmmaker delivering to one couple at a time is nowhere near it. If your monthly delivery is in the low hundreds of gigabytes, the cap is a line in a help article you will never trip, and switching platforms to avoid it would be solving a problem you do not have.

The rest of the case for staying is real too, and it has nothing to do with bandwidth. Vimeo’s player is widely recognised and clients trust the look of it. Its marketing tools, its OTT product, its collaboration and its distribution features have no equivalent here, and this site will not pretend otherwise. If those are what you are paying for, keep paying for them. This page is for the accounts on the other side of the 99%: the ones whose work is being watched enough that the meter has started to matter, and who would rather not have a meter on being watched at all.

The trade is not free and it is not hidden. Vimeo gives you 7 TB of storage on Advanced; Max here gives 1.5 TB hot plus 1 TB cold at the same monthly figure, and Vimeo’s $75 is the annual-billing price where this one is the month-to-month price. If your problem is keeping a very large library parked online cheaply, Vimeo’s storage-heavy tiers are better value and you should take them. If your problem is that the library is being watched, the meters point in opposite directions.

The second trade is technical. There is no adaptive ladder here, because the player streams the exact file you uploaded rather than a set of re-encoded renditions. A viewer on a weak connection buffers instead of being silently dropped to a mushy version of your grade. That is deliberate, and for a colourist or a DP sending graded work it is the right default, but it is a genuine downside for a public page with an unpredictable audience, and it belongs in the comparison rather than in the small print. If your priority is that everyone everywhere gets a frame instantly, an adaptive platform is doing something this one does not.

Two related pages carry the rest of the detail: what Vimeo actually delivers at 4K and the uncapped alternative in full.

If the answer is to move, do it in an order that keeps the embeds alive: bring the library across first, repoint the embeds, then cancel. The leaving Vimeo checklist covers the sequence, including which Vimeo plans expose original files and which do not. Nothing here is re-encoded on arrival, so the file that lands is the file you uploaded.