Premiere Pro auto-detects log footage: what it fixes
How automatic log detection and timeline tone mapping work in Premiere Pro 26.3, where to override them, and why two normalised clips still do not match.
Adobe Premiere Pro now auto-detects log footage: drop a Sony S-Log3 or Panasonic V-Log clip on a timeline and Premiere reads the metadata, tags the color space, and tone maps the clip to your sequence automatically. The flat gray look is gone without a preset. That is the fix. What it does not do is make two cameras match, and the gap between those two jobs decides your workflow.
Behaviour below was checked against Adobe Premiere Pro 26.3 (the 26.3.2 update, August 2026).
What does automatic log detection do in Premiere Pro?
When you import a clip, Adobe Premiere Pro inspects its metadata and, for recognised formats, tags the source color space: Sony S-Log3, Panasonic V-Log, Canon Log variants, camera raw formats, and HLG or PQ video such as iPhone footage recorded in HDR. The sequence's color management then converts each tagged clip into the sequence's working space, and tone mapping compresses the wide range of a log or HDR source into a Rec.709 sequence without clipping.
The control lives in the Lumetri panel's Settings tab since the color management rework in Premiere Pro 25, and it carries into 26.3. The project-level switch is called Color Manage Auto Detected Log and Raw Media. With it on, a detected clip shows its space next to Use Media Color Space in the same tab.
The practical result: a log clip looks close to correct the moment it hits the timeline. No display preset from the camera maker, no manual interpretation, no flat footage shipped to a client because someone forgot a step. If you have ever explained to an editor why their S-Log3 looked like fog, this feature retires that conversation.
How do I override the detected color space?
Detection reads metadata, and metadata is sometimes wrong or missing. Footage passed through a transcode, screen recordings of log clips, or older cameras that do not write the tag can come in misread, and a misread is worse than no read, because the normalisation applied is the wrong one.
Two places to fix it. Per clip in the timeline: select the clip, open the Lumetri panel's Settings tab, and set Override Media Color Space to the space the footage was actually shot in. In bulk from the Project panel: select the clips in a bin, right-click, Modify, then Color, and set the color space there; this is the route for batches, since the Lumetri route works one clip at a time.
Timeline tone mapping has its own controls. In the Lumetri Settings tab, the sequence section carries the tone mapping method under Advanced, and you can change the method or switch tone mapping off per sequence if you would rather handle the conversion yourself. One reported catch in recent versions: an override can fail to stick across a relaunch, so if a clip reverts, re-check the override before blaming the footage. If these settings are new territory, the broader map is in Premiere Pro color management, explained plainly.
Does auto log detection make my cameras match?
No, and this is the distinction the feature quietly hides. Normalising a clip makes it look correct on its own. Matching makes two clips look correct next to each other. Auto detection does the first, per clip, and only the first.
Here is why the gap survives perfect normalisation. Color management undoes each camera's transfer curve, the mathematical encoding of the recording. It does not undo each camera's rendering: the sensor's spectral response, the maker's color science, the in-camera processing that decides what "red" means on that body. A Sony body and a Canon body, both detected correctly, both tone mapped correctly, still disagree about the same face, because they disagreed at the moment of capture and normalisation faithfully preserves the disagreement. Cameras do not see color the same way, and why multicam footage never matches walks through the reasons.
| Automatic log detection | Camera matching | |
|---|---|---|
| Works on | One clip at a time, in isolation | Clips relative to a chosen reference |
| Fixes | Flat, gray, washed-out log display | Two cameras disagreeing about the same scene |
| Source of truth | Metadata and the format's published curve | The actual pixels of each clip |
| After it runs | Each clip looks correct alone | Clips agree with each other |
| Cut between two cameras | Still shifts in hue and density | Holds |
Two clips both correctly normalised still do not match each other, because they came from different cameras.
What should the workflow be, then?
Let Premiere Pro's detection do its job. It is good at it, it runs on import, and it costs nothing. Verify the tags on anything that looks off, override the misreads, and your timeline is normalised: every clip individually presentable.
Then match. That step is per clip relative to a reference, and it is the step MOVON Match exists for: select the clips in the sequence, pick the clip whose look should win, and MOVON computes a grade for each selected clip that brings it to the reference. It reads each clip as the camera recorded it, so there is no preparation step, and no conversion to do before matching; the same pass covers the Sony, the Canon and the iPhone, with no camera profile for any of them. It also does not care whether the sources were log, HLG or standard video, which matters on real timelines, where they are mixed. Batch habits for that step are covered in match color across many clips at once, and the two-camera interview case, where the gap between normalised and matched is most visible, gets the full treatment in two cameras, one interview.
Normalise with Premiere. Match against your reference. Two different jobs, and now the first one is automatic.
Common questions
How do I turn on auto detect log footage in Premiere Pro?
In Premiere Pro 26.3 it is on through the project's color settings: open the Lumetri panel, Settings tab, and check Color Manage Auto Detected Log and Raw Media. Detected clips then show their space next to Use Media Color Space. In older versions the switch was a General preference called Auto Detect Log Video Color Space.
Which formats does Premiere Pro auto-detect?
Common log formats with reliable metadata: Sony S-Log variants, Panasonic V-Log, Canon Log, plus camera raw media and HLG and PQ video, including iPhone HDR clips. Formats without metadata tags need a manual color space assignment via Modify, Color, or an override in the Lumetri Settings tab.
Why does my log footage still look flat after import?
Either detection missed the format, the clip's metadata is wrong, or sequence color management is off for that sequence. Check the Lumetri Settings tab: confirm the detected space is right, and confirm the sequence's working color space and tone mapping are active. A transcoded copy of a log clip often loses the tag the detection relies on.
Do I need to normalise my footage before matching it with MOVON?
No. MOVON reads each clip as the camera recorded it and computes the grade from there, so there is no conversion step before matching. Premiere Pro's color management can stay on for viewing either way; the match does not depend on it.
Get the next dispatch in your inbox.
Release notes, color science notes, and the occasional field report. No marketing. Unsubscribe one click.
