Log is a low-contrast recording curve designed to preserve and distribute scene information for color work. It is not the codec, container, bit depth, color gamut, or a guarantee of more dynamic range.

A reliable Log workflow records the exact camera profile and gamut, exposes without clipping important detail, tags the source correctly, transforms it once into a managed working/output pipeline, and uses scopes to verify the result.

Updated July 30, 2026. Color-management guidance was checked against current Adobe and Apple documentation. Camera profiles, supported transforms, and application behavior can change by model and software version.

What Log is—and what it is not

Swipe the table horizontally to see all columns.

TermWhat it controlsExample
Log curveHow scene brightness is encodedS-Log3, C-Log 3, Apple Log
Color gamutThe primaries and color volume used with the curveS-Gamut3.Cine, Cinema Gamut, Wide Gamut 4
CodecHow frames are compressed or storedProRes, H.264, H.265
ContainerThe file wrapperMOV, MXF, MP4
Bit depthHow many code values describe the image8-bit, 10-bit, 12-bit
RAWEncoded camera/sensor data before a normal display renderingProRes RAW, BRAW, camera RAW

Those properties work together. “It was shot in Log” is incomplete handoff information. Ask for the camera, profile, gamut, codec, bit depth, exposure approach, white balance, monitoring LUT, and intended output.

When Log helps—and when it does not

Log is useful when the scene contains highlight and shadow detail you want to shape later, the camera records a robust signal, and the production has a monitored post workflow. It also helps match cameras when each source is normalized correctly into a common working space.

Log does not repair clipped highlights, crushed shadows, poor focus, mixed color temperatures, or incorrect white balance. On some cameras, low-light noise, 8-bit recording, aggressive compression, or a rushed turnaround can make a standard profile safer.

  • Choose Log: controlled exposure, 10-bit or better recording, planned grading, difficult contrast, or multi-camera matching.
  • Choose a standard profile: immediate delivery, limited monitoring, fragile recording formats, or a scene that does not benefit from the extra grading latitude.

Common Log profiles and paired gamuts

Swipe the table horizontally to see all columns.

Camera ecosystemCurrent profile familyWorkflow note
AppleApple Log, Apple Log 2Use the matching Apple camera LUT or managed input transform
CanonCanon Log 2 / Canon Log 3 + Cinema GamutConfirm curve and gamut; they are separate choices
SonyS-Log2 / S-Log3 + S-Gamut3 or S-Gamut3.CineS-Log3 alone does not identify the gamut
PanasonicV-Log + V-GamutUse Panasonic's matching transform or managed tag
FujifilmF-Log, F-Log2, F-Log2 CSupport depends on camera and editor version
NikonN-Log; supported Log3G10 workflowsRecord the exact camera/RAW path used
Blackmagic DesignBlackmagic Film Gen 5Generation matters for the input transform
ARRILogC3 or LogC4 + matching wide gamutDo not interchange LogC3 and LogC4 transforms
DJID-Log + D-GamutCheck aircraft/camera-specific guidance
REDLog3G10 + REDWideGamutRGBOften managed through the RAW decode pipeline

This is a reference map, not a universal LUT list. The correct transform depends on the exact curve, gamut, camera implementation, application version, and intended output.

Color-Gamut

A color-gamut graphic showing why a Log curve and gamut must be identified together.

Capture and handoff checklist

  1. Record the exact profile and gamut, not just “Log.”
  2. Use a recording codec and bit depth suitable for the planned grade.
  3. Set intentional white balance; Log does not make white balance irrelevant.
  4. Protect important highlights while respecting the camera maker's exposure guidance.
  5. Use an appropriate monitoring transform rather than judging the flat image blindly.
  6. Slate or document camera, profile, gamut, ISO/exposure method, LUT, and output intent.
  7. Preserve originals and metadata through ingest and proxy creation.

Modern Log workflow in Adobe Premiere

Current Premiere color management separates the input color space, working color space, and output color space. Premiere can automatically detect supported Log and RAW media, but metadata is not always complete. Verify source tagging instead of assuming the flat picture proves the clip is configured correctly.

  1. Inspect the clip's color-space assignment and correct it when metadata is missing or wrong.
  2. Choose a sequence working color space that fits the job.
  3. Choose the intended output: normally Rec.709 for SDR, or a deliberate Rec.2100 HLG/PQ pipeline for HDR.
  4. Grade after the technical input transform, while monitoring the output transform.
  5. Use scopes to verify exposure, neutral balance, gamut, and output limits.

