Why doesn't Premiere Pro auto-detect Canon Log on my MP4 files?

The classic 'Auto Detect Log Video Color Space' toggle only ever worked on Canon footage in an MXF container — MP4 recordings, common on R-series bodies, weren't auto-detected, and some Canon models don't write color space info into MP4 metadata at all. Recent Premiere versions (2024+) have a broader Color Management system that auto-processes RAW across more cameras, so check which system your version uses. The log/gamma tag also usually doesn't survive a transcode to ProRes or H.264 — ask whoever transcodes to note the original log format in the filename.

Tools/Canon LUTs

Canon LUTs Guide

What each Canon Log LUT actually does, where to get it, and how to lay it down in your edit app of choice — without losing an afternoon to a mis-tagged clip.

~5 minute read · updated Jul 2026

Not sure what any of the terms below mean? Skip straight to the confidence check — it tells you if your footage is fine without needing to understand why.

One more thing worth knowing: this guide covers both standard Log footage and RAW. RAW is for the highest possible image quality when you have the storage and post-production time to match; standard Log footage with the right LUT gives you perfectly good, usable, broadcast-ready footage with far less overhead — most jobs only need that. Whichever you shot, switch between them right at the top of the workflow builder below.

Written by Keith Ingram, Glasgow-based Director of Photography — owner-operator on a Canon Cinema EOS package.

If you're producing

Deciding before the shoot and don't have an editor yet? You can still choose your Log setting and delivery LUT in the workflow builder — that decision stands on its own — and export it as a PDF to hand off later. Already shot and just need to know it's fine? Run the confidence check below instead.

If you're editing or grading

Jump straight to building the workflow — pick what was shot, the delivery LUT, and your app, for a step-by-step setup plus a printable pre-shoot sheet.

The easy confidence check

Cinema RAW Development (for RAW files)

DOWNLOAD ↗

If you shot Cinema RAW Light and want one sanity check before handing it off, use Canon's own Cinema RAW Development software. It reads the camera's Color Space and Gamma correctly — no guesswork — and lets you preview the footage with a gamma or LUT applied. If the preview looks like a normal, well-exposed picture, the file's metadata is intact and the workflow builder below will carry that same correct read into your edit app.

Worried about what your footage actually is?

For standard (non-RAW) Log files, the color space and gamma are written openly into the file, and a free tool like MediaInfo will show you exactly what's tagged — no camera or Canon software required. RAW and Cinema RAW Light are the exception: that metadata is compressed and NLEs don't always parse it consistently, even when it's there. For those, Cinema RAW Development (or a proper look at the file straight off the camera) is the safest way to confirm what you've actually got.

Build your workflow

This part's for whoever is setting up the edit — an editor, DIT or colorist. Pick what was shot, the delivery LUT and the app, and it'll lay out the exact steps — plus a printable pre-shoot sheet you can hand off.

Standard (Log)

RAW

+ Show technical detail (gamma specs, LUT internals)

+ Planning before the shoot? See pros & cons of each stage

For deciding before you roll — weigh these before you commit to a setting on the day.

STAGE 1 — LOG SETTING

Canon Log

ADVANTAGE

Simplest to post — smallest chance of a Log-variant mix-up, works with older gear and plugins.

TRADE-OFF

Least dynamic range headroom of the three — less room to recover blown highlights or crushed shadows in the grade.

Canon Log 2

ADVANTAGE

Much wider dynamic range, more highlight protection for tricky or contrasty lighting.

TRADE-OFF

Needs 10-bit recording and correct metadata to decode cleanly — flatter image means less confidence checking it on a small monitor.

Canon Log 3

ADVANTAGE

Same wide range as Log 2 with easier default skin tones — the factory-default choice on current bodies.

TRADE-OFF

Shares its metadata tag space with Log 2, so it's the variant most likely to get mis-read in post — flag it clearly for your editor.

STAGE 2 — LUT / DELIVERY TARGET

Rec.709 delivery LUT

ADVANTAGE

Fastest turnaround — the image looks right immediately, no colorist required.

TRADE-OFF

Locks you into HD/SDR — no way back to HDR or 4K wide-gamut later without reprocessing from the log source.

Rec.2020 / HDR delivery LUT (PQ or HLG)

