How to Set Up Color-Managed Dailies That Match the On-Set Look

A show can arrive in editorial looking nothing like video village for a small number of reasons, and nearly all of them are pipeline reasons. The A camera is in LogC4. The B camera is in S-Log3. The crash cam is some flavor of Rec.709. The show LUT is named “FINAL_v7_REALLY_FINAL.cube,” and three people want to know why yesterday’s dailies look warmer than the monitor on set. The fix is a color recipe that gets repeated exactly. Dailies should use the same recipe the DP used to judge the image on set. Apply it in the same order, with the same camera input assumptions, and render it for the viewing environment editorial will actually use. A color-managed dailies workflow is a repeatable chain:

Identify the camera source color space and gamma.
Normalize that source correctly.
Apply the approved creative look.
Apply shot-level CDL values when used.
Transform to the dailies viewing target.
Render proxies with metadata that can round-trip to editorial and finishing.

Guess at one step, duplicate it, or run it out of order, and editorial receives an image that is technically viewable but creatively misleading.

Dailies match the on-set look when the color chain is repeated in the same order.

Decide how the look will travel before the first shoot day

The color plan belongs in the workflow memo, not in a Slack thread after the first camera card is uploaded. The memo should say exactly what the dailies colorist applies to each clip. The most common options are:

A single show LUT across all footage
A show LUT plus per-shot CDL corrections
Multiple looks selected by camera metadata or scene metadata
An ACES pipeline using input transforms, a look transform, and an output transform
Camera-native look metadata, such as ARRI Look Files, carried downstream

The right choice depends on how much color work set is actually doing. If the DP and DIT run one approved viewing LUT all day and only make exposure decisions, a single show LUT may be enough. If the DIT live grades every setup, dailies needs a reliable way to receive and apply those CDLs or look files. On a show with multiple camera systems, a single LUT can still be part of the pipeline. It can't be the entire pipeline unless it was designed for every source feeding it. This is where many productions get into trouble. A show LUT is often built for a specific camera color space and display target. A LUT built for LogC to Rec.709 isn't automatically safe for S-Log3 or Canon Log. It also isn't safe for V-Log or a baked Rec.709 drone file. Feed the wrong source into a LUT and it shifts saturation and contrast, and it changes skin tone and highlight behavior. Those shifts look like creative intent, but they are transform errors.

Different log sources need the correct input transform before a shared creative look.

Separate technical transforms from creative intent

A clean dailies pipeline treats technical color management and creative look work as separate decisions. The technical side answers: “What is this footage, and how do we display it correctly?” That covers the camera color space and log curve, the input transform and working space, and the output display transform. The creative side answers: “What did the DP and colorist intend the image to feel like?” That covers the show LUT or look file, the LMT and CDL, and primary adjustments such as saturation trims and contrast shaping. Keeping those separate makes the workflow easier to debug. When the image looks wrong, you have four questions to ask, and each one points at a different node. Is the camera input transform wrong? Did the pipeline apply the look twice? Did it use the wrong output transform? Did the CDL come through at all? A typical color-managed order of operations looks like this:

Interpret the source, including camera raw settings, log curve, gamut, ISO metadata, and white balance metadata
Transform the input from camera space into the chosen working space, such as ACES or DaVinci Wide Gamut Intermediate
Apply primary CDL adjustment, including slope, offset, power, and saturation when used
Apply the creative show look, such as a LUT, LMT, ARRI Look File, or equivalent show transform
Apply the output transform for Rec.709 Gamma 2.4, P3, HDR, or another agreed viewing target
Encode the render with the editorial proxy codec, burn-ins, audio sync, and naming

Some workflows put the CDL before the show look. Others place it after a normalization transform but before a display rendering transform. Decide the order, test it, then document it and repeat it on every batch. The same values in a different node order can produce a different image. For dailies, keep shot-level color simple. Primary corrections and show LUTs are portable. Secondaries, power windows, and tracking effects are not, and neither is proprietary grading data. They are much harder to reproduce reliably. That is true in dailies systems and editorial software. It is also true in VFX and final color. If the on-set look requires advanced corrections, test the exact transport path before production depends on it.

