What Is a DCP File? DNG Camera Profiles Explained
A .dcp file is a DNG Camera Profile: the instructions a RAW converter uses to turn the numbers your sensor recorded into meaningful colour.
It is easy to mistake for a preset or a LUT because all three change how an image looks. The difference is where in the pipeline it acts, and that difference is why a camera profile can fix things a preset cannot.
What a camera profile is for
A sensor does not record colour. It records how much light passed each of three filters, and those filters are different for every camera model. Turning those three numbers into a colour a human would agree with requires knowing the specific sensor's response — and that knowledge is the profile.
Without one, a RAW file is unrenderable in any meaningful sense. Every converter has profiles built in for the cameras it supports, which is exactly why a camera released last month cannot be opened by software that is otherwise current.
A .dcp is that data in a standalone, transferable file, in the format Adobe defined as part of the DNG specification.
What is inside one
A DCP is binary, structured like a TIFF, and holds several distinct pieces that do different jobs.
The colour matrices convert sensor response to a standard colour space. There are usually two, measured under different illuminants — typically tungsten and daylight — and the converter interpolates between them based on the white balance, which is how a profile stays accurate across lighting conditions.
The hue/saturation map is a lookup table indexed by hue, saturation and value, correcting the places where a matrix alone gets colours wrong. This is where a profile fixes a camera that renders, say, deep reds too orange.
The look table and tone curve are the creative layer. They are what separates Adobe Standard from Camera Vivid on the same sensor: identical underlying colour science, different rendering on top.
- ·ColorMatrix1 / ColorMatrix2 — sensor to colour space, per illuminant
- ·ForwardMatrix1 / ForwardMatrix2 — the same, for the profile-connection path
- ·HueSatDeltas — the 3D correction table
- ·LookTable — creative rendering, on top of the corrections
- ·ToneCurve — the default tonal response
Profile, preset, LUT: three different things
All three change colour, and they act at different stages, which is why they are not substitutes.
A camera profile acts first, as part of interpreting the RAW data — before exposure, before contrast, before anything you would recognise as editing. It defines the starting image.
A preset acts next: a set of develop settings applied on top of that starting image, still fully editable.
A LUT acts last, on already-rendered colour, and knows nothing about where it sits in a pipeline. Give it the same pixel and it always returns the same answer.
The practical consequence: if a camera renders a colour wrongly, a profile is the right fix, and a preset or LUT can only paper over it. If you want a look, a preset or LUT is the right tool, and building it into a profile makes it much harder to adjust later.
Where DCP files live
Lightroom and Camera Raw read them from a CameraProfiles directory, and profiles appear in the Profile browser at the top of the Develop panel once they are in place, filed under the camera they were made for.
A profile made for one sensor applied to another is not merely inadvisable, it is meaningless — the matrices describe that sensor's filters. Converters generally hide profiles that do not match the file for exactly this reason.
- ·Windows — %APPDATA%\Adobe\CameraRaw\CameraProfiles
- ·macOS — ~/Library/Application Support/Adobe/CameraRaw/CameraProfiles
Frequently asked questions
What is the difference between a DCP and a preset?
A DCP defines how RAW data becomes colour in the first place; a preset is a set of adjustments applied afterwards. A profile changes your starting point, a preset changes what you do from there. They stack, and most edits use both without the photographer thinking about the first one.
Is a DCP the same as a LUT?
No. A LUT is a fixed table applied to already-rendered colour. A DCP contains matrices that are interpolated according to white balance, so it responds to the lighting conditions of each shot. That adaptivity is precisely what a LUT cannot do.
Why do Adobe Standard and Camera Faithful look different?
Same underlying colour science, different look table and tone curve on top. Camera Matching profiles are Adobe's attempt to reproduce the manufacturer's own rendering — Canon's Picture Styles, Nikon's Picture Controls — so that a RAW opens looking like the camera's screen did.
Can I make my own DCP?
Yes, with a colour target and profiling software such as Adobe's free DNG Profile Editor or X-Rite's tools. You photograph a reference chart under known lighting and the software solves for the matrices. This is worth doing for critical reproduction work — artwork, product, scientific imaging — and rarely worth it otherwise.
Do DCP profiles work outside Adobe software?
Several converters read them, since the format is part of the published DNG specification — RawTherapee and darktable among them. Capture One uses its own profile system instead and does not.
Will a DCP fix a bad white balance?
No, and it is not meant to. White balance is a per-image setting; a profile describes the sensor. What a good profile does is make white balance behave predictably, so that a correction of a given size produces the colour shift you expect.
Open a RAW edit in RawCut's Studio and the Deconstruction Engine separates the profile's contribution from everything applied on top of it.
See a profile's effect