Using GoPro footage which are in 10-bit color space (yuvj420p), and using Blender as a video editor, the output seems to always be in 8-bit color space.

How can I preserve the 10-bit color space?


  • Output: AVI RAW
  • Output: H.264 + Encoding Format: H.264 + [X] Lossless
  • Output: H.264 + Encoding Format: AVI + Codec: H.264 + [X] Lossless
  • Output: H.264 + Encoding Format: Quicktime + Codec: H.264 + [X] Lossless
  • Output: H.264 + Encoding Format: AVI + Codec: HuffYUV
  • Float color space in sequencer

No matter these, in the end ffprobe always shows it's not anymore in yuvj420p but in yuv420p (or what should be another 8-bit color space format). This results in washed out colors visible on HDR monitors (barely noticeable on older monitors).

Similar questions without good answers yet:

Note: Input video file format (from ffprobe):

Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc), 1920x1080 [SAR 1:1 DAR 16:9], 8217 kb/s, 59.94 fps, 59.94 tbr, 60k tbn, 119.88 tbc (default)
  • 1
    $\begingroup$ Hmm, I have this dim recollection that the VSE is 8bit. Try enabling each strips color management in properties. $\endgroup$
    – 3pointedit
    Commented Feb 15, 2017 at 23:07
  • $\begingroup$ @3pointedit In Sequencer for the video strip (trying with a single strip) I've enabled Colors: Convert to Float and tried various Input Color. Still having no yuvj420p in the end. $\endgroup$
    – Wernight
    Commented Feb 15, 2017 at 23:21
  • $\begingroup$ The difference between yuvj420p and yuv420p isn't the bit depth, but the range. yuv420p has the range 16-235 whereas yuvj420p has the full range, 0-255. Moreover, your input file is encoded with profile High, which doesn't support 10-bit. You'll need High 10, High 4:2:2 or High 4:4:4 Predictive for 10-bit support. So basically your input seems to be 8-bit, and the colour loss is likely caused by the reduced range rather than by fewer bits. Unfortunately, I don't know how to get the VSE to use yuvj420p, so I won't add this as an answer. $\endgroup$
    – user27640
    Commented Feb 16, 2017 at 0:31
  • 1
    $\begingroup$ 3PointEdit wins another one; VSE is always 8 BPP. $\endgroup$
    – troy_s
    Commented Feb 16, 2017 at 7:07
  • $\begingroup$ @DuaneDibbley Thanks for clarifying the format. Would you know which lossless codec is likely to have the largest color range? I can always force ffmpeg to use uyvj420p later and that might do the trick. $\endgroup$
    – Wernight
    Commented Feb 16, 2017 at 17:43

3 Answers 3


You can't.

When working on footage, it is always most prudent to operate on the frame level, with controlled decoding to the file format you choose. Codecs always have been and always will be an awful choice.

Currently in Blender, all codecs via the VSE (and otherwise I believe) are decoded using the FFMPEG call that converts them to an 8 bit buffer.

So, decode outside to a suitable 16 bit container such as TIFF, then properly linearize the results via a controlled transform.

Also, “8 bit” is not a colour space, nor is “10 bit”, nor is “float color space”.


Answering my own question here, it looks like it's possible by rendering as PNG then using:

ffmpeg -framerate 500/21 -i %d.png -i audio.wav -c:v libx264 -crf 0 -pix_fmt yuv422p10le -c:a copy output.mkv

See https://youtu.be/Ng8bS2iPS1w?t=922


As other have said convert to png and back but your answer makes a 20 b/px file from a 12 b/px file which is wasteful;

ffmpeg -pix_fmts 2>&1 | grep -P "yuvj?420p |FLAGS|yuv422p10le"
IO... yuv420p                3             12      8-8-8
IO... yuvj420p               3             12      8-8-8
IO... yuv422p10le            3             20      10-10-10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .