Why does log footage look washed out?

Readers ask this question so often that camera manufacturers answer it in their own support material. They answer the panic before they answer the physics. ARRI answers the same question in its Color FAQ: “This is not an error! You have chosen to record in "Log C" – ARRI's native color encoding. Opposed to a "video" image (in REC 709 color space) Log C maintains more details in the lowlight as well as in the highlight areas. Log C is also referred to as the camera negative as it is unprocessed footage.”

The camera negative comparison is the useful part. A negative is not a picture that you look at. It is a picture that you print from. Nobody looks at a negative and decides that the film stock is defective. A log clip is in the same state, because it is an unfinished recording. You finish it in the edit.

Many readers look through the settings to find a switch that they turned on by mistake. No such switch exists. The flat picture is not a preview mode, a stuck filter, or a corrupted file. The flat picture is what the recording contains. To change it, you grade it.

A sensor sees a far wider range of brightness than an ordinary video file can hold. A picture profile decides how the camera fits that range into the file. A standard profile makes the decision at the moment of the recording. It applies a contrast curve that looks correct immediately. The parts that do not fit, such as a blown-out sky or the black under a chair, are lost permanently.

A log profile makes the opposite decision. The Final Cut Camera User Guide states this in one sentence: “Log footage is captured using a logarithmic curve to preserve a greater dynamic range than standard video, resulting in a flat, desaturated image intended for color grading.” The flatness and the extra range are not two facts that you can separate. They are the same fact in two forms.

Panasonic's page on how V-Log and V-Gamut work gives the clearest account of why the picture on your screen looks wrong: “To store this wide range of exposure in the recorded image, a log (logarithmic) contrast curve is utilized. However, displaying this huge range of image contrast (the darkest shadows to the brightest highlights) in Log format on a conventional monitor will result in an image that looks flat and dull to the eye, with colors appearing desaturated. These Log-recorded images are used to provide the greatest possible flexibility for later color correction; they are not intended to be viewed directly.”

A log recording is not for direct viewing. If you judge your clip on the phone screen after the take, you judge a picture that nobody designed for that purpose.

Apple's Motion User Guide glossary describes the full sequence, from the flat recording to the graded result: “A method of encoding video that preserves shadow and highlight details. A log recording takes the dynamic range (exposure range) of the source image and maps it across a logarithmic curve. This allows you to flexibly manipulate the shadows and highlights in post-production. Initially, a log recording looks flat, desaturated, and lacking in contrast. But when you apply a camera LUT or make manual color corrections, the video reflects the natural vibrancy and contrast of the original scene.”

The fastest way to understand the effect is to look at where a log profile puts the tones inside the file. Panasonic publishes exact figures for V-Log in its V-Log/V-Gamut Reference Manual (Rev 1.0, 28 November 2014), on a 10-bit scale: “Gray output code with reflection of 18% is defined as 433, black output code with reflection of 0% as 128, and white output code with reflection of 90% as 602.”

Each column in the table needs a word of explanation. IRE is a 0 to 100 scale for signal level, and a waveform display shows it. The code value is the number that the camera writes into the file. A 10-bit file has 1024 code values, numbered 0 to 1023. Input reflection describes the subject: a black card, a middle gray card, or a white card.

Those numbers mean something only next to an ordinary video standard. ITU-R BT.709-6 (06/2015) is the recommendation behind what most people call standard video. It sets 10-bit black at 64 and nominal peak white at 940. The container is the same, and the 1024 code values are the same. Rec.709 uses almost the full range, but V-Log puts a 90% white card at 602.

About 340 code values are higher than the white card, and no part of a normal picture uses them. The camera does not waste those values. It reserves them for highlights. Highlights brighter than a white card need a place in the file. A window behind your subject, a chrome edge, and a bright sky all keep their detail. Without that reserve, each one becomes a single flat white shape.

The bottom of the range works the same way in reverse. V-Log puts black at code 128, and Rec.709 puts black at code 64. The darkest part of the picture therefore does not press against the floor of the file.

That reserve is the washed-out look. The picture never reaches the top or the bottom of the range. Nothing in the picture is fully white, and nothing is fully black. All the other tones sit closer together in the middle. The same encoding also removes saturation, so your eye reads the result as gray and lifeless. The file loses nothing, and an ordinary player shows the reserved range as dull.

Bit depth belongs in the same discussion. An 8-bit file has 256 values per channel, and a 10-bit file has 1024. A log curve puts a wider range of brightness into the same number of values, so each step covers more brightness.

ARRI states the consequence for its own curve in the LogC4 specification (23 January 2025). The document says that the curve “was designed for 12-bit encoding as its minimum quantization level”, and that 10-bit LogC4 “should not be used for archival or interchange”. That statement covers LogC4 only, and it is not a rule for every log format. The direction is general, because a log curve asks more of the bits than a standard profile does.

The second complaint after the flatness is noise in the shadows. It has the same explanation.

RED describes the effect in its RED 101 article on REDlogFilm and REDgamma: “REDlogFilm images will initially appear flat, with lighter and noisier shadows, along with darker and more abrupt highlights. Tones retain the full dynamic range and are not actually any noisier though they are just being displayed differently.”

The noise is not new. A log curve lifts the darkest part of the picture, so the camera records shadow detail instead of a flat black. The same lift makes the noise in the shadows visible. When you add the contrast in the grade, the shadows become dark again. Most of the visible noise disappears with them.

Underexposure does make the noise worse. If you record a dark picture and then lift it in the grade, you amplify the quietest part of the signal. Noise lives in that quiet part. Underexposure is a different problem from the one in this article. Examine your exposure before you blame the log profile.

If you recorded this clip on an iPhone, one detail needs care. It is the easiest fact in this subject to misread. Apple's own Log recording has a documented device requirement. The Final Cut Camera User Guide states that “Log recording requires iPhone 15 Pro or later.”

That requirement is Apple's, and it applies to Apple's own Log recording in Apple's camera apps. It is not a requirement for log video on iPhone in general. It is not a requirement for a third-party camera app either. A log profile is a tone curve that an app applies to the picture. An app can carry that curve itself and apply it to each frame as it records. Such an app does not wait for Apple to offer Apple Log on your phone.

Log Cam: RAW 4K Video Camera, the app that this site belongs to, works in that second way. It does its own log encoding and applies the curve in its own GPU pipeline. It does not request Apple's Log, so its log profiles are not limited to the iPhones that Apple's Log covers. The app needs iOS 17.6 or later. The quoted sentence is a fact about Apple's feature, and not a verdict on your phone.

One more fact helps before you read other articles. Apple does not publish a dynamic range figure in stops for Apple Log. Every 12-stop or 13-stop number in circulation is a third-party estimate. An article that attributes a stop count to Apple quotes something that Apple did not say. The number is absent because no official source gives one.

The grade is the step that the flatness makes room for. You do the grade in your editor, not in the camera. The order is always the same. First, make the picture look normal. Then give it the look that you want.

The range that you recorded is what makes the second step possible. You can make a bright window darker, or make a face in shade brighter. Real detail is still there in both places. That range is the reason to record log video.

Examine one thing before you start. If the same file looks flat in one app and normal in another, you have a different problem. A LUT will not correct that problem. The last question in the FAQ covers it.

You have two options, and both are correct.

Log video is worth the work when you will edit the footage. That is the whole test.

If you publish a clip directly from the phone, a standard profile looks better and needs no work. That choice is not a compromise. Log video costs you a grade on every clip. It also costs you a picture that you cannot judge correctly during the recording. On footage that you never open in an editor, that cost buys you nothing.

Record log video when the subject matters to you. A stage light, a sunset, or a white shirt in direct sun puts a hard range in the frame. Log video is the version of that clip that you can still rescue next week. The flat gray picture is the price of that range.

This site belongs to Log Cam: RAW 4K Video Camera, an iPhone app that records log video. None of this article depends on that fact. The washed-out picture is the normal result of a log curve, on any camera and in any app.