Bit depth is where a grade lives
A grade is built out of precision: 1,024 levels per channel instead of 256, spent mostly on the flat areas where your eye finds steps. Every streaming platform is built around a delivery ceiling far below a graded master. Here is what the platforms publish, what browsers document, and what it takes to have the file arrive as you exported it.
No credit card required. Cancel any time.
Updated September 2026
What 10-bit actually buys
Bit depth is how many distinct values a single colour channel is allowed to hold. Eight bits gives 256 of them. Ten bits gives 1,024. That is the whole difference, and it decides whether a sky falls off smoothly or arrives in visible steps.
Banding is a quantisation artifact. Encoding a picture means rounding every sample to one of the values the format allows, and the visible error is the size of the gap you rounded across. In a busy frame nobody sees it: detail, grain and motion scatter the error into noise your eye reads as texture. In a flat frame there is nothing to hide behind. A dusk sky, a white cyclorama, a slow fade to black, a skin tone rolling into shadow: these are exactly the regions where neighbouring pixels differ by one or two code values, and where a coarse rounding step turns a gradual ramp into a staircase.
A grade makes this worse before it makes it better. Lifting shadows, pulling contrast, adding a colour cast: every one of those operations stretches a narrow range of source values across a wider output range. If the source held 256 levels, the stretch multiplies the gaps between them. If it held 1,024, there is four times the material to stretch, and the result still lands on a fine enough grid to look continuous. This is the reason colourists insist on 10-bit acquisition, and the reason a 10-bit master and an 8-bit master of the same shot are not interchangeable deliverables.
Bit depth also feeds the encoder. Precision in a flat area is what lets a codec allocate bits sensibly there instead of quantising the whole region to a handful of values and hoping nobody notices. Fewer code values plus coarse quantisation is the recipe for banding, and it is the combination the rest of this page is about, because both halves of it are decided by the platform you upload to.
10-bit master
1,024 shades per channel. The night sky falls off smoothly, the way the camera saw it.
Crushed to 8-bit, then starved
256 shades, and aggressive quantization spends even fewer on dark areas. The falloff turns into visible bands.
Illustration rendered by your browser, exaggerated for visibility. The mechanism is real: fewer code values plus coarse quantization equals banding.
What the platforms publish
It is worth separating what a platform states from what people assume about it. Vimeo publishes an unusual amount about its delivery renditions. YouTube publishes almost nothing about delivery and a great deal about upload. Both state plainly that they re-encode.

