Back to blog

Gallery / P4 · CineX

Does CineX Keep HDR and Dolby Vision? It Depends on Whether the Picture Is Re-encoded

CineX can retain HDR and Dolby Vision information when it only changes the video container. On that path, the picture is not recompressed, HDR10 static metadata passes through, and Dolby Vision metadata can survive, with some exceptions. If CineX must re-encode the picture, Dolby Vision metadata is lost and 10-bit / HDR video is converted to 8-bit. The decisive question is what CineX has to do to the picture, not whether the file ends in MKV or MP4. Those paths have substantially different consequences for preservation.

This distinction matters if you are preparing a viewing copy but also care about preserving the characteristics of a particular HDR master. CineX creates an MP4 better suited to opening on iPhone, iPad, and Mac. It does not promise that a file requiring full conversion will retain every feature of its source picture. Here is what each processing path means specifically for HDR10 and Dolby Vision, without trying to predict the fate of an untested file.

1. The outcome follows the picture, not the file extension

“Convert to MP4” describes the destination, not necessarily the journey. CineX may have little to do to the video picture: it can move an already compatible picture into a different container without compressing it again. Or it may need to rebuild that picture before writing the new MP4. These paths have different consequences for HDR. If you want the broader explanation of why they differ, see container changes versus re-encoding.

Two videos can both be named MKV and still contain different video encodings or parameters. Likewise, two files can both be labeled HDR but require different work inside CineX. Neither the extension nor the badge is a reliable shortcut to the outcome. For this question, look past the outside of the file and ask whether its picture can be carried over as it is.

In CineX, keeping HDR and Dolby Vision depends on the picture-processing path. A container-only change preserves the eligible picture and metadata; full re-encoding loses Dolby Vision metadata and converts 10-bit / HDR video to 8-bit.

2. HDR10 and Dolby Vision: keep the picture and its metadata separate

You do not need a technical specification to make sense of the difference. Think of the video picture as one part of the file and the information accompanying that picture as another. HDR10 includes static metadata. Dolby Vision carries its own metadata. When you ask whether CineX “keeps HDR,” you might be asking about the pixels, the information accompanying them, or both. Those are related questions, but they are not interchangeable.

That is why “it is still an MP4” is not an adequate answer. An MP4 is the resulting file type; it tells you nothing by itself about whether CineX recompressed the picture or carried over the HDR10 and Dolby Vision information. Nor does successful playback, on its own, establish that the resulting picture has all the characteristics of the original. The distinction matters particularly when the goal is preservation, not merely obtaining a file that opens.

3. Container-only conversion: the picture stays intact and metadata can travel with it

When CineX can use the picture already in the file, it only changes the container. The video picture is not recompressed, and its bit depth does not change. HDR10 static metadata is passed through. Dolby Vision metadata can also be retained, except in special cases. That last qualification matters: it is a description of the container-only path, not a blanket promise about every Dolby Vision file.

Keeping metadata and avoiding picture recompression are distinct benefits. The first describes information associated with the video; the second describes what happens to the picture itself. Together, they explain why a container-only conversion may suit someone who wants a more directly usable MP4 without having CineX remake an already compatible HDR picture. They should not be stretched into a claim that every input carrying an HDR label will take this path.

When CineX only changes the container, it does not recompress the picture or change its bit depth. HDR10 static metadata passes through, and Dolby Vision metadata can be retained, subject to special cases.

4. Full re-encoding: the Dolby Vision loss and 8-bit change are explicit

When CineX needs to re-encode the picture, Dolby Vision metadata is lost, and 10-bit / HDR video is converted to 8-bit. This is not a minor alteration to a filename. CineX has made a new version of the picture. If the purpose of your copy is to retain the source’s Dolby Vision metadata, a file that takes this route will not meet that purpose.

HDR10 requires equally precise wording, but not the same wording as Dolby Vision. On a container-only path, HDR10 static metadata passes through. On a full re-encoding path, the information changes along with the reprocessed picture; you should not expect an unchanged copy of the source’s HDR10 static metadata. It would be misleading to compress these different outcomes into either “all HDR survives” or “every piece of HDR information disappears.” The documented change to the picture is specific: 10-bit / HDR video becomes 8-bit.

