Export settings, answered
Vimeo publishes a recommended bitrate for every resolution, from 2 Mbps at SD to 80 Mbps at 8K, along with the codec, profile, frame rate, CRF and audio settings it wants. Those numbers are the answer for almost every upload, and this page starts with them. It then covers the settings that are not bitrate, the rendition rule that can quietly cost you the 4K version of your film, and what Vimeo says it delivers at the far end.
No credit card required. Cancel any time.
Updated September 2026
The short answer
Vimeo publishes a recommended upload bitrate for every resolution it accepts. Hit the middle of the band for your export and you are done. The right-hand column is arithmetic, not Vimeo’s figure: what ten minutes of picture weighs at each rate, so you can sanity-check a render before you start it.
Bitrates as published in Vimeo's video and audio compression guidelines, fetched 4 September 2026. File sizes are plain arithmetic from those figures, video only, before audio and container overhead: bitrate in megabits per second times 600 seconds, divided by eight.
The bitrate is only half of the answer. The rest of Vimeo’s guideline is a short list of settings that matter as much, and one of them, the H.264 profile, is the item most export presets get wrong by default.
Codec, profile, CRF, frame rate and audio from Vimeo's compression guidelines. The per-file size and duration limit is quoted from Vimeo's pricing page: a size limit of 300 GB and a duration limit of 24 hours per video file, regardless of plan. Both fetched 4 September 2026.
The settings behind the numbers
A fixed bitrate has to be sized for the hardest shot in the timeline. Set 40 Mbps for a 4K piece and the locked-off interview wastes it while the handheld night exterior with real grain runs out of bits in the same second. CRF sets a quality level and lets the bitrate rise and fall to hold it. Grain is the reason this matters: it is high-frequency detail with no pattern to predict, so it is the first thing a starved encoder turns into smeared blocks. Vimeo's guideline is CRF 18 or below.
Vimeo names High Profile explicitly. High Profile allows the 8 by 8 transform and custom quantization matrices that Main does not, so at the same bitrate it has more tools to hold fine detail. Plenty of export presets, especially ones built for older devices, still default to Main. It is a one-click change in every encoder and it is free.
Vimeo lists eight accepted rates and asks for all of them constant. Screen recorders, phone cameras and some game-capture tools write variable frame rate, where frame durations change through the file. There is no single frame duration for a downstream encoder to hold to. Conform the footage to a constant rate in your NLE before export rather than hoping the platform guesses right.
The limit that catches ProRes masters
The rule most articles miss
This is the one that quietly costs people the 4K version of their film. Vimeo does not build a rendition because you exported something you think of as 4K. It builds each rendition only if the uploaded file clears a dimension threshold, and the rule is an OR: the larger dimension qualifies, or the smaller one does.
Thresholds and maximum bitrates as published in Vimeo's guidelines for determining playback resolution, fetched 4 September 2026. Bitrates shown are from the H.264 ladder and are maximums; Vimeo states that a video could transcode at a lower bitrate depending on the complexity of the image.
Run your own export size against those two columns before you upload. Standard UHD at 3840 by 2160 clears the 4K gate twice over and needs no thought. The awkward cases are the ones that are only unusual by a few hundred pixels.
A 2.39:1 crop of UHD delivered at 3840 by 1608 is well under the 2052px smaller-dimension threshold, but its larger dimension is 3840, so the OR saves it and the 4K rendition is built. A square 2160 by 2160 social cut fails the larger-dimension test at 2160, and clears the smaller-dimension test at 2160, so it also gets a 4K rendition. A DCI 2K scope master at 2048 by 858 clears the 1080p60 gate on its larger dimension and misses both the 2K gate and the 4K gate on both axes, so the best rendition it will ever have is 1080p, no matter how high the bitrate on the file you uploaded. Above 4K there is a further condition: Vimeo states it will only generate a 5K to 8K transcode if the creator uploaded an HDR video greater than 5K resolution, that those renditions are delivered in HEVC, and that mobile devices, iOS and Android, including the Vimeo app and mobile browsers, cannot play them.
The practical rule is simple. If a resolution matters to you, make sure the export clears that rendition’s threshold on at least one axis. Cropping for aspect ratio is where people lose it, because the crop takes pixels off the axis they were counting on.
The other end of the pipe
Everything above is upload advice, and it stands. This part is the context that changes how much bitrate is worth chasing. Vimeo states that during transcoding, your video file is re-encoded into several formats that will be available to view on Vimeo. It also publishes the maximum bitrate of each of those formats. Both numbers come from Vimeo’s own help center, not from a measurement here.
All figures published by Vimeo in its guidelines for determining playback resolution, fetched 4 September 2026. Vimeo's wording: the bitrates listed for each resolution are a maximum, which means your video could transcode at a lower bitrate depending on the complexity of the image. Read every number here as up to.
Your 4K export, top of the range Vimeo recommends
Vimeo's published maximum 4K delivery, H.264 ladder
Vimeo's published maximum 4K delivery, HDR ladder
The same 60 Mbps file on uncompressed.io
The two Vimeo bars are Vimeo's own published maximums, not a measurement by this site, and real output can be lower. The uncompressed.io bar is the file itself: there is no ladder here, so the delivered bitrate is whatever you exported. Playback of any high-bitrate file depends on the viewer's hardware decoder.
Put the two halves together and the arithmetic is plain. Vimeo asks for 30 to 60 Mbps at 4K and publishes a delivery ceiling of up to 22 Mbps. Everything between those two numbers is headroom for Vimeo’s encoder, not picture the viewer receives. That headroom is real and it is worth giving: a clean, lightly compressed source produces a better 22 Mbps rendition than a source that was already squeezed once. But past the top of Vimeo’s recommended band, more bitrate in your export buys a better input to the re-encode and nothing at all at the far end.
The audio tells the same story in one line. Vimeo asks you to upload AAC-LC at 320 kb/s CBR, and publishes a delivered maximum of 256 Kbps from 540p through 4K. The upload recommendation is higher than the delivery ceiling on both tracks, picture and sound, by Vimeo’s own two pages.
When to stop reading
This deserves saying plainly, because most pages that reach this point turn into a pitch. For the large majority of uploads, follow the table at the top of this page and nothing more is needed.
A corporate piece, a wedding film, a music video, a case study, a showreel that lives on a website: at 1080p or 4K, watched on a laptop or a phone, on a connection that is not guaranteed, a 4K rendition at up to 22 Mbps delivered through an adaptive ladder is a good viewing experience. The ladder is not a defect. It is the reason a viewer on a weak connection sees a smaller version instead of a spinner, and it is why Vimeo can serve your film to a stranger on hotel wifi without you thinking about it.
Vimeo also has things with no equivalent here: a player you can brand and put calls to action inside, hosted live events, OTT and distribution products, marketing tooling, and a team account structure. If any of that is why you are on Vimeo, this page is only telling you which export settings to use, and the answer is the one at the top.
The one case where it is not enough
There is one job the ceiling genuinely breaks: showing a client, a colorist or a festival programmer what the grade actually looks like. If the point of the link is the picture itself, a delivered rendition capped at 22 Mbps, made from a 60 Mbps master, is not the thing you made.
The escape hatch is a host with no ladder, which streams the exported file itself. That is what uncompressed.io does: the player streams the exact bytes you upload, with no transcode anywhere, no adaptive ladder and no re-encode of video or audio. A 60 Mbps export plays at 60 Mbps. A 150 Mbps export plays at 150 Mbps. Uploads are MP4 or MOV in H.264, HEVC or AV1, up to 50 GB per file, and no bandwidth is metered on any plan, including the free one. Storage is the only meter.
The honest trade runs the other way too. With no ladder there is no smaller rendition to fall back on, so a viewer on a slow connection buffers instead of quietly dropping to a mushy version. That is the right behaviour for a grade review and the wrong behaviour for a public marketing page, and playback of a high-bitrate file still depends on the viewer’s hardware decoder. ProRes 422, ProRes 4444 and DNxHR are hosted for client download rather than streamed, and camera RAW is not uploaded raw: the honest workflow is to finish to HEVC or ProRes, then upload.
Most people reading this question do not need any of that. They need the top table, and a preset saved with High Profile ticked.
Questions
Vimeo's guidelines ask for 10 to 20 Mbps at 1080p, in H.264 High Profile, ProRes 422 HQ or HEVC, at a constant frame rate, with audio in AAC-LC at 320 kb/s CBR and 48 kHz. If your encoder offers a constant rate factor, Vimeo recommends CRF 18 or below instead of a fixed target, which lets a busy shot spend more bits and a static one spend fewer.
It buys a cleaner source for Vimeo's encoder, and nothing at the viewer's end. Vimeo re-encodes every upload into several formats, and its own playback guidelines put the maximum delivered 4K bitrate at 22 Mbps on the H.264 ladder and 16 Mbps on the HDR ladder. Above the 30 to 60 Mbps Vimeo recommends, you are paying in upload time and storage for headroom the delivery ladder will not pass on.
Use CRF where the encoder offers it. Vimeo's own guideline is CRF 18 or below. A fixed target has to be sized for the worst shot in the timeline, so a grainy night exterior and a locked-off interview get the same budget; CRF sets a quality level and lets the bitrate move to hold it. That matters most on graded footage with real grain, which is exactly the material a fixed target starves.
Vimeo generates renditions by pixel dimensions, not by what you call the export. The 4K rendition needs a larger dimension of at least 3648px or a smaller dimension of at least 2052px. A DCI 2K scope master at 2048 by 858 misses both the 2K and the 4K gate on both axes, so no 2K or 4K version is ever built, whatever bitrate you exported it at.
It gives the encoder a better source, which is why Vimeo lists it as an accepted upload codec alongside H.264 High Profile and HEVC. It does not skip the re-encode: Vimeo states that every uploaded file is re-encoded into several formats. Watch the ceiling that applies to every plan, a size limit of 300 GB and a duration limit of 24 hours per video file.
AAC-LC, 320 kb/s CBR, at a 48 kHz sample rate. Note that the same help center publishes a maximum delivered audio bitrate of 256 Kbps for renditions from 540p through 4K, and 265 Kbps on the HDR 2K and 4K renditions, with all conversions at 48 kHz. You upload 320 and Vimeo delivers up to 256, so the audio is re-encoded downward by Vimeo's own two pages.
Vimeo asks for a constant frame rate at 23.98, 24, 25, 29.97, 30, 50, 59.94 or 60 fps. A variable-frame-rate file, which is what screen recorders and some phone cameras produce, has no single frame duration for the encoder to hold to, so the safe move is to conform it to a constant rate before export rather than to hand the platform a moving target.
uncompressed.io streams the exact file you upload, at whatever bitrate you exported it at. No ladder, no re-encode, no bandwidth meter. Starter is free with 5 GB.