Bitrate ceilings, in public

Video hosting with no bitrate limit.
A 200 Mbps master streams at 200 Mbps.

Every platform that re-encodes your upload has a number above which your file cannot be delivered. Vimeo publishes its ladder. YouTube publishes nothing. Here is what both actually say, and what a host with no ladder at all does with the same file.

See plans and storage

No credit card required. Cancel any time.

Updated September 2026

What a bitrate limit actually is

A host that re-encodes has a ceiling:
it publishes a ladder, or it publishes nothing.

When a platform re-encodes your upload, it does not produce one file. It produces a set of renditions, one per resolution, each with a target bitrate. That set is the ladder, and the top rung of the ladder is the most any viewer can ever receive, no matter what you sent.

This is the part of hosting that is invisible until you compare a delivered frame with your own export. Your grade, your grain, your dark scenes and your slow pans all survive the upload. They do not survive the rung. A ceiling of a few dozen megabits per second is not a conspiracy, it is a sensible engineering choice for a platform whose job is to play video to millions of people on unknown connections. It is simply not the same job as delivering a master to a client who is about to sign off on it.
There are three honest positions a host can take, and the industry contains all three. Publish the ladder, as Vimeo does. Publish nothing about delivery, as YouTube does. Or have no ladder at all, which is the position described in the rest of this page.

Vimeo, 4K rung, standard H.264 ladder

22 Mbps maximum

Vimeo, 4K rung, HDR and above-4K HEVC ladder

16 Mbps maximum

uncompressed.io, any file

your file's own bitrate
050100150200Mbps

Vimeo figures are the maximum video bitrates published in its help centre, fetched 5 September 2026. YouTube has no bar on this chart because Google publishes no delivered bitrate at any resolution; the bitrate tables on its help pages are recommended upload settings. The 200 Mbps bar is an example of a file, not a platform figure: with no ladder, the delivered bitrate is whatever the uploaded file's bitrate is.

The published ladder

“The bitrates listed for each resolution
are a maximum.

Vimeo deserves credit for publishing this at all. The help centre lists a video bitrate for every rendition it produces, on two ladders: a standard H.264 ladder, and an HDR and above-4K ladder delivered in HEVC.

Vimeo standard H.264 ladder
Vimeo HDR / above-4K HEVC ladder
720p
2.5 Mbps max
2.2 Mbps max
1080p
7 Mbps maxlisted at 60 fps
5 Mbps max
2K
12 Mbps max
10 Mbps max
4K
22 Mbps max
16 Mbps max
Above 4K
not on this ladder
HEVC, no bitrate published

Vimeo Help Center, fetched 5 September 2026. Vimeo's own wording: the bitrates listed for each resolution are a maximum, and a video could transcode at a lower bitrate depending on the complexity of the image.

Read that qualifier carefully, because it is the most important sentence on the page. The numbers above are not what your 4K file will be delivered at. They are the most it can be delivered at. A complex shot, which is exactly the kind of shot that needs the bits, can be transcoded lower.
Two further details are worth knowing before you plan a delivery around Vimeo. Above 4K, Vimeo states that videos are delivered in HEVC and that it only generates a 5K to 8K transcode when the creator uploaded an HDR video greater than 5K resolution. That tier is also excluded on mobile devices, iOS and Android, including Vimeo’s own app and mobile browsers. And no bitrate figure is published for it, so above 4K, Vimeo joins YouTube in the category of unpublished.

The number that does not exist

YouTube
publishes no delivered bitrate at any resolution.

It is tempting to quote a YouTube 4K number, because plenty of blog posts do. We will not, because Google does not publish one, and a figure repeated in an article is not a figure from the vendor.

What YouTube publishes is a table of recommended upload bitrates: 35 to 45 Mbps for 2160p at standard frame rates, 53 to 68 Mbps at high frame rates, 8 Mbps at 1080p, and so on up to 160 Mbps for 8K. Those are instructions for your encoder, not a description of what a viewer receives. Confusing the two is the single most common error in this whole subject.
Everything Google does say about the delivery side points in one direction. YouTube always re-encodes videos to optimise their playback quality. A video is initially processed in low quality, and higher qualities such as 4K or 1080p can take hours to appear. Your video is converted to the highest resolution available to ensure successful playback on different devices and networks. Even the paid tier is described qualitatively rather than numerically: 1080p Premium is called an enhanced bitrate version of 1080p, with more information per pixel, and no figure attached.

How to state this accurately

The correct sentence is “YouTube publishes no delivered bitrate”, not “YouTube delivers N Mbps”. The absence is the finding. If you are choosing a platform for client delivery and the vendor will not tell you what the viewer receives, that is information about the platform, and it is enough to make the decision.

Why there is no ceiling here

A structural absence,
not a generous limit.

The claim on this page is not that our ceiling is set high. It is that there is no ceiling anywhere in the path, because there is no step in the path that could impose one.

1

You export

Whatever your NLE or grading suite writes: a 200 Mbps HEVC master, a 4K H.264 at 80 Mbps, an 8K deliverable. Up to 50 GB per file.

2

We store the bytes