Build the pipeline around the camera sources you really have

The dailies system needs to know the origin of each image. Raw formats often carry enough metadata for the software to identify camera color science, but non-raw files may not. ProRes, XAVC, and H.264 files can arrive with incomplete or misleading tags, and so can other video formats. If the dailies colorist guesses, the look match becomes luck. For each camera type, your color plan should capture:

Camera model and recording format
Log curve and gamut
Raw decode settings, if applicable
Monitoring LUT or in-camera look used on set
Whether the look is baked into any files
Whether clip metadata carries the active look name
Any required input transform or IDT
Expected output target for dailies review

This is especially important on mixed-camera shows. These four sources are not interchangeable inputs:

An ARRI ALEXA 35 shooting LogC4/AWG4
An older ALEXA shooting LogC3
A Sony camera shooting S-Log3/S-Gamut3.Cine
A DJI or GoPro source

They may all end up as Rec.709 dailies, but they don't get there through the same transform. Normalize each source correctly so the approved look behaves as expected. In an ACES workflow, that means using the correct input transform for each camera. In a Resolve color-managed workflow, that may mean assigning the correct input color space per clip. In a LUT-based workflow, use camera-specific technical conversion LUTs before a shared creative look. You can also build separate show LUTs for each camera family. The worst version applies one camera-specific LUT to everything because it “looks close.” That passes a quick review on a laptop. It fails when the editor cuts between cameras, when the DP reviews on a calibrated monitor, or when the conform returns to original camera files.

Match the on-set monitor

When someone says dailies should match set, ask what “set” means. Was the DP looking at a calibrated Rec.709 monitor at video village? A DIT cart monitor? An HDR monitor? A wireless client monitor? A camera LCD? A still pulled from the DIT system? The reference display decides the last transform in the dailies chain. A LogC-to-Rec.709 conversion isn't the same as a LogC-to-P3 or HDR transform. ARRI’s newer look workflows separate the creative part of a look from the display rendering transform. That lets the same creative intent be viewed through different target transforms. If the on-set monitor was SDR Rec.709 and editorial receives Rec.709 proxies, matching is straightforward. If set monitored HDR and editorial reviews SDR proxies, define the SDR rendering yourself. The HDR look will not translate on its own.

The display transform has to match the target monitor for set and editorial to agree.

For editorial dailies, Rec.709 Gamma 2.4 is still a common target for controlled viewing. Some teams use Rec.709-A or other variants for web and computer playback, but make that choice consciously. Those targets do not agree with each other. A render made for Gamma 2.4 can look washed out or too contrasty when it is viewed as Gamma 2.2, as Rec.709-A, or in an unmanaged QuickTime player. The important questions are:

What display target did the team use for approved on-set monitoring?
What display target will editorial and creative review use?
Are the monitors calibrated or at least known?
Is the dailies viewer color-managed or browser/player-dependent?
Are stills or reference frames available for comparison?

If editorial is judging dailies in a browser, on office displays, or on home monitors, exact matching isn't always possible. Export a file that is technically correct for its intended target anyway. Don't compensate for a bad viewer by baking random corrections into the dailies. That creates a second mismatch downstream.

Use reference stills as color evidence

Reference stills are one of the easiest ways to prevent look disputes. If the DP, DIT, or colorist approves a frame on set, send that frame with the camera roll or dailies batch. It gives the dailies colorist a target. It also narrows down where a mismatch came from. Was it the set monitor or the dailies transform? Was it the viewer, or did the look file change? Good reference material includes:

Approved stills from the DIT system
The look file, LUT, CDL, or AMF used for that still
Camera source metadata for the matching clip
Display target used when the still was approved
Notes about exposure, white balance, or intended mood when relevant

