--- title: "Why Do RAW Photos Look Flat Before Editing?" description: "Nothing is wrong with the file: no tone curve has been applied yet. Why linear light looks pale, what the camera screen shows, and how flat differs from underexposed." canonical: "https://freeaigeneration.com/en/guides/why-do-raw-photos-look-flat-before-editing/" robots: "noindex" lang: "en" --- # Why Do RAW Photos Look Flat Before Editing? Open a raw file in a converter for the first time and it looks as if the picture lost its nerve: pale, greyish, low in contrast, faintly disappointing next to the JPEG the camera produced beside it. Nothing is wrong with the file. You are looking at an image that has not yet been told how to look. The flatness is structural, and once the two causes behind it are clear, the develop panel stops feeling like a repair kit. ## No tone curve has been applied yet A raw file is sensor data plus metadata. What the sensor recorded, at 12, 14 or 16 bits per photosite, is roughly proportional to the light that arrived. That proportionality is convenient for arithmetic and unhelpful for viewing, because a display expects an image whose tones have been redistributed for human eyes. The camera does that redistribution when it writes a JPEG. Its image processor applies white balance, a tone curve, saturation and sharpening before quantising to 8 bits, which is why the JPEG looks finished. A converter that respects the raw file applies none of those decisions until you ask it to. Flat is what an unfinished photograph looks like. ## Why linear light looks so wrong The mismatch runs deeper than missing contrast. The working space a browser uses, sRGB (IEC 61966-2-1), is not linear: its encoding compresses the bright end and expands the dark end. Feed linear values into an sRGB screen without transferring them and mid-tones sit far too low. The numbers make it concrete. A linear mid-grey of 0.18 encodes to 0.18^(1/2.4) × 1.055 − 0.055 = 0.4613, which is 118 of 255, not the 46 you would get by reading the linear value as a code value. A linear 0.5 encodes to 188 of 255 rather than 128. The steps are not distributed evenly either: the upper half of linear light, one stop, occupies only the codes from about 188 to 255, a quarter of the range, while the remaining three quarters describe everything below it. That produces two different faults that are easy to confuse. An image shown without the transfer looks far too dark through the mid-tones. An image shown with the transfer but without a curve is correct in brightness and flat in contrast. Which fault you are looking at decides which control to reach for. With the transfer applied and the ends of the histogram pulled in slightly, the same data reads as a normal photograph. The information was always there; the encoding and the curve were the missing steps. ## The camera screen is not showing you the raw file Every preview of a raw frame that a camera displays, on the rear screen or through an electronic viewfinder, is a rendering made with the camera's own curve, sharpening and white balance. It is a JPEG that exists only for display. That is why the two files seem to disagree so strongly. The camera's rendering has already invested contrast; the converter's neutral rendering has not. Neither is lying. They are at different points in the same pipeline. ## What flat is not Flat is not low quality. A washed-out raw frame often has a histogram that spans the full range without clipping at either end, which is a well-exposed capture with headroom intact. The washed-out look is the absence of a curve, not a shortage of data. Flat is not damage either. A file that opens grey and lifeless but responds to a contrast adjustment is working correctly. The failure signature of a broken decode is different: no thumbnail, or a preview that will not update when a slider moves. Flat is also not a second image hiding inside the file. Raw does not contain a secret contrasty version waiting to be revealed; it contains one set of measurements and a lot of parameters left to be decided. ## Telling flat from underexposed Both look dull, and they take different fixes. An underexposed frame has its histogram bunched against the left edge with a long empty stretch on the right; the correction is exposure. A flat frame has data spread across the middle with nothing touching either edge; the correction is contrast and a tone curve. The order matters. Fixing exposure on a flat file pushes the range until it clips, while adding contrast to an underexposed file crushes shadows it just made darker. ## From flat to finished The develop sequence is unremarkable once the cause is understood: place the exposure, then add the contrast and curve the file is missing, then adjust colour. The editor's Edit panel offers Auto, B&W and Reset, the Light panel carries HDR, Exposure and Contrast above an RGB histogram, and tone curves, a colour mixer, masks and crop are part of the develop set. Whether the flat starting point is worth the extra step is a format question rather than a technical one; [RAW vs JPEG](/en/guides/raw-vs-jpeg-which-format-should-you-edit/) weighs the two records against each other. What happens to your adjustments afterwards is the subject of [non-destructive RAW editing](/en/guides/what-is-non-destructive-raw-editing/). Try it on a frame you already own in the free [RAW Photo Editor](/en/tools/raw-photo-editor/): the flat opening is normal, and the panel is where you finish the picture.