Best video hosting for colorists
A host that stores your file and streams those exact bytes.

A grade puts its work in two places an encoder finds expensive. The first is the bottom of the range: a lifted-black look, a slow falloff into a shadow, a night exterior held two stops down. Fine differences between adjacent dark values are exactly what coarse quantization throws away, and the result is banding across a falloff you spent an hour shaping. The second is smooth gradation anywhere in the frame: a sky, a wall, a gel wash, a skin tone rolling off into shade. Those are large areas of tiny differences, which is the most bit-hungry thing a picture can contain and the easiest thing for an encoder to approximate away.

Add grain, and the problem compounds. Film grain is high-frequency noise across the entire frame, so it defeats the prediction between frames that modern codecs rely on and forces the encoder to spend real bits everywhere at once. A graded image with heavy grain and deep shadows is not an average video. It is the specific worst case, and it is what a colorist sends.

Read that against the previous section and the two halves lock together. The number is a ceiling, not a promise, and the thing that pulls a file below the ceiling is the complexity of the image. A graded frame with heavy grain and deep shadows is the complex image. The published maximum is therefore the best case for the work least likely to receive it.

The step before the ceiling matters just as much. Vimeo states that during the transcoding process your video file is re-encoded into several formats that will be available to view on Vimeo. There is no setting, plan or upload codec that skips it. Uploading a pristine master gives the encoder a cleaner source to work from, which is genuinely worth doing, but it does not change what the viewer is served.

The player is handed the stored master directly. There is no transcode step, no rendition ladder and no adaptive delivery anywhere in the path, which is why there is no delivery ceiling on this page to compare against Vimeo’s: there is no delivery encoder to have one. A 150 Mbps export plays at 150 Mbps. Files go up to 50 GB each, and no bandwidth is metered on any plan, including the free one. Storage is the only meter.

Three precise statements about codecs, because this is where marketing usually overreaches. First, we never re-encode, so a 10-bit 4:2:2 file is stored and served untouched, exactly as it left the suite. Second, whether a given browser decodes 10-bit 4:2:2 in a video element is not documented by any vendor, in either direction, so the honest instruction is to test the real file on the client’s real machine before you build a review around it. The page on 10-bit 4:2:2 browser playback sets out what is documented and what is not. Third, there is no codec allowlist in our code: what plays is decided by the viewer’s browser decoder, not by a platform rule. Camera RAW never streams anywhere, and the honest workflow is to finish to HEVC or ProRes and upload that. ProRes and DNxHR are hosted for client download rather than played in a browser. 8K plays when the viewer’s hardware decodes it.

And the cost of the trade, stated plainly. With no ladder there is no lower rung, so a viewer on a thin connection buffers instead of quietly sliding to a mushy version. For a public showreel that is a real drawback. For a grade going to four people who have to judge the picture, buffering for ten seconds and then seeing the actual image is the better failure mode, and it is the whole reason to choose this shape of host.

Streaming is often not the point of the delivery. A colorist frequently wants the client, the online editor or the finishing house to take the actual file rather than watch a version of it in a browser. Every film here carries an allow-download switch, and when it is on, the watch page issues a signed download URL so the viewer can save the master.

Two things worth knowing about it. It is per film, so a locked hero grade can be download-enabled while everything else in the library stays view-only, and it is not tier gated: it works on the free plan the same way it works on Vault. The single restriction is that it is forced off for a vaulted film, which is the point of vaulting. Compare that with Vimeo, where downloading from a video’s page is documented as a paid-plan feature, and where keeping your source file at all requires checking the Keep source video files box on a paid account, with Vimeo stating that source files may otherwise be deleted and may not be recoverable.

The practical reading of that: use the host to make the remote look honest, and reserve the reference environment for the moments that need it. A no-transcode link plus a downloadable master covers most of the round trips in a job. The one session that decides the show is still worth doing properly.

Neither of those is a reason to accept a re-encode for the finishing pass. They are reasons to use two tools for two different jobs, which is normal. If you want the underlying mechanism in more depth, the guide on video hosting that does not compress covers the architecture, 10-bit video hosting covers bit depth end to end, and sending graded footage without banding is the practical version of the failure this whole page is about.