CineMatch supported cameras: what if yours isn't listed?
Profile-based matching tools like CineMatch support a specific list of cameras. What actually happens when yours is not on it, which workarounds exist, and what each one costs you.
When your camera is not on a matching tool's supported list, the tool has no measurement of it and cannot include it in a proper match. Your options are: fake it with the closest listed profile, request the profile and wait, match that camera by hand, or use a tool that reads the clip instead of the list.
None of these options is imaginary; editors hit this wall every week, with phones, drones, action cameras, and older B-cams, and the search phrase "cinematch supported cameras" exists because people keep needing to check.
What does a supported-camera list actually mean?
For a profile-based tool, the list is not marketing, it is the mechanism. FilmConvert's CineMatch, a well-built and widely used matching plugin for Adobe Premiere Pro, After Effects and Final Cut Pro, works from lab measurements: in FilmConvert's own words, it "profiles each camera individually under identical shooting conditions", so it knows exactly how each profiled sensor reproduces a given color. As of 2026, FilmConvert's supported-cameras page lists profiles covering roughly seventy cameras across ARRI, Sony, Canon, Blackmagic Design, Panasonic, Nikon, GoPro, Apple and others, with new profiles added over time, recently the Apple iPhone 17 Pro and the Nikon ZR.
That design is a genuine strength for the cameras on the list. It is also a hard boundary. A profile-based tool knows the cameras someone measured in a lab, and no others; the list is the product's entire knowledge of the world. This is a design constraint, not a flaw someone forgot to fix.
What actually happens when your camera is missing?
Less than you might expect. The tool simply has no entry to select for that source. The match it is built to perform, known camera to known camera, cannot include the unknown one. The clip still sits on your timeline looking different from everything else, and the difference is now your job again.
The cameras that fall off lists are predictable: phones older or newer than the profiled models, drones outside the couple of profiled DJI bodies, action cameras, discontinued B-cams, and anything released in the months before the developer gets to it. In other words, exactly the sources that sneak onto real timelines uninvited.
What are the workarounds, and what do they cost?
| Workaround | What you do | What it costs |
|---|---|---|
| Nearest-profile stand-in | Pick the listed camera that seems closest to yours | The match is built on a measurement of a different sensor; you are trusting a resemblance nobody verified |
| Request and wait | Ask the developer to profile your camera | Works only for cameras popular enough to justify lab time, and not on this project's deadline |
| Match by hand | Comparison View and the Lumetri Color panel in Adobe Premiere Pro, clip by clip | Your time and your eye; doable, slow, and covered in our guide to matching different cameras in Premiere |
| Clip-analysis tool | Use software that reads the footage instead of a list | Depends entirely on the reference you choose; no lab knowledge behind it |
The nearest-profile stand-in is the tempting one, so look at it twice. It sometimes lands close, especially within one manufacturer's family. But the entire argument for profiles is measured precision, and a stand-in profile spends that argument: you are back to approximation, now with extra steps.
Why does a clip-reading tool not have this wall?
Because there is no list to fall off. A clip-analysis tool like MOVON Match reads the pixels of the clip in front of it and computes the match from what it sees. It never asks what camera shot the footage, so an unlisted camera is not a special case; there is no recognition step to fail. A camera released tomorrow works the same as one released ten years ago. The full mechanism is in How does AI color matching work?, and the practical answer to "does MOVON support my camera" is yes, and here is why.
The trade does not disappear, it moves. A clip-analysis match depends on the reference you choose, and a poor reference produces a faithful match to a poor target. The two designs and their failure modes are compared properly in Camera profiles vs clip analysis. If your whole production is on a tool's list, that tool is a fine choice. The wall only exists off the list; the point is that real timelines spend a lot of time off the list.
Common questions
Is CineMatch bad software because of the list?
No. CineMatch is good software with a design constraint. Profile-based matching is precise for the cameras it has measured, and FilmConvert keeps adding profiles. The question to ask is not "is it good" but "will every source on my timelines, this year, be on the list".
My camera shoots a log format that IS supported by other cameras on the list. Am I covered?
Not by the profile. A log curve is a container; the profile measures the specific sensor and processing behind it. Two cameras recording the same log format can still render color differently, which is much of why matching tools exist at all.
Can I just ask for my camera to be added?
You can, and developers do take requests. Lab profiling takes equipment, time, and access to the camera, so common bodies get profiled and rare ones mostly do not. Either way, the answer arrives on the developer's schedule, not your delivery date.
Does MOVON have any list at all?
No. MOVON Match ships no camera profiles and keeps no supported-camera list. Footage from Sony, Canon, ARRI, RED, Blackmagic, Panasonic, DJI, Nikon, Fujifilm, and Apple devices matches every day in the beta, and that list is examples, not a boundary. The clip is read as the camera recorded it, and the match is computed from there.
Get the next dispatch in your inbox.
Release notes, color science notes, and the occasional field report. No marketing. Unsubscribe one click.