Vimeo and YouTube figures are quoted from their own help centres, fetched 4 September 2026 and listed in the sources below. Vimeo's delivery bitrates are the maximums it publishes for each rendition, not measurements. YouTube publishes recommended upload settings and upload ceilings; it publishes no delivery bitrate and no delivery chroma subsampling at any resolution, so neither is stated here.
Read the table for what it does not say as much as what it does. Nobody here is accusing either platform of throwing away your grade on purpose, and neither of them publishes the chroma subsampling of what it sends to a viewer, so this page will not guess at it. What both of them do state, in their own words, is that the file a viewer receives is not the file you sent. It was re-encoded, into more than one format, and on Vimeo the largest of those formats has a published ceiling of up to 22 Mbps in 4K.
That ceiling is the number worth sitting with. It is not a criticism of Vimeo, whose figure is in line with what the streaming industry as a whole is built around. It is a statement about what a delivery rendition is for. Which brings us to the best available yardstick.
The industry yardstick
The HLS authoring specification is Apple telling every streaming engineer what a good ladder looks like, and it is the document most professional ladders are built against. It publishes its own example bitrates, which makes it a fair external measure of what “streaming quality” means when nobody is selling you anything.
Apple HLS authoring spec, 1920x1080 HEVC SDR, top rung
Apple HLS authoring spec, 2560x1440 HEVC SDR
Apple HLS authoring spec, 3840x2160 HEVC SDR, top rung
Apple HLS authoring spec, 3840x2160 HEVC HDR, top rung
Vimeo published maximum, 4K H.264 rendition
A graded 4K master exported at 150 Mbps, streamed here as exported
Apple figures are the example HEVC ladder in its HLS authoring specification for Apple devices, in kbps, converted to Mbps; the specification notes that at 24 fps these should come down about 20 percent. The Vimeo figure is the published maximum for its 4K H.264 rendition, which Vimeo states can transcode lower on complex images. The bottom bar is an export choice, not a platform figure: a 150 Mbps master streams here at 150 Mbps because nothing re-encodes it.
Put a graded master beside that ladder and the gap is not marginal. A 4K delivery export at 100 to 200 Mbps is roughly six to twelve times Apple’s top 4K HEVC rung. This is not a flaw in the specification. A ladder exists to hold a picture together across a hotel wifi and a phone on cellular, and 16,800 kbps is a considered answer to that problem. It is simply a different problem from showing a colourist’s work to the person who paid for it.
The same specification carries a second detail that matters more to this page than the bitrates do. It requires HEVC streams to be Main 10 Profile, Level 4.0 Main Tier for maximum compatibility. Main 10 is the 10-bit profile. The document the industry authors its ladders against does not offer 8-bit HEVC as an option at all, which is the strongest official signal available that 10-bit is the professional streaming baseline rather than a specialist request. If you have been treating a 10-bit deliverable as something to apologise for, stop.
What browsers document about 10-bit
Decoder documentation is thinner than anyone would like, and the honest approach is to quote what exists and say nothing where nothing exists. The anchor document is Microsoft’s specification for the Windows HEVC decoder, because it is the one primary source that names profiles and chroma formats outright.
Microsoft lists the profiles it supports as Main, Main Still Picture and Main10, and the chroma formats as 4:2:0 only. Output subtypes are NV12 and P010, the 8-bit and 10-bit pairings. The specification states outright that 10-bit input must declare the Main10 profile. Maximum dimensions are 4096x2304, and hardware acceleration is guaranteed only up to 1920x1088, above which hardware is used where the machine supports it and software decoding otherwise.
Microsoft's own codec table lists HEVC as “Conditionally supported - Requires a valid HEVC Video Extension and a working HEVC decoder path”. Edge reaches HEVC through the Windows decoder above, so the profile and chroma rules in that specification are the rules that apply.
HEVC hardware decoding shipped in Chrome 107 and is enabled by default. Chrome's own wording states the condition: support for decoding HEVC “on platforms where hardware (e.g., GPU, media accelerator, etc) is available (Android 5.0+, macOS 11+, Windows 8+, ChromeOS)”. Hardware availability is the stated requirement.
The Firefox 134.0 release notes are brief and specific: “Hardware-accelerated playback of HEVC video content is now supported on Windows.” On Windows that path runs through the same Microsoft decoder.
WebKit's Safari 18.4 notes name H264, HEVC and AV1 among video tracks. Apple has no single page stating that Safari supports HEVC for web playback, and its own guidance on delivering video content for Safari names H.264 and HLS. The strongest Apple statement about 10-bit HEVC is the HLS specification's Main 10 requirement.
Bit depth and chroma subsampling are named in exactly one of these documents, Microsoft's, and it names 4:2:0. Apple's Mac technical specifications list hardware-accelerated H.264, HEVC and ProRes without naming a chroma format or a bit depth anywhere. Where a vendor is silent, this page stays silent.
The 4:2:2 question, handled properly
10-bit 4:2:2 HEVC is a different case from 10-bit Main10 4:2:0, and it deserves its own treatment rather than a confident sentence here. No browser vendor documents 10-bit 4:2:2 HEVC decoding in a video element. Microsoft’s decoder specification covers 4:2:0 chroma only. Apple documents HEVC 10-bit 4:2:2 as an encoding capability of Compressor on Apple silicon, which is a statement about making files, not about playing them in a browser. So the accurate word is “not documented”, in either direction.
Our side of it is not ambiguous, because we do not re-encode: a 10-bit 4:2:2 file is stored and served here exactly as you uploaded it, and what a given viewer’s machine does with it is that machine’s decoder’s business. The sibling guide walks through every primary document line by line, including the ones people routinely misread as support statements.
Our answer
There is no clever compression story here, because there is no compression step. The file is stored as uploaded and streamed as stored. A 10-bit Main10 HEVC export arrives at your viewer as encoded, at the bitrate you gave it, with the bit depth and the chroma format you exported.
0
re-encodes
video and audio both arrive as exported
50 GB
per file
MP4 or MOV, H.264, HEVC or AV1
1
meter
storage. Bandwidth is not metered on any plan
0
adaptive renditions
one file, no softer version to swap in
This is the configuration with documented decoder coverage, and the profile Apple's HLS specification requires of HEVC. For 4K, 100 to 200 Mbps keeps the flat areas smooth with room to spare. Put it in an MP4 or a MOV.
Up to 50 GB per file. Uploads are resumable, survive navigation away from the page, and heal through network hiccups, so a large master does not need a perfect connection, only a patient one.
No transcode, no ladder, no rendition selection. The viewer's player pulls the file you uploaded. Views, viewers and uploads are not metered on any plan, including the free one; storage is the only meter.
Playback depends on the viewer's hardware decoder, so if a specific client on a specific machine has to see this grade, send them the link before the deadline rather than after it. That is the only reliable test, on any platform.
The caveats, stated up front
Three of them, and none is negotiable. Playback depends on the viewer’s hardware decoder: we can guarantee the bytes leaving our side, never the silicon on theirs. The practical band that browser hardware decoders handle today is roughly 300 to 400 Mbps, which is an engineering observation about current machines rather than a specification we publish. And there is no adaptive ladder, so a viewer on a weak connection buffers instead of being quietly served something softer.
That last one is a deliberate trade, and it is the whole argument of the page. A ladder protects the viewing experience by degrading the picture without telling anyone. For a graded master shown to the person who commissioned the grade, that is the wrong default.
When you should not use this
A film aimed at a general audience on mixed devices, over connections you will never see, is exactly the problem adaptive streaming was invented to solve. Send that to YouTube or Vimeo. YouTube costs nothing, reaches an audience no other platform can, and carries search, recommendation and monetisation that have no equivalent here. Vimeo’s player, marketing tools, privacy controls and OTT products are a real product line, and this page is not going to pretend otherwise. 8-bit H.264 remains the format with the broadest playback coverage anywhere, and if a stranger on an unknown device has to see your film, that is the format to hand them.
The case for hosting a 10-bit master untouched is narrower and specific: the grade review, the client approval, the colourist’s reel, the festival screener, the delivery of a finished film to the person who paid for it. Those viewers are known, their machines are known or knowable, and the whole point of the file is the precision a delivery ladder is designed to spend. Use the right tool on each side of that line, and understand what bitrate is doing before you decide which side a given job sits on.
Questions
No. The player streams the exact bytes you uploaded. There is no transcode of video or audio anywhere in the pipeline and no adaptive ladder, so a 10-bit Main10 HEVC export arrives at the viewer exactly as it was encoded, at the bitrate you gave it. Whether a given viewer's machine decodes it is their decoder's business, which is the subject of the browser section above.
HEVC in the Main10 profile at 4:2:0, in an MP4 or MOV container, at 100 to 200 Mbps for 4K. Main10 is the profile every relevant decoder specification names for 10-bit HEVC, and it is the profile Apple's own HLS authoring specification requires of HEVC streams. That export uploads, stores and streams here untouched, up to 50 GB per file.
That is not documented by any browser vendor. The one official primary document, the Windows HEVC decoder specification, covers 4:2:0 chroma only, and Apple documents 10-bit 4:2:2 HEVC as an encoding feature of Compressor rather than as a browser capability. We will not tell you it plays and we will not tell you it does not. We can tell you what happens on our side: the file is stored and served as uploaded, nothing is re-encoded. The sibling guide on 10-bit 4:2:2 HEVC browser playback lays out every primary document line by line.
Two things stack. The platform re-encodes: Vimeo says your file 'is re-encoded into several formats', and YouTube says it 'always re-encodes videos to optimize their playback quality'. Then the rendition it delivers is bounded. Vimeo publishes a maximum of up to 22 Mbps for its 4K H.264 rendition and up to 16 Mbps on its HDR and above-4K HEVC ladder, and says those figures are ceilings that can come in lower on complex images. A sky that fell off smoothly across a thousand levels is being reconstructed with far fewer bits than it was graded with, and banding is what that shortage looks like.
We do not set one. The practical limit is the viewer's hardware decoder, and the band that machines handle in a browser today is roughly 300 to 400 Mbps. That is an engineering caveat about the viewer's computer, not a product specification, and it sits far above the 100 to 200 Mbps a graded 4K master is normally exported at.
It buffers. There is no adaptive ladder here, so there is no softer rendition to swap in when the pipe narrows. That is the honest trade: nobody is ever shown a mushy version of your grade without being told, and somebody on a weak connection waits. If silent degradation is preferable to waiting for your audience, a ladder is the right tool and you should use one.
Main10 is the HEVC profile that carries 10-bit samples. The Windows HEVC decoder specification lists Main, Main Still Picture and Main10, and states that 10-bit input must declare the Main10 profile. Apple's HLS authoring specification goes further and requires HEVC streams to be Main 10 Profile at all. When the specification the whole streaming industry authors against will not accept 8-bit HEVC, 10-bit is not an exotic request; it is the professional baseline.
uncompressed.io streams the exact bytes you upload. No transcode of video or audio, no adaptive ladder, no delivery ceiling set by us. MP4 or MOV, H.264, HEVC or AV1, up to 50 GB per file.