Export settings, answered
What bitrate should I export 4K video at?
The published numbers, and where they survive the trip.
There are two answers, and which one applies depends entirely on what happens to the file after you press export. If a platform is going to re-encode it, the published upload recommendations are the answer and anything above them is paid for and thrown away. If the file is going somewhere that streams it untouched, the bitrate you choose is the bitrate your viewer receives, and the only ceiling is the size you want to store.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
By uncompressed.io · Updated September 2026
The short answer
Start at 35 to 45 Mbps,
then ask who re-encodes it.
The published recommendations are narrow and they agree on the shape of the problem. Where they stop being useful is the moment the file lands somewhere that does not rebuild it, because then the number you exported is the number your viewer receives.
35 to 45
Mbps, 4K SDR
YouTube's recommended upload bitrate for 2160p at 24, 25 or 30 fps.
53 to 68
Mbps, high frame rate
The same SDR table at 48, 50 or 60 fps.
44 to 56
Mbps, 4K HDR
YouTube's separate HDR table at standard frame rate.
1 to 1
Bitrate in, bitrate out
Here the player streams the exact bytes uploaded, so a 200 Mbps master streams at 200 Mbps.
Two different questions hide inside one search. The first is what number gives a platform’s encoder enough to work with. The second is what number gives your viewer the best picture. On YouTube, on Vimeo, on any host that builds its own renditions, those questions have different answers, and only the first one is under your control.
The recommendations below are upload targets published by platforms that re-encode. They are not delivery bitrates, and they are not quality ceilings for a file you keep. Treat them as the brief you are writing for somebody else’s encoder.
What is actually published
YouTube’s recommended upload bitrates,
by resolution and frame rate.
This is the most detailed first-party table in public. It is published alongside a codec recommendation of H.264 High Profile with 4:2:0 chroma, in an MP4 container with the moov atom at the front of the file, so the numbers are H.264 numbers.
YouTube Help, recommended upload encoding settings, fetched 11 September 2026. The same page recommends AAC-LC or Opus audio at 48 kHz, at 128 kbps for mono, 384 kbps for stereo and 512 kbps for 5.1. Vimeo publishes its own recommended range for a 4K upload and lists H.264, Apple ProRes 422 HQ and HEVC as accepted upload codecs; the resolution-by-resolution figures and the delivery ceilings on that platform are covered on the page linked below.
A second platform publishes a comparable table with a wider 4K range and a different codec list. Rather than restate it here, the numbers and the playback ceilings that go with them are on the Vimeo export bitrate page. The point both tables make is the same one: the platform is telling you what its encoder wants to be fed, not what your audience will receive.
By codec and by destination
Pick the codec first, from
where the file has to open.
Bitrate is the last decision, not the first. A number that is generous in one codec is wasteful in another, and a codec that looks efficient on paper is useless if the person opening the link cannot decode it.
Browser support quoted from MDN's Web video codec guide, fetched 11 September 2026. Chroma constraint from Microsoft Learn, H.265 / HEVC Video Decoder, fetched 11 September 2026. Codec acceptance for uploads from each platform's own guidelines. No vendor documents 10-bit 4:2:2 HEVC decode in a video element in either direction, so this table says nothing about it.
Why the number survives here
A 200 Mbps master
streams at 200 Mbps.
Not because of a premium tier or a quality setting. Because there is no transcode step in the path. The player serves the exact bytes you uploaded, so the bitrate you set in the export dialog is the bitrate leaving the server.
YouTube recommended 4K SDR upload, top of range
YouTube recommended 4K HDR upload, top of range
A 100 Mbps export, streamed here
A 200 Mbps export, streamed here
An 8K export at 240 Mbps, streamed here
The first two bars are upload recommendations published by YouTube on 11 September 2026, not delivered bitrates. The lower three are files uploaded here: the player streams the exact bytes uploaded, with no transcode anywhere, so the export figure and the delivery figure are the same number. Browser playback covers H.264, HEVC and AV1. The 8K bar is drawn at the edge of the scale; 8K plays when the viewer's hardware decodes it.
This is the whole difference between the two answers at the top of the page. A platform rebuilds your upload into a ladder of renditions sized for connections it has to serve at scale, so headroom above its recommendation is spent on upload time and storage and then discarded. Here nothing is rebuilt, which means the headroom is the deliverable.
Bandwidth is not metered on any plan, and views, uploads and viewers are unlimited, including on the free tier. A 200 Mbps film costs the same whether one person opens it or two hundred do. What you pay for is storage, which is why the export bitrate is a storage question here rather than a delivery question.
Name the recipient
A platform that re-encodes, a client on an unknown laptop, or a broadcaster who wants a mastering file. Each one has a different right answer and they are not close to each other.
Choose the codec
H.264 for the widest reach, HEVC or AV1 when you know the device, ProRes when the file is a handoff rather than something to watch in a browser.
Set the bitrate
The published range for a platform upload. For a link you control, 100 to 200 Mbps is a normal finished-film choice, and the ceiling is storage rather than playback.
Check the size
Multiply bitrate by duration before you commit. The table below does it for the four numbers people actually use.
What the number costs
Above the platform ranges, bitrates
are a storage decision.
Video only, bitrate times duration, rounded, in decimal gigabytes. Audio adds a few hundred kilobits per second on top: YouTube recommends 128 kbps for mono, 384 kbps for stereo and 512 kbps for 5.1.
Starter is free with 5 GB of hot storage, which holds a ten-minute 4K film exported at 45 Mbps with room left over, or a shorter one at 200 Mbps. Lite is $9 a month for 100 GB and Pro is $25 a month for 500 GB. Past a plan, hot storage is $40 per TB a month and cold archive storage is $20 per TB a month.
Working backwards from that table is usually the faster way to decide. A ninety-minute feature at 200 Mbps is 135 GB of hot storage, which is a real line on a bill; the same feature at 100 Mbps is 67.5 GB and, on a browser-decodable codec, still arrives at more than twice any published platform recommendation for 4K.
The one number that is not yours to choose
Beyond the slider
Four settings that change the result
more than the bitrate does.
Frame rate
YouTube's high frame rate column is roughly half again as large as its standard column at every resolution: 53 to 68 Mbps at 4K against 35 to 45. Doubling the frames without raising the budget halves the bits each frame receives.
HDR
YouTube publishes a separate and higher table for HDR uploads, 44 to 56 Mbps at 4K standard frame rate against 35 to 45 for SDR. Exporting HDR at the SDR number starves exactly the gradients HDR exists to show.
Chroma and bit depth
YouTube asks for 4:2:0 on uploads. For browser playback of 10-bit 4:2:2, behaviour is not documented by any vendor: MDN states support at the codec level only, Android's format list does not mention chroma, and Microsoft's HEVC decoder specification documents 4:2:0 chroma. We never re-encode, so such a file is stored and served untouched, but the decode end is undocumented.
Container and audio
YouTube asks for MP4 with the moov atom at the front of the file, described on its page as Fast Start, with AAC-LC or Opus audio at 48 kHz. A correct bitrate in a file that will not start streaming promptly is still a bad delivery.
If the export is going to a client for approval rather than to a platform, the decisions shift again, toward what opens reliably on an unknown machine and what the reviewer needs to see. Those are covered in export settings for client review, and the mechanics of what a bitrate controls are in video bitrate explained. For why the number holds all the way to the viewer here, see video hosting that does not compress.
Questions
Frequently asked
What bitrate should I export 4K video at?
For an upload to a platform that re-encodes, use the platform's own recommendation. YouTube publishes 35 to 45 Mbps for 2160p SDR at 24, 25 or 30 fps, and 53 to 68 Mbps at 48, 50 or 60 fps. Its HDR table is higher: 44 to 56 Mbps at standard frame rate and 66 to 85 Mbps at high frame rate. For a link you control, the number is a storage decision rather than a delivery ceiling, and 100 to 200 Mbps is a normal choice for a finished 4K film.
Is there any point exporting 4K above the recommended range?
Only if nothing re-encodes it. A platform rebuilds every upload into its own set of renditions, so a higher upload bitrate buys a cleaner source for that encoder and nothing at the viewer's end. On a host that streams the exact bytes uploaded, the opposite is true: a 200 Mbps master streams at 200 Mbps, because there is no transcode step anywhere in the path to lower it.
H.264 or HEVC for a 4K export?
Choose by where the file has to open, not by the bitrate. MDN records H.264 support in all versions of Chrome, Edge, Firefox, Opera and Safari, with Firefox depending on codecs the operating system provides. HEVC support is stated per platform: Safari on macOS High Sierra or later, Chrome and Edge on devices with hardware support, Firefox from version 134 on Windows and later versions elsewhere. H.264 is the safe choice when you do not know the recipient's machine.
Should I export 10-bit 4:2:2 for a browser review link?
Browser behaviour for that combination is not documented. MDN states browser support at the codec level and gives no statement that differentiates by chroma subsampling or bit depth, Android's supported-formats page does not mention chroma at all, and the one primary decoder specification among the three, Microsoft's Media Foundation HEVC decoder, documents 4:2:0 chroma only. Our side is safe because we never re-encode, so a 10-bit 4:2:2 file is stored and served untouched. For a link a client opens in a browser, send a 4:2:0 export and keep the 4:2:2 file as the download.
What does a 4K export actually cost in storage?
Bitrate times duration. Ten minutes at 45 Mbps is about 3.4 GB, at 100 Mbps about 7.5 GB, and at 200 Mbps about 15 GB. Ninety minutes at 200 Mbps is about 135 GB. Starter is free with 5 GB of hot storage, Lite is $9 a month for 100 GB, and Pro is $25 a month for 500 GB. Storage past a plan is $40 per TB hot a month.
What bitrate for 8K?
YouTube publishes 80 to 160 Mbps for an 8K SDR upload at standard frame rate and 120 to 240 Mbps at high frame rate, rising to 100 to 200 and 150 to 300 Mbps on its HDR table. Here an 8K file plays when the viewer's hardware decodes it, which is a property of their machine rather than of the bitrate you chose.
Export the number you meant, and let it arrive
uncompressed.io streams the exact bytes you upload. No ladder, no re-encode, no bandwidth meter, and no per-view charge. Starter is free with 5 GB of hot storage.
Sources
- 1.YouTube Help: recommended upload encoding settings, SDR and HDR bitrate tables, container and audio recommendations (fetched 11 September 2026)
- 2.Vimeo Help Center: video and audio compression guidelines, accepted upload codecs (fetched 11 September 2026)
- 3.MDN: Web video codec guide, browser support for H.264, HEVC and AV1 (fetched 11 September 2026)
- 4.Microsoft Learn: H.265 / HEVC Video Decoder (Media Foundation), format constraints table (fetched 11 September 2026)
- 5.Android Developers: supported media formats (fetched 11 September 2026)
- 6.uncompressed.io pricing: plans, included storage and storage blocks