ADVANTAGE

Matches the 4K/UHD and HDR spec some platforms require, using the wider gamut you shot.

TRADE-OFF

Only worth it if you know the platform needs it — harder to preview without an HDR monitor, and adds a compatibility check.

No LUT — grade natively

ADVANTAGE

Full creative and dynamic range control — the best result if you have the time and a colorist.

TRADE-OFF

Slowest option and needs a trained eye and correct color management — easy to get wrong without one.

STAGE 3 — EDIT APP

Premiere Pro

ADVANTAGE

Auto-detects Canon Log tags on most modern camera files — easy if you're already in Adobe's ecosystem.

TRADE-OFF

Auto-detect isn't 100% reliable across every model/codec — RAW files often need a manual override.

DaVinci Resolve

ADVANTAGE

The most complete color-management and LUT toolset — the gold standard for grading control.

TRADE-OFF

Steeper learning curve, and still needs a manual per-clip color space check.

Final Cut Pro

ADVANTAGE

A clean, dedicated Log Processing field per clip — quick to spot and fix at a glance.

TRADE-OFF

Fewer manual override options than Resolve, and Mac-only.

Avid Media Composer

ADVANTAGE

Rock-solid for larger episodic and turnover-heavy workflows.

TRADE-OFF

No reliable auto-detection at all — every clip must be set manually or baked in at transcode.

Downloads

Canon EOS / Cinema EOS support downloads

DOWNLOAD ↗

Model-specific "Look" (.cube) LUTs and Custom Picture files live under Software on each camera's support page.

Canon Log to Rec.709 (standard)

DOWNLOAD ↗

For older C-Log bodies (C100/C300 Mk I & II, 5D/EOS Cinema). BT709_CanonLog-to-BT709_WideDR.

Canon Log 2 / Log 3 to Rec.709

DOWNLOAD ↗

For C200/C300 Mk III/C500 Mk II and current EOS R Cinema bodies. BT2020_CanonLog2(3)-to-BT709_WideDR.

Wide DR Gamut / BT.2020

DOWNLOAD ↗

For HDR finishing — keeps the full Cinema Gamut/Log range for grading in Rec.2020 or PQ/HLG.

Canon ships LUTs per camera model, not as one universal pack. On Canon's support site, select your exact body, then look under Software for the "Look" or "Custom Picture" file — not just the firmware. If your model isn't listed above, the same naming logic applies: [input space]_[input gamma]-to-[output space]_[output gamma].

Common hiccups

Tap one open — most people only need the first two.

C-Log 3 read as C-Log 2 (or vice versa)

−

The most common one. DaVinci Resolve in particular has been reported decoding C-Log 3 (and Cinema RAW) clips as C-Log 2/Cinema Gamut by default — the image data is identical, only the tag is wrong, so nothing looks broken until you grade it and the curve is off. Always spot-check the reported gamma against what you set in-camera.

MP4 files (and transcodes) often carry no tag at all

The classic "Auto Detect Log Video Color Space" toggle only ever worked on Canon footage in an MXF container — MP4 recordings, common on R-series bodies, aren't auto-detected by it, and some Canon models don't write color space info into MP4 metadata in the first place. Recent Premiere versions (2024+) added a broader Color Management system that auto-processes RAW across more cameras, so check which system yours is running. Either way, the log/gamma tag usually doesn't survive a transcode to ProRes or H.264 — ask whoever transcodes to note the original log format in the filename.

Full range vs. legal range

Canon cameras output full-range (0–255/0–1023) video. Without the matching metadata, some edit apps display or export it as legal range, crushing blacks and clipping whites slightly. Worth a levels check on a waveform before you trust what you're seeing.

LUT applied twice

If a monitor LUT was baked in on set (via a Ninja/Shogun recorder set to "legalize" or a viewing LUT burned in), applying the same conversion again in post double-corrects the image. Confirm with whoever pulled focus/monitored on set whether anything was baked in before you grade.

Grabbing the wrong LUT variant

Canon names LUTs input-space_input-gamma-to-output-space_output-gamma — it's easy to grab a BT2020-in LUT for footage that's actually tagged BT709-in, or a Log 2 LUT for Log 3 footage. Match the filename to your camera's picture profile exactly, not just "the Canon one."