Bit depth is not a review of how a particular scene will look. It tells you something concrete about the resulting video, not how much you will personally like the image. What is clear is that the new 8-bit picture is not the same as the original 10-bit / HDR picture. For an archival or production workflow that requires those source characteristics, the full conversion path is not an equivalent replacement.

If CineX must re-encode the picture, Dolby Vision metadata will be lost and 10-bit / HDR video will become 8-bit. HDR10 static metadata should not be expected to pass through unchanged as it does during a container-only conversion.

5. Why choose a predictable downgrade over keeping the old metadata?

Full conversion changes the picture itself. Information attached to the original picture may no longer describe the newly processed picture accurately. Carrying it across simply to leave an HDR label in place could create a mismatch between that label and what the file actually contains. CineX instead takes a deliberate, conservative route: when it has to re-encode, it accepts the stated bit-depth downgrade rather than retaining Dolby Vision information that may no longer fit the new picture. This is an intentional trade-off, not an intermittent bug.

For someone who mainly needs a video they can open, a predictable result may be preferable to an impressive label attached to a mismatched picture. For someone whose priority is preserving Dolby Vision and 10-bit characteristics, the same trade-off is a reason to stop before using full conversion. Both can be true. The useful information is the precise boundary, not a claim that one outcome is indistinguishable from the original.

6. There is another bit-depth boundary: 12-bit, 4:2:2, and 4:4:4

Even if your file does not advertise Dolby Vision, its picture may have characteristics you want to preserve. CineX’s documented boundary also covers 12-bit, 4:2:2, and 4:4:4 pictures: these are converted to 8-bit. Do not reduce the preservation question to checking for a Dolby Vision label. What happens to the picture is at least as important as what happens to its accompanying metadata.

It also helps to distinguish the purpose of the new file from the purpose of the original. A video that opens in the intended viewing environment is not automatically an untouched copy of the source. CineX creates a new MP4 rather than replacing the original file, so the source remains separate. That is useful, but it does not make the newly converted picture equivalent to the one you started with.

7. Can I tell which path my particular HDR file will take?

The relevant clues are the video encoding and parameters inside the file. If the picture is already of a type the device can play directly and its parameters are within the compatible range, CineX may be able to change only the container. If the encoding or parameters fall outside that range, CineX needs full conversion. That distinction is what determines whether the HDR10 and Dolby Vision information can travel with the picture or encounters the full-conversion limits described above.

Do not turn that rule of thumb into certainty about an individual file. A 10-bit label, a Dolby Vision badge, or an MKV extension does not settle the question. And even on the container-only path, the Dolby Vision metadata statement has exceptions. The actual processing result is what establishes what happened to a specific file. For the decision process itself, see how CineX chooses a conversion path; this article focuses on the HDR consequences after that choice.

8. Limits: what this article cannot promise

The practical question is therefore not merely “Does CineX support HDR?” It is: “Will this file require re-encoding, and if it does, can I accept losing Dolby Vision metadata and receiving an 8-bit picture?” That framing gives you a more useful basis for deciding what to do with this particular source.

Frequently asked questions

If I make an MP4, will Dolby Vision still be there?

Dolby Vision metadata can be retained when CineX only changes the container, with some exceptions. If the picture needs full re-encoding, that metadata is lost. The MP4 extension alone does not answer the question.

Does the same thing happen to HDR10?

Not quite. HDR10 static metadata passes through on a container-only path, and the picture is not recompressed. On the full conversion path, the information changes with the reprocessed picture, and 10-bit / HDR video is converted to 8-bit.

Why would CineX turn my 10-bit video into 8-bit?

It is a deliberate, conservative choice for full re-encoding, not an intermittent bug. Once the picture is rebuilt, CineX avoids keeping metadata that may no longer match and produces a more predictable 8-bit result.

My file says Dolby Vision. Can I know the result before converting?

Not from that label alone. The deciding factors are the video encoding and parameters inside the file, and a specific outcome depends on actual processing. See how CineX chooses a conversion path.

Is changing the container the same as re-encoding the picture?

No. With a container-only change, CineX does not recompress the picture or change its bit depth. Full conversion reprocesses the picture; 10-bit / HDR video then becomes 8-bit. The two paths should not be described as having the same picture-preservation outcome.

Axiom One LLC — CineX. Figures current as of 24 September 2026.