The upload moves in 10 MB parts and is written to object storage as it arrived. There is no encode step after it lands, so nothing rewrites the file.

3

The player is handed that file

The watch page issues a short-lived signed link to the stored master and feeds it to a plain video element. There is no ladder to pick a rung from, because no renditions were ever made.

4

The viewer's decoder does the rest

What plays is decided by the browser and the hardware in front of it, not by a platform rule. That is the only gate left.

Because the encode step does not exist, there is nothing to tune, no quality setting, and no support ticket that can raise your rung. A 200 Mbps master is delivered at 200 Mbps for the same reason a file copied to a hard drive arrives byte for byte: nothing in between was asked to change it.
Vimeo
YouTube
uncompressed.io
Delivered4K bitrate
22 Mbps maximum16 Mbps on the HDR ladder
not published
your file's bitrateno ceiling below it
Above 4K
HEVC only, no bitrate publishedexcluded on mobile devices
not published
plays when the viewer'shardware decodes it
Re-encodeon upload
yes, re-encoded intoseveral formats
always re-encodes
never
Renditionladder
published, two ladders
not published
none exists
Bandwidthmetering
2 TB per month thresholdon self-serve accounts
not applicable
none, storage isthe only meter
Per-filesize limit
300 GB, 24 hours
256 GB or 12 hours,whichever is less
50 GB

Competitor figures from the pages listed in Sources, all fetched 5 September 2026. Vimeo's bitrates are published maxima. YouTube's per-file limit is an upload limit; it publishes no delivery figure to compare.

Note the one row where we are the smaller number. Vimeo accepts a 300 GB file and YouTube accepts 256 GB; our upload ceiling is 50 GB per file. If your deliverable is a single uncompressed multi-hour master above that size, that is a real reason to look elsewhere, and we would rather you read it here than discover it at 2 a.m. during a delivery.

The honest trade

With no ladder,
there is nothing softer to fall back to.

A rendition ladder is not only a ceiling. It is also a safety net, and removing the ceiling removes the net with it.

On a laddered platform, when a viewer’s throughput drops, the player quietly switches to a lower rung. The picture gets softer and the playback continues, often without the viewer noticing that anything happened. That behaviour is the entire reason adaptive streaming was invented, and for most video on the internet it is the correct design.
Here there is exactly one file, so there is nothing to switch to. When the connection cannot sustain the file’s bitrate, the player buffers. It does not degrade the image, because it has no degraded image to serve. Your client sees the frames you graded, or waits. Nothing in between.

Right for this

Client approvals, colour and VFX review, festival and jury screeners, portfolio reels where the picture is the product, and any handoff where a soft frame would send you round another revision for no reason.

Wrong for this

A video aimed at a mass consumer audience on unpredictable mobile connections. If most of your viewers arrive on cellular data and you cannot control the file they receive, a laddered platform serves them better, and you should use one.

Wrong for this too

Anything where reach and discovery are the goal. We have no recommendation engine, no search surface and no audience of our own. A platform with a ladder usually also has an algorithm, and both are reasons to be there.

The mitigation, such as it is

Export the file your viewers can actually receive. A 4K HEVC master at a bitrate their connection sustains gives them your exact bytes and no buffering. The point of no ceiling is that you choose the number, not that the number has to be enormous.

What still limits playback

The remaining gate is a decoder,
not a platform rule.

Removing the ladder does not make every file playable everywhere. It moves the decision from the platform to the machine in front of the viewer, which is worth being precise about.

Codec

The browser plays what the browser can decode. H.264, HEVC and AV1 are the codecs a browser can be expected to handle. ProRes 422, ProRes 4444 and DNxHR are hosted at full size for download rather than playback, and nothing on our side re-encodes them to make them play.

Chroma and bit depth

A 10-bit 4:2:2 file is stored and served untouched, because we never re-encode. Whether a browser decodes 10-bit 4:2:2 HEVC in a video element is not documented by any vendor, in either direction, so we will not tell you it plays and we will not tell you it fails.

Resolution

8K plays when the viewer's hardware decodes it. That caveat is not a hedge, it is the whole answer: the file is intact and delivered, and an underpowered machine will still struggle with it.

Camera RAW is the clear exception. BRAW, R3D, ARRIRAW, N-RAW, X-OCN and ProRes RAW are never streamed. They can be stored and handed to a collaborator, but the workflow that actually works for review is to finish to HEVC or ProRes and upload that.

What full bitrate costs you

We meter the storing,
not the watching.

A ceiling is not only about picture quality. It is also how a platform controls its own delivery costs, which is why bitrate limits and bandwidth limits tend to arrive together.

Vimeo publishes a bandwidth threshold of 2 TB per month on self-serve accounts, counting playback, player and thumbnail loads, downloads and live streaming, with a defined escalation when an account exceeds 2 TB twice in twelve months or 10 TB once. Our position is the other one: storage is the only meter, the terms state there are no bandwidth caps, and the pricing page lists unlimited views, uploads and viewers on every plan, including the free one. Storage is the number that differs by plan: 5 GB free on Starter with one film at a time, 100 GB on Lite, 500 GB on Pro, 1.5 TB hot plus 1 TB cold on Max, 2 TB hot plus 2 TB cold on Vault. There is no fair-use number behind the unlimited, because there is no fair-use number.

0

transcode steps

no encoder touches the file after upload

0

renditions made

there is no ladder to pick a rung from

50 GB

per file

the upload ceiling, not a bitrate ceiling

5 GB

free to start

one film at a time, no credit card

Storage is where the plans differ: 5 GB free on Starter, 100 GB on Lite at $9 a month, 500 GB on Pro at $25, 1.5 TB hot plus 1 TB cold on Max at $75, and 2 TB hot plus 2 TB cold on Vault at $250. Full details are on the pricing page. The bitrate your viewers receive is the same on all of them, because it is your file on all of them.

Questions

Frequently asked

What is the highest bitrate uncompressed.io will stream?

There is no platform ceiling. The player is handed the file you uploaded, so the delivered bitrate is your file's bitrate. The practical limits are the 50 GB per file upload ceiling, the storage on your plan, and whether the viewer's browser and hardware can decode what you sent.

Does Vimeo really cap 4K at 22 Mbps?

Vimeo's help centre publishes a delivery ladder whose 4K rung lists a video bitrate of 22 Mbps, and states in its own words that the bitrates listed for each resolution are a maximum, with a video potentially transcoding lower depending on the complexity of the image. On the HDR and above-4K HEVC ladder the 4K rung lists 16 Mbps. Above 4K, Vimeo publishes no bitrate figure at all.

What bitrate does YouTube stream at?

Google does not publish one, at any resolution. The bitrate tables on YouTube's help pages are recommended upload settings, which is a different thing: the figure you send, not the figure a viewer receives. YouTube states that it always re-encodes videos to optimise playback quality, and describes its Premium tier as an enhanced bitrate version of 1080p without giving a number. The honest statement about YouTube's delivered bitrate is that it does not exist publicly.

Will my client's laptop actually play a very high bitrate file?

That is the real question, and it has two halves. The decoder half: the browser plays what the browser can decode, so H.264, HEVC and AV1 files play where the machine supports them, while ProRes, DNxHR and camera RAW are hosted for download rather than playback. The connection half: sustained playback needs sustained throughput, because there is no lower rendition to fall back to.

Is there an adaptive quality setting for viewers on slow connections?

No, and that is the trade. A laddered platform quietly swaps in a softer version when throughput drops. With one file and no ladder, a thin connection buffers instead. For a colourist, a client approval or a portfolio piece that is the right behaviour. For a video aimed at a mass consumer audience on unpredictable mobile connections, a laddered platform serves that audience better.

Does streaming at full bitrate cost me bandwidth fees?

No. Storage is the only meter on uncompressed.io: the terms state there are no bandwidth caps, and the pricing page lists unlimited views, uploads and viewers on every plan including the free one. For comparison, Vimeo publishes a 2 TB per month bandwidth threshold on self-serve accounts, with a defined escalation path when an account exceeds it.

Can I upload ProRes, DNxHR or camera RAW?

ProRes 422, ProRes 4444 and DNxHR are hosted at full size for your client to download; nothing re-encodes them. Camera RAW formats such as BRAW, R3D, ARRIRAW, N-RAW and X-OCN are never streamed, and the honest workflow there is to finish to HEVC or ProRes and upload that alongside the RAW you are storing.

Host the export, not a copy of it

No transcode, no rendition ladder, no ceiling below your own file. Storage is the only meter, on every plan including the free one.

See plans and storage

Sources

  1. 1.Vimeo Help Center, delivery bitrates by rendition (standard H.264 ladder and HDR / above-4K HEVC ladder) (fetched 5 September 2026)
  2. 2.Vimeo Help Center, above-4K playback and HEVC delivery (fetched 5 September 2026)
  3. 3.Vimeo Help Center, recommended upload settings (fetched 5 September 2026)
  4. 4.Vimeo Help Center, what happens during transcoding (fetched 5 September 2026)
  5. 5.Vimeo Help Center, bandwidth threshold and escalation (fetched 5 September 2026)
  6. 6.Vimeo pricing page and plan FAQ (per-file limits, bandwidth limit, 4K marketing claim) (fetched 5 September 2026)
  7. 7.YouTube Help, recommended upload encoding settings (fetched 5 September 2026)
  8. 8.YouTube Help, video encoding and re-encoding on upload (fetched 5 September 2026)
  9. 9.YouTube Help, upload videos and resolution conversion (fetched 5 September 2026)
  10. 10.YouTube Help, video processing and available qualities (fetched 5 September 2026)
  11. 11.YouTube Help, upload file size and length limits (fetched 5 September 2026)
  12. 12.YouTube Help, 1080p Premium enhanced bitrate (fetched 5 September 2026)
  13. 13.uncompressed.io pricing, plans, storage and unmetered viewing (fetched 5 September 2026)
  14. 14.uncompressed.io Terms of Service, storage as the only meter (fetched 5 September 2026)

Keep reading

Video hosting that does not compress your fileStreaming a 200 Mbps file in a browser8K video hostingVideo bitrate, explained
Video Hosting With No Bitrate Limit: Published Ceilings Compared