A Direct 709 workflow can suit a straightforward SDR edit. A wide-gamut, tone-mapped sequence can be more flexible for mixed cameras and multiple outputs. The right choice is the one the team can monitor and deliver consistently.

Color management, technical LUTs, and creative LUTs

  • Managed input transform: the application converts a correctly tagged source into the working space.
  • Technical LUT: a profile-specific normalization used when a managed transform is unavailable or intentionally bypassed.
  • Creative LUT: a look, not a substitute for correct source normalization.
  • Display/output transform: maps the working image to Rec.709, HLG, PQ, or another target.

The classic failure is double normalization: Premiere automatically manages the Log clip and the editor adds a camera-to-Rec.709 LUT again. The result is often crushed, oversaturated, or too contrasty. Check source tagging and the sequence pipeline before adding another transform.

Log and camera LUTs in Final Cut Pro

Final Cut Pro can apply camera LUTs at the media level before clip effects. That is different from adding a creative LUT effect later in the stack. Confirm the library and project color processing, the camera LUT assigned to the source, and the intended SDR or HDR output.

Apple's current documentation includes support for Apple Log and Apple Log 2 as well as multiple camera Log families. Use the matching transform and keep a note of any custom LUT used in the project handoff.

Use scopes instead of trusting the flat picture

A waveform shows luminance distribution; RGB parade helps compare channels and find color imbalance; the vectorscope shows chroma direction and saturation. Scopes do not replace a calibrated display, but they reveal clipping, crushed levels, casts, and out-of-range output that a bright or uncalibrated screen can hide.

The authentic Premiere capture below shows a scopes-based color workspace. The precise panel layout may differ in current releases, but the measurement roles remain useful.

Color-Correction-In-Premiere-Pro-Scopes-Layout

An authentic Premiere Pro scopes workspace for evaluating a normalized Log image.

Troubleshooting common Log problems

Swipe the table horizontally to see all columns.

ProblemLikely causeCheck
Still flat after setupMissing/wrong input transformProfile, gamut, clip tag, sequence color setup
Crushed and oversaturatedDouble transformAutomatic management plus manual LUT
Washed-out exportOutput or player mismatchSequence/output space, export tag, review app
Cameras do not matchWrong source tags or white balanceNormalize each camera separately before matching
Noisy shadowsUnderexposure or aggressive liftOriginal exposure, ISO, transform, noise reduction
Highlights remain clippedCapture clippingOriginal channels and RAW controls if available

Frequently asked questions

Is Log a video format or codec?

Usually no. Log describes a transfer curve, normally paired with a named color gamut. The recording still uses a codec and container. Record the profile, gamut, codec, bit depth, and camera because all can affect the transform.

Does shooting Log increase a camera's dynamic range?

Log redistributes the scene information the camera captured so highlights and shadows can be encoded and graded more flexibly. It does not increase the sensor's physical range or recover clipped exposure.

Is RAW the same as Log?

No. RAW concerns captured or encoded sensor data. Log is a transfer characteristic. RAW footage is often decoded into a Log working representation, so the concepts can appear together.

Should I apply a LUT to every Log clip?

No. A color-managed workflow may perform the technical transform without a manual LUT. If you use a technical LUT, match it to the exact profile and gamut and avoid applying a second normalization transform.

Why does Log footage look flat?

The low-contrast appearance is expected before the correct display transform. First confirm the clip's input color space and the sequence/output color space; then make creative contrast and color decisions.

What is the normal delivery color space for Log footage?

Rec.709 is the common SDR output target. Rec.2100 HLG or PQ requires an intentional HDR working, monitoring, export, and review pipeline.

Can I mix different Log profiles in one timeline?

Yes, if every source is tagged or transformed from its own profile and gamut into a common working space. Do not use one camera LUT on unrelated footage.

When should I avoid shooting Log?

Use a standard profile when the camera's Log implementation, recording bit depth, exposure conditions, turnaround time, or monitoring setup makes Log more fragile than useful. A well-exposed standard profile can be the safer choice.

Official sources

Joseph Nilo, video producer and creator workflow writer
About the Author

Joseph Nilo has been working professionally in all aspects of audio and video production for over twenty years. His day-to-day work finds him working as a video editor, 2D and 3D motion graphics designer, voiceover artist and audio engineer, and colorist for corporate projects and feature films.