The still documents the pipeline. If the still and the rendered daily match inside the dailies software but not in the review platform, the issue may be playback color management. If the still doesn't match inside the dailies software, check transform order and source interpretation first, then look versioning and CDL application.

Keep LUT versions predictable and traceable

LUT chaos is a real production risk. Everyone ends up with a different copy, under a similar filename, applied in a slightly different place. A show LUT needs a clear version and owner, plus a note saying what it expects on input and what it produces on output. One LUT might be intended for LogC4/AWG4 input and Rec.709 Gamma 2.4 output. Another might be a creative log-to-log transform meant to sit inside an ACES or color-managed pipeline before the output transform. Those two files aren't interchangeable, even if they create a similar look. Track these details for every look file:

Look name
Version
Intended camera input color space
Intended working space, if applicable
Intended display output, if baked into the LUT
Whether it's creative-only or includes technical conversion
Approved date and approver
Replacement policy when your team issues a new version

Creative-only looks are more flexible than display-baked LUTs, because they can be paired with different output transforms. Plenty of productions still ship .cube show LUTs, and that works as long as you know what the file expects and where it belongs in the chain.

Preserve CDLs and metadata for downstream use

Dailies are part of the editorial and finishing bridge. Editorial may cut with proxies, but finishing needs to relink to the original camera negative. Finishing also wants access to the same color decisions used during the shoot. That means your dailies process should preserve the relationship between:

Original camera filename
Reel or roll name
Timecode
Sound roll and synced audio metadata
LUT or look name
CDL values
Camera color space
Framing metadata
Clip names used by editorial
Any ALE, EDL, XML, AMF, CDL, or other sidecar files

If this metadata is sloppy, the color may look fine on day one but fall apart during turnover. Assistant editors feel it first. Proxies don't relink and source names don't match. Color references can't be traced, and nobody knows which LUT dailies used on scene 42. For color-managed dailies, metadata is part of the image pipeline. A rendered proxy without the color recipe is just a viewing copy. A proxy with traceable source metadata and color decisions supports the work downstream: editorial and VFX pulls, then conform and final grade.

Metadata travels with the daily so editorial and finishing can trace the intended look.

Pick the right level of dailies color

Not every show needs per-shot graded dailies. More color control means more coordination, more metadata, and more places for failure. The best setup is the simplest one that preserves the DP’s intent. For a straightforward single-camera or single-look production, use one approved show look and correct source interpretation. That is fast, consistent, and easy to maintain. For shows where the DIT is making shot-level trims, use CDLs plus the show look. That gives the DP and DIT meaningful control without trapping the show in a proprietary grading setup. For shows with multiple cameras, use camera-specific input transforms. Pair them with either a shared creative look in a common working space or approved camera-specific looks. Don't rely on one camera LUT unless it was built and tested for all sources. For productions using ACES, define each camera’s input transform, the look transform, and the output transform. If your team uses AMF, treat it as the transportable color recipe. It carries the same decisions from set through dailies and editorial, and on to VFX and finishing. For shows with heavy on-set grading, test the exact handoff path. If the grade uses secondaries, keys, or tracking, test it before you commit. Do the same if it depends on proprietary formats. Dailies, editorial references, and finishing all need to reproduce or at least interpret the intent. Otherwise, simplify dailies color to portable primary corrections and save complex shaping for final grade.

Where discrepancies usually come from

When dailies don't match the on-set look, the cause is usually one of a few repeat offenders.

Mismatch pattern	Likely cause	Fast isolation test	Usual fix
One camera looks normal and another looks too saturated, flat, green, or contrasty	Wrong input color space, gamma, or camera-specific transform	Disable the creative look and view each source through only its input transform	Assign the correct input transform per camera or build approved camera-specific paths
Image looks overly contrasty or clipped compared with set	Normalization was applied twice, such as a LUT plus color management	Bypass the technical conversion LUT or the color-managed input transform one at a time	Use either the technical LUT or the color-management transform, not both
CDL values seem to push the image differently than the DIT reference	CDL is applied in a different order relative to the show look or output transform	Compare the same frame with CDL before and after the creative look	Match the documented node order from set and keep it consistent for all dailies
Yesterday's dailies match but today's same setup does not	LUT, look file, or CDL version changed without a controlled handoff	Compare file names, hashes, approval dates, and sidecar metadata between days	Lock look versions, archive replaced looks, and publish a clear replacement policy
Render is correct in the dailies system but wrong in review	Viewer, browser, OS, or monitor is changing the display appearance	Compare the same render on a calibrated reference monitor and in the review platform	Keep the render technically correct for the target and document playback limitations

Common failure modes include:

Your team assigned the wrong input color space to a camera source.
The pipeline applied both a technical conversion LUT and a color management transform, doubling the normalization.
The dailies system applied CDLs in the wrong order relative to the show look.
The DIT updated the LUT, but dailies used an older version.
Reviewers watched Rec.709 Gamma 2.4 renders in unmanaged players that changed the apparent contrast.

The fastest way to troubleshoot is to isolate the chain:

View the source with only the input transform.
Add the CDL.
Add the show look.
Add the output transform.

Compare against an approved reference still at each stage if you have one. If the image breaks after a specific node, you have found the neighborhood.

Make editorial’s copy predictable, consistent, and explainable

Editorial doesn't need mystery color. They need dailies that are synced and properly framed, consistent with set, and stable enough to cut against for weeks or months. The DP needs confidence that the creative review image hasn't drifted. The post supervisor needs a pipeline that another dailies colorist can repeat tomorrow. Finishing needs metadata that can be traced back to the OCN. A strong dailies handoff includes the rendered proxies plus the color context behind them. That context can be simple: “A camera LogC4, show LUT v03, CDL per shot, Rec.709 Gamma 2.4 output,” or it can be more formal through ACES and AMF. Either way, the receiving team should be able to answer three questions without guessing:

What source color space did dailies assume?
What creative look did dailies apply?
What display target did dailies render?

Write those three answers into the delivery note for every batch. If they're missing, even a beautiful on-set look arrives in editorial as an argument.

FAQ

Yes, if that LUT was the approved viewing look and the dailies system feeds it the same type of image in the same order. Pair it with the correct camera input color space, any required CDL values, and the agreed output transform. A LUT built for one log curve or display target shouldn't be applied blindly to every source.

The usual causes are wrong source interpretation and a LUT applied to the wrong log curve. Duplicated technical transforms, missing or misplaced CDL values, and LUT version mismatches do it too. So does a difference between the set monitor and the editorial viewing environment. Browser playback, unmanaged QuickTime viewing, and mismatched Rec.709 gamma assumptions can also make a technically correct file appear different.

Each camera source should be identified and normalized correctly before the creative look is applied. An ARRI LogC4 file, a Sony S-Log3 file, and a baked Rec.709 drone file shouldn't all receive the same camera-specific LUT unless that LUT was designed and tested for all of them. Use camera-specific input transforms, camera-specific technical LUTs, or a color-managed workflow such as ACES or Resolve color management.

CDLs are commonly applied after source interpretation or normalization and before the final display transform. The exact order depends on the show’s chosen workflow. The important point is to document the order, test it, and repeat it consistently. The same CDL values can produce a different result if they're placed before or after a creative LUT.

Yes. Even when proxies have the look baked in, preserve the source filename, reel name, and timecode. Preserve the camera color space, the LUT or look version, the CDL values, and any sidecar files that exist. That metadata lets editorial, VFX, conform, and final color trace what was done and relink accurately to the original camera media.

Treat the color recipe as part of the dailies package rather than a separate email attachment. Aspect gives the team one place to store camera media, reference stills, LUTs, CDLs, and notes together, so the DIT, dailies colorist, assistant editor, and post supervisor work from the same shared cloud filespace.