Vimeo vs YouTube for a filmmaker's portfolio.
One of them publishes its playback ceiling. The other publishes nothing.

Vimeo’s equivalent guidance is a band rather than a grid: 30 to 60 Mbps as the recommended upload bitrate for 4K, in its video and audio compression guidelines. Its upgrade page adds that videos can stream up to 4K Ultra HD, which is a statement about resolution and not about bytes per second.

Now hold that number next to the next section, because it is the clearest single fact on this page. Vimeo asks you to upload 4K at 30 to 60 Mbps, and its playback guidelines put the maximum it will ever serve at 22 Mbps in standard H.264. The gap between what a platform asks you to send and what it will ever send back out is the whole story of hosted video, and Vimeo is the one platform here honest enough to let you measure it.

YouTube is explicit about the transformation while staying silent about its size. Its help center states that YouTube always re-encodes videos to optimize their playback quality. That sentence tells you the file the viewer streams is not the file you exported, without giving you any way to know how far apart the two are.

Vimeo publishes no equivalent sentence about re-encoding, and this page will not put words in its mouth. It does publish conversion and playback specs, with the maximums above, and those maximums are the useful thing. A 4K master exported at 30 to 60 Mbps, as Vimeo itself recommends, reaches a viewer at a maximum of 22 Mbps, possibly less. That is not a criticism of Vimeo’s honesty. It is a description of what a streaming ladder is for, and the mechanics of why the difference shows up on screen are in the guide on why uploads look worse.

The practical rule for either platform is the same one every editor learns once: the upload is not the backup. Keep your masters on disks you own, and treat a hosting account as distribution. The difference is that on one of the three the distribution copy and the master happen to be the same bytes.

YouTube has reach and Vimeo does not. There is no hedge to add. If discovery matters to your business, if you want a search result and a suggested-video slot and a subscriber count, YouTube is the platform and no comparison table changes that. Its visibility settings are worth understanding before you use it as a private portfolio, though: unlisted videos can be seen and shared by anyone with the link, and they stay out of YouTube’s search results unless someone adds the video to a public playlist.

The price of that reach is written into the Terms of Service. You grant YouTube the right to monetize your content on the service, and that monetization may include displaying ads on or within content or charging users a fee for access. For a music video chasing views, that is the deal and it is a fair one. For a reel a commissioner opens from your email signature, an ad in front of your first frame is a cost with no upside.

Vimeo is unambiguous in the other direction and deserves the credit: it states it never puts ads before, during, or after your videos, even on its Free plan. That is a clear win for Vimeo over YouTube on this axis, and it is most of why filmmakers have kept Vimeo tabs open for fifteen years.

For most filmmakers most of the time, neither cap is the thing that hurts. Vimeo’s own 99 percent figure says as much. The cap becomes real in exactly two situations: a film that gets shared widely inside one month, and a delivery-heavy studio sending large masters to many people. If you are neither, do not choose a host on the bandwidth line.

One consequence is easy to miss. On a platform that re-encodes, exporting at a very high bitrate is close to pointless past the recommendation, because you are paying upload time for detail the encoder is about to discard. On a platform that does not re-encode, the export bitrate is the only decision that matters, because it survives to the viewer unchanged. The two workflows look identical in the export dialog and mean opposite things. The arithmetic that turns a bitrate into a file size, and a file size into a plan, is in the bitrate guide.

Both platforms in this comparison were built to serve a stream, not to store a master. That is a legitimate design, and it explains everything above: the upload recommendations exist to feed an encoder, the playback maximums exist because a ladder has to end somewhere, and the download-back rules follow from a copy that was never meant to be the copy of record.

The third column answers a different question. The player streams the exact bytes that were uploaded, so the published upload figure and the delivered figure are the same number. That is why there is no delivery bitrate on this site to publish: a 4K export at 150 Mbps reaches the viewer at 150 Mbps, next to a published maximum of 22 Mbps for 4K H.264 on Vimeo and no published figure at all on YouTube. Browser-decodable codecs stream, meaning H.264, HEVC and AV1. ProRes 422, ProRes 4444 and DNxHR are hosted for client download rather than streamed. 8K plays when the viewer’s hardware decodes it, which is a real caveat and not a footnote. Storage is the only meter, from 1 GB free up to 2 TB hot plus 2 TB cold on Vault, and no bandwidth is metered on any plan.

If you are already on Vimeo and want to move the library rather than re-upload it, the guide to leaving Vimeo covers what transfers, what Vimeo will and will not hand over, and which plans expose originals through the API.