Sony A7 IV S-Log3 Color Grading in DaVinci Resolve, Explained

Resolve Color Management or a manual Color Space Transform node, which one should you use?

Both get you to the same place. Which one fits depends on how much of your project is A7 IV footage shot the same way versus a mix of cameras and log formats.

Resolve Color Management, set under Project Settings, Color Management, with Color Science set to DaVinci YRGB Color Managed, lets you assign S-Gamut3.Cine and S-Log3 as a clip's input color space directly through Clip Attributes, and Resolve applies the conversion automatically without you touching a node on every clip. That's the faster setup for a project built almost entirely from A7 IV footage shot the same way, and it's the approach Color Culture's own step-by-step walkthrough recommends, which sets "Color science to DaVinci YRGB Color Managed" and picks "HDR DaVinci Wide Gamut Intermediate" as the color processing mode before selecting "S-Gamut3.Cine/S-Log3" directly on the input side, as documented in their guide to grading S-Log3 in Resolve.

A manual Color Space Transform node gives you more control per clip or per group, which matters the moment you're mixing A7 IV footage with a different camera in the same timeline. You can normalize each camera's native color space independently before applying one shared creative grade across all of them. Our guide to color matching different cameras in DaVinci Resolve covers that multi-camera normalization step in more depth if your project isn't A7 IV-only.

To set up Resolve Color Management on an A7 IV project, open Project Settings, the gear icon in the bottom right, and go to the Color Management panel. Set Color Science to DaVinci YRGB Color Managed, set your Timeline Color Space to DaVinci Wide Gamut / Intermediate, and set Output Color Space to Rec.709 or your actual HDR target. From there, select your A7 IV clips in the Media Pool, right-click, and open Clip Attributes to assign Input Color Space and Input Gamma once per clip or per group of clips.

What ISO should you shoot S-Log3 at on the A7 IV for these settings to work correctly?

The Color Space Transform math assumes you exposed the footage the way S-Log3's gamma curve was designed for, and getting that wrong upstream isn't something Resolve can fully fix downstream.

The A7 IV uses a dual base ISO sensor, meaning it has two points where the sensor's analog gain circuit resets and noise performance improves, rather than degrading smoothly across the whole range. For S-Log3 specifically, those two base points are ISO 800 and ISO 3200, according to a documented reference of Sony's base ISO values by camera by film editor Keith Knittel, who notes that most current Sony bodies "have dual base ISOs, or at least a second ISO value where the image cleans up." ISO 800 is the floor most hybrid shooters should treat as their default for daylight and well-lit interior work; ISO 3200 is the second clean point to jump to in low light rather than pushing gain gradually upward through the noisy range between them.

Sony's own official documentation is direct about the tradeoff involved in exposing S-Log3 away from that base. Per the ILCE-7M4's help guide, "When using S-Log2 or S-Log3 gamma, the noise becomes more noticeable compared to when using other gammas," and it recommends shooting brighter to improve noise, while noting that doing so narrows your usable dynamic range, straight from Sony's own Picture Profile page for this exact camera. That's the same headroom tradeoff colorists warn about across the Sony ecosystem generally, not something specific to the A7 IV.

Cinematographer Alister Chapman, who has written extensively about S-Log exposure across Sony's cinema and mirrorless lines, has pushed back on the older habit of overexposing S-Log3 by a stop or two out of caution, noting that Sony's more recent camera generations "were already down rated to 800 ISO, making them less noisy, so always shooting brighter really isn't necessary" the way it was on the original A7S and FS7. The A7 IV, released after that generational noise improvement, falls squarely into the "expose it well, don't chase extra brightness by default" camp Chapman describes.

Exposing S-Log3 below the A7 IV's ISO 800 base doesn't just make footage darker, it works against the entire reason to shoot S-Log3 instead of a standard picture profile in the first place. If your A7 IV footage still clips highlights or shows crushed shadows after a correct Color Space Transform, check your original ISO before you spend more time on the color node. A curve exposed off its intended base won't grade like one that hit it.

Does S&Q slow motion change the ISO math for S-Log3 on the A7 IV?

Slow motion doesn't get its own exposure rules, but it makes the ones covered above harder to hit, and that's worth knowing before you're on set shooting 120fps at f/2.8 in a dim room.

Sony's own help guide is direct about why: "In slow-motion recording, the shutter speed becomes faster and you may not be able to obtain the proper exposure. If this happens, decrease the aperture value or set the ISO sensitivity to a higher value," per the ILCE-7M4's S&Q Settings page. Shooting 120fps at a conventional 180-degree shutter angle means a shutter speed around 1/240s or faster, roughly four stops tighter than the 1/50s you'd use at 24fps, and every one of those stops has to come from somewhere: a wider aperture, more light on set, or more ISO.

That last option is the one that collides with the ISO base points covered earlier in this guide. Sony's ISO documentation confirms the available range itself shifts with your Picture Profile Gamma, noting that "the available range for ISO sensitivity varies depending on the setting for [Gamma] under [Picture Profile]," and separately that "the available ISO settings will differ depending on whether you are shooting still images, shooting movies, or shooting slow-motion/quick-motion movies," according to the same camera's ISO help page. None of that changes where S-Log3's two clean noise floors sit, ISO 800 and ISO 3200. It just means a slow motion shot in anything less than bright, even light will often need enough extra exposure compensation that jumping straight to ISO 3200, rather than nudging up through the noisy range in between, is the correct move rather than a compromise.

Outdoors in daylight, 120fps S&Q rarely forces the issue: there's usually enough light to open the aperture and stay near ISO 800. Indoors or in mixed light, plan for ISO 3200 before you roll rather than discovering it mid-shot, since chasing exposure by nudging ISO up in small increments during a slow motion take is exactly the noisy middle ground the base ISO section above warns against.

A slow motion S-Log3 shot doesn't have a separate noise budget from a normal-speed one, it just spends that same ISO 800-or-3200 budget faster. If a 120fps clip looks grainier than the rest of your footage from the same scene, check its actual recorded ISO before assuming the frame rate itself is the problem.

How do you judge S-Log3 exposure on the A7 IV's screen if the image looks flat and grey?

A correctly exposed S-Log3 frame looks wrong on the A7 IV's own LCD and viewfinder, by design, which makes judging exposure by eye during a shoot close to useless unless you turn on the one feature built specifically to fix that.

Sony's help guide explains the underlying reason directly: "Movies with S-Log gamma are assumed to be processed after shooting in order to make use of the wide dynamic range," per the ILCE-7M4's Gamma Display Assist page, which is Sony's way of saying the flat, low-contrast image you're seeing is intentional and not a preview problem. Gamma Display Assist exists to undo that flatness on your monitor and viewfinder only, without touching the actual recorded file, so what you're judging exposure against looks like a normal-contrast image instead of a grey, washed-out one.

The specific look that assist applies depends on the Gamma Disp. Assist Type setting, and the A7 IV gives you several: Auto, which reads your current Picture Profile and picks a matching conversion automatically; S-Log2→709(800%) and S-Log3→709(800%), which each "displays images with an S-Log[2/3] gamma reproducing contrast equivalent to ITU709 (800%)," matched to whichever log curve you've actually selected; and HLG(BT.2020) and HLG(709), which adjust the display "to a quality that is almost the same as when images are displayed on an [HLG] compatible monitor," for shooters previewing an HDR delivery rather than a Rec.709 one, according to the camera's Gamma Disp. Assist Type page.

For the workflow this guide covers, that means setting Gamma Disp. Assist Type to S-Log3→709(800%) specifically, not Auto, whenever you're shooting S-Log3 for the two-node Color Space Transform pipeline described earlier. Auto is a reasonable default if you switch Picture Profiles often and don't want to remember to change the assist type every time, but it's one more layer of guessing between you and a display that actually matches what you shot. Setting the type explicitly removes that guess.

This matters because the Color Space Transform math covered throughout this guide assumes correct exposure at the sensor, not correct exposure as judged against a flat, uncorrected S-Log3 preview. A shot that looks underexposed on a plain S-Log3 monitor image might actually be exposed correctly, and a shot that looks fine on that same flat image might be crushing shadows you won't catch until you're already in the grade. Gamma Display Assist doesn't replace a waveform or histogram, both of which still read the actual signal regardless of what contrast curve you're viewing it through, but it puts what your eye sees closer to what your exposure decisions should be based on.

Gamma Display Assist changes what you see on the A7 IV's screen, never what gets written to the card, which is exactly why it's safe to leave on for every S-Log3 shoot without worrying it'll affect your Color Space Transform settings later. Confirm the assist type matches your actual gamma before you trust what the LCD is showing you.

Does auto white balance work for S-Log3, or should you set it manually on the A7 IV?

Auto white balance isn't wrong on S-Log3 the way an incorrect gamut or gamma setting is wrong. It's just a variable you're choosing to introduce into every clip instead of controlling once.

White balance doesn't touch the values in your Color Space Transform at all. It's applied before the sensor data ever reaches Input Color Space or Input Gamma, and it gets corrected, if it needs correcting, in your primary grading node after the Color Space Transform has already converted the clip into DaVinci Wide Gamut, the same node where the worked example later in this guide sets white balance with an eyedropper on a neutral reference. What white balance changes is how much work that node has to do, and how consistently, from clip to clip.

Auto white balance re-evaluates the scene continuously, which means two takes of the same subject in the same light, shot a minute apart, can land on slightly different color temperatures without you noticing on a flat S-Log3 preview. That's a minor issue on a normally-graded picture profile where the difference is subtle enough to ignore. It's a bigger issue on S-Log3, where the low-contrast image already makes small color shifts harder to spot by eye, and where you're relying on a single primary correction node to normalize the whole scene before your creative grade goes on top. A white balance that drifted between takes turns one correction into several, clip by clip, instead of one setting applied once.

A locked, manual white balance, either a specific Kelvin value dialed in for the lighting on set or a custom white balance taken off a grey card or white reference at the head of the scene, removes that variable entirely. Every clip from that setup starts from the same color temperature, so the eyedropper-and-neutral-reference step in your primary node does the same job across the whole scene instead of a slightly different one on every cut.

This isn't a rule specific to the A7 IV or to Sony's color science. It's the same reason cinematographers lock white balance on any log-gamma camera rather than leaving it on auto: a flat image hides small shifts that a normally-contrasted one would make obvious, and log footage gets pushed hard enough in the grade that those hidden shifts show up eventually. If a scene changes lighting mid-shoot, tungsten practicals to daylight through a window, re-white-balance deliberately for the new light rather than letting auto quietly drift there over several takes.

A locked manual white balance doesn't change a single Color Space Transform value, it just means your primary correction node is solving one consistent problem instead of a slightly different one on every clip. If footage from the same scene needs a different white balance pull in Resolve shot to shot, check whether auto white balance was on before you assume the difference is a grading choice.

S-Log2 vs S-Log3, which one should you actually shoot on the A7 IV?

S-Log3 for nearly every hybrid shooting situation, and the reason comes down to how each curve distributes its stops rather than either one being generically "better."

S-Log3 has a gentler, more film-like shadow rolloff and, per Sony's own help guide language quoted above, is designed with "more similar features to film" than S-Log2. It's also the log curve used consistently across Sony's Cinema Line, the FX3, FX6, and FX9, which matters directly if you're ever intercutting A7 IV footage with a Cinema Line camera on the same project, since matching two clips that already share the same gamma curve is a smaller color problem than matching two that don't.

S-Log2 predates S-Log3 in Sony's lineup and distributes dynamic range differently, with a shadow curve that tends to need more careful handling to avoid noise or banding in the darkest regions. It still shows up in some older LUT packs and legacy production pipelines built before S-Log3 became Sony's default recommendation, which is really the only scenario where reaching for it on an A7 IV makes practical sense today.

S-Log3 is the log curve Sony's own Cinema Line standardizes on, and it's the one this entire settings guide is built around because it's the curve nearly all current A7 IV footage actually arrives in. Unless you have a specific legacy-pipeline reason to shoot S-Log2, S-Log3 is the more forgiving, better-matched default.

Is S-Cinetone a better option than S-Log3 for the A7 IV?

They solve different problems, and picking between them is a decision about how much grading time you have, not a question of which one is objectively higher quality.

S-Cinetone is a picture profile Sony carried over from its Cinema Line, matching "the look of the critically acclaimed VENICE" cinema camera according to Sony's own marketing for the profile, and it's designed to look natural and correctly saturated straight out of the camera with little to no grading. It trades away S-Log3's extra dynamic range headroom for speed: footage that's usable in a rough cut or even a final delivery with minimal color work.

S-Log3 needs the Color Space Transform setup covered throughout this guide before it looks like a finished image at all, but it holds onto meaningfully more shadow and highlight detail for a colorist to work with later. For a run-and-gun shoot with no time in the color suite afterward, S-Cinetone is the more practical choice. For anything getting a real grade, especially footage that needs to match against other log-shot cameras, S-Log3's extra latitude is worth the setup cost.

Choosing between S-Cinetone and S-Log3 on the A7 IV is a choice between speed and latitude, not a choice between a lesser option and a better one. Know which one your project actually needs before you set your Picture Profile menu, since switching mid-shoot means intercutting two fundamentally different color pipelines in the same edit.

Why does HDMI-recorded S-Log3 footage sometimes look different from internal recording?

This is the gotcha most tutorials skip, and it has nothing to do with your Color Space Transform math being wrong.

The HDMI standard itself doesn't carry an arbitrary camera-specific color gamut tag. It only formally supports a small set of defined color primaries, effectively Rec.709 or Rec.2020, regardless of what the camera sending the signal is actually recording internally. Rodrigo Polo, who publishes detailed camera-to-recorder setup guides for both Canon and Sony bodies, put the underlying constraint plainly in his most recent Atomos Ninja setup reference for both brands: "the limitations of the HDMI standard, which doesn't support CinemaGamut at all, just Rec/BT.709 and Rec/BT.2020," he wrote, describing exactly the kind of gamut-versus-HDMI-tag mismatch that also applies to Sony's wider gamuts when a camera sends S-Log3 out over standard HDMI video, in his December 2025 setup guide covering both Canon and Sony HDMI workflows.

That means an external recorder, an Atomos Ninja V or similar, receiving your A7 IV's S-Log3 signal over HDMI may log the resulting file with a Rec.2020 tag in its metadata rather than an S-Gamut3.Cine one, even though the underlying image data came from the exact same sensor and Picture Profile as your internally recorded clips. Apply your standard S-Gamut3.Cine Input Color Space to that externally recorded file anyway, and you're feeding the Color Space Transform a tag that doesn't match what the recorder actually wrote, which produces a transform that's mathematically valid but built on the wrong starting assumption.

This mismatch is one of the recurring questions in our 100,000+ member video-editing community: two clips of the same subject, one recorded internally, one recorded seconds later on an external monitor, that come out of the identical Color Space Transform node looking different. Polo's broader guidance on matching camera output settings to recorder settings applies directly here: "If your camera settings match the Atomos Ninja settings, you'll always get the best quality and accurate colors," a principle written about Canon's C-Log 3 output in the same guide but equally true for Sony's S-Log3 signal reaching the same recorder.

An externally recorded S-Log3 clip needs its Color Space Transform's Input Color Space checked against what your recorder actually tagged the file, not assumed to match your internal-recording settings by default. Miss this one check and internal and external footage of the same scene, shot seconds apart, will grade to visibly different color no matter how carefully you match everything else.

What about 16-bit RAW output over HDMI, does that need different settings?

Some Sony bodies can send 16-bit RAW video over HDMI to a compatible external recorder for capture as ProRes RAW, and if you're working with that kind of file, it's a genuinely different pipeline from the standard S-Log3 workflow this guide covers.

Sony's own help documentation for RAW-capable HDMI output states plainly that "the gamma is locked to S-Log3 during RAW output," meaning the camera doesn't let you swap gamma curves once you've switched into RAW HDMI mode, per Sony's official help guide covering RAW movie HDMI output settings. That RAW signal gets decoded and debayered by Resolve's Camera RAW palette rather than handled through a standard Color Space Transform node, closer in spirit to how Blackmagic RAW or Canon's internal RAW footage gets processed than to the two-node CST setup covered throughout this guide.

Before assuming your A7 IV footage is in this category, confirm your specific camera actually supports RAW HDMI output at all and that you deliberately enabled it; not every Sony body in the a7 lineup ships with that capability, and it isn't the default HDMI mode. If your external recorder captured a standard 10-bit 4:2:2 file rather than a RAW one, you're in the standard S-Log3 workflow covered earlier in this guide, not the RAW path, and the HDMI gamut-tagging gotcha in the previous section is the one that applies to your footage.

RAW HDMI output and standard S-Log3 HDMI output are two different pipelines that happen to travel over the same cable, and confirming which one you actually recorded matters before you troubleshoot either the color or the decode. If you're not certain which mode your recorder captured, check the file's own metadata or your recorder's log from the shoot day rather than guessing from memory.

Does noise get worse at higher ISO, and how do you fix it in Resolve?

Every stop of ISO you add above the A7 IV's S-Log3 base points buys you correct exposure at the cost of more visible noise once you stretch that flat Log image out into a normal-contrast grade, and the Color Space Transform itself does nothing to reduce it.

DaVinci Resolve's Noise Reduction tools, both Temporal and the DaVinci Neural Engine-driven Spatial and UltraNR modes, are Studio-exclusive. Blackmagic's own Studio product page lists temporal and AI spatial noise reduction among the features that separate Studio from the free version, alongside the wider Neural Engine feature set. If you're already on Studio for other reasons, you already have access to these tools; if you're not, denoising a noisy high-ISO S-Log3 clip inside Resolve itself isn't something the free version offers.

Node placement matters more than which specific noise reduction mode you pick. Apply Noise Reduction on a node before your Color Space Transform converts the clip out of Log, while the image is still flat and the noise pattern is closer to what the sensor actually recorded, rather than after you've already pushed contrast and saturation back in through the grade. Denoising after a heavy grade means fighting noise that's already been amplified by every downstream contrast and saturation move, asking far more of the same tool for a worse result.

Our dedicated guide to DaVinci Resolve's video noise reduction settings covers the specific Temporal, Spatial, and UltraNR parameters, motion estimation range, and the tradeoffs between denoising strength and softened detail in more depth than fits here.

S-Log3's noise floor on the A7 IV is a shooting-day problem first and a Resolve problem second. Staying near ISO 800 or jumping cleanly to ISO 3200, rather than sitting somewhere in between just because the dynamic range technically allows it, keeps you out of the noise reduction workflow altogether on most shoots.

Why won't some Sony A7 IV clips import into DaVinci Resolve smoothly at all?

If your S-Log3 clip stutters on playback or won't decode fast enough to scrub, that's a different failure mode from a wrong-looking grade, and it usually traces back to the codec, not the color space.

The A7 IV records its 10-bit 4:2:2 S-Log3 footage in XAVC S-I, XAVC HS, or standard XAVC S depending on your codec setting, with a maximum bitrate up to 600 Mbps, per CineD's coverage of the camera's video specifications at launch. XAVC HS is Sony's H.265 long-GOP option specifically, which trades a smaller file size for a heavier decode cost, and Resolve's free version has real limits decoding H.265 on some hardware and OS combinations. Puget Systems' own breakdown of Resolve's decoding support notes that "the Studio version of DaVinci Resolve has long been able to utilize hardware decoding of H.264 and H.265 (HEVC) media," which means Windows users specifically on the free version lean harder on the CPU for the exact codec the A7 IV's XAVC HS mode produces, confirmed directly in Puget Systems' hardware decoding analysis.

Our related guide on why Sony A7S III XAVC S footage won't play smoothly in DaVinci Resolve covers this exact decode bottleneck in more depth, and the underlying cause is the same across Sony's current mirrorless lineup: 10-bit 4:2:2 long-GOP footage is genuinely expensive to decode in real time, regardless of which specific Sony body recorded it.

If a clip won't come online at all rather than just stuttering, confirm you're running a Resolve build that supports your specific XAVC variant, and on Windows, that any required Microsoft HEVC decoding component is installed at the OS level, since Windows doesn't ship H.265 decoding natively the way recent macOS versions do.

A Sony A7 IV clip that stutters or won't decode isn't a color science problem and no Color Space Transform setting fixes it, it's a codec decode cost specific to the file's compression, not its color space. Confirm which XAVC variant and bitrate you're running before you spend time troubleshooting a Color Space Transform on a clip that hasn't actually decoded smoothly yet.

Do you need proxies to edit A7 IV S-Log3 footage smoothly?

Often, yes, and the reason is the same long-GOP decode cost covered above, not the color space or resolution alone.

DaVinci Resolve gives you two related tools for this, Proxy Media and Optimized Media. Right-click a clip or a bin in the Media Pool and choose Generate Optimized Media to have Resolve transcode a full local copy in the background at a resolution and codec you set in Project Settings, Master Settings. On a Mac, ProRes, typically ProRes 422 or ProRes 422 LT, is the standard proxy codec; on Windows, DNxHR fills the same role. Our proxy media setup guide for a slow laptop walks through the exact Project Settings panel and a decision tree for which resolution tier fits your specific hardware.

Proxies fix playback performance, not color. Building optimized media from an A7 IV clip doesn't change or skip the Color Space Transform step covered earlier in this guide; Resolve automatically relinks to your full-resolution originals for the final render regardless of what you cut with, so your S-Gamut3.Cine input tagging still applies exactly the same way it would without proxies in the pipeline.

Do you need DaVinci Resolve Studio for any of this?

No, not for the core S-Log3 workflow this page covers. The Color Space Transform effect and Resolve Color Management's automatic tagging both work in the free version of DaVinci Resolve, with no functional restriction on the color math itself.

Per Blackmagic's own free version product page, the free tier covers professional color grading tools without a Studio license. Where Studio genuinely enters the picture is a delivery target that needs Dolby Vision metadata authoring or HDR10+ analysis and export, both listed on Blackmagic's Studio product page as Studio-exclusive; workflows that lean on Studio-only Noise Reduction tools for a noisy high-ISO clip, covered above; or hardware-accelerated H.265 decoding on Windows for the A7 IV's XAVC HS footage specifically, also covered above.

Getting Sony A7 IV S-Log3 footage to grade correctly is a color management problem, and color management is not a feature Blackmagic gates behind the Studio license. Don't let a general free-versus-Studio comparison talk you into buying software just to make your A7 IV footage look right, unless you've actually hit one of the specific decode or noise reduction walls above.

How do you deliver both SDR and HDR from the same S-Log3 grade?

Most A7 IV projects only need one deliverable, but the moment a client asks for both a Rec.709 web version and an HDR10 or Dolby Vision master from the same shoot, you're choosing between regrading from scratch and branching off the grade you already built.

The node structure covered throughout this guide makes branching straightforward, because the S-Log3 conversion and your creative grade both happen before the final output-facing Color Space Transform node, not inside it. The input Color Space Transform, optional Noise Reduction, primary correction, and creative grade all operate in DaVinci Wide Gamut and don't reference an SDR or HDR target at all. Only the last node, the output Color Space Transform, cares what you're delivering to.

The practical approach is to duplicate the timeline, right-click it in the Media Pool or Edit page and choose Duplicate Timeline, so you have two timelines sharing the same clips and the same grade up through your creative-grade node. On one timeline's output Color Space Transform, set Output Color Space to Rec.709 and Output Gamma to Rec.709 or Rec.709-A for your SDR delivery. On the other, set Output Color Space to Rec.2100 and Output Gamma to ST 2084 (PQ) for HDR10 or Dolby Vision, or HLG if that's your target instead. The shared base grade means a change to your primary correction or creative look on one timeline doesn't automatically propagate to the other, so treat the duplication point as the moment your two deliverables start diverging, and make base-grade fixes before you duplicate rather than after.

One setting worth knowing about on that final Color Space Transform node: a Tone Mapping menu that controls how highlights that fall outside your output's displayable range get compressed rather than hard-clipped. The manual describes several methods, including a "Simple" curve that "compress[es] or expand[s] the highlights and/or shadows of the timeline dynamic range to better fit the output dynamic range," a "DaVinci" method with "a smooth luminance roll-off in the shadows and highlights, and controlled desaturation of image values in the very brightest and darkest parts of the image," and a "Saturation Preserving" option built for grades that push color harder without the extra desaturation the DaVinci method applies, as documented in Blackmagic's own Color Space Transform Tone Mapping reference. This matters more on the HDR-to-SDR direction, where you're deliberately narrowing dynamic range, than on a straightforward S-Log3-to-Rec.709 delivery with no HDR intermediate step, but it's the control to reach for if an HDR-derived SDR version clips highlights that looked fine in the HDR grade.

Branching an SDR and an HDR deliverable from the same S-Log3 grade means duplicating the timeline after your creative grade and changing only the final Color Space Transform's output settings, not rebuilding the grade twice. Keep the branch point late, right before the output node, so a fix to your base grade only has to happen once and gets duplicated forward rather than needing to be repeated on both versions by hand.

Is there an ACES workflow for Sony A7 IV S-Log3 footage in DaVinci Resolve?

Yes, though it takes more setup than the DaVinci Wide Gamut path this guide is built around, and it's worth it mainly if you're already delivering through an ACES pipeline for other reasons.

Blackmagic Design is an official member of the Academy Color Encoding System project, and DaVinci Resolve supports it as a full alternative to DaVinci YRGB Color Managed. Switch Color Science in Project Settings to ACEScct or ACEScc, and Resolve treats your working space, scopes, and grading tools according to the ACES standard end to end. Sony's mirrorless and Cinema Line cameras have reasonably solid first-party ACES Input Device Transform coverage compared to some hybrid competitors, since Sony's own S-Gamut3.Cine and S-Log3 combination is a documented, published input transform in most current ACES-compatible software, including Resolve.

ACES is worth setting up for A7 IV footage when you're intercutting with true Cinema Line or other ACES-native cameras on the same project, or when your delivery pipeline downstream already expects ACES natively. For a single-camera A7 IV project heading to a standard Rec.709 or HDR10 delivery, the DaVinci Wide Gamut intermediate covered throughout this guide gets you there with far less setup.

Does this guide still apply now that the Sony A7 V exists?

Yes, entirely. Sony announced the A7 V in December 2025, four years after the A7 IV's original release, bringing a partially-stacked 33MP sensor and faster readout, but the A7 IV's S-Log3 color science, S-Gamut3.Cine and the S-Log3 gamma curve, is unchanged between the two cameras, per Newsshooter's coverage of the A7 V's announcement.

The A7 IV remains one of the most widely owned hybrid cameras on the market, with a huge installed base of working bodies that didn't disappear the moment a newer model shipped. Every Color Space Transform setting in this guide, Sony S-Gamut3.Cine input, S-Log3 gamma, DaVinci Wide Gamut intermediate, Rec.709 output, applies identically whether your A7 IV shipped in 2021 or you bought one secondhand last month. If you're deciding whether to upgrade to an A7 V specifically for color reasons, don't; the sensor and readout speed improvements target rolling shutter and autofocus performance, not the underlying log color pipeline this guide walks through.

A camera generation shipping newer doesn't change the color science of the camera you already own, and every setting in this guide still applies to A7 IV footage exactly as written regardless of what Sony announces next. If you're shopping used or budget-conscious, an A7 IV with a correct Color Space Transform setup produces a grade that's indistinguishable, on the color side specifically, from footage shot on Sony's newest body.

A step-by-step example: taking one S-Log3 clip from flat to Rec.709

Here's the full sequence in order, from a fresh A7 IV clip in the Media Pool to a delivered Rec.709 grade, with every step from earlier in this guide placed where it actually happens in a real node tree.

1. Confirm the source. Right-click the clip, check Clip Attributes, and confirm it's S-Log3 with S-Gamut3.Cine, shot near ISO 800 or ISO 3200, and note whether it was recorded internally or over HDMI.
2. Build optimized media if the clip is stuttering on scrub. If it's a 10-bit 4:2:2 XAVC HS file playing back roughly, generate optimized media at Half or Quarter Resolution before you touch color, so you're not fighting playback performance and grading decisions in the same pass.
3. Node 1, Color Space Transform in. Set Input Color Space to Sony S-Gamut3.Cine (or the color space your HDMI recorder actually tagged, if this clip was recorded externally), Input Gamma to S-Log3, Output Color Space to DaVinci Wide Gamut, Output Gamma to DaVinci Intermediate.
4. Node 2, Noise Reduction, if the shot needs it. If the clip was shot at a high ISO and shows visible grain once it's out of Log, add a Temporal or Spatial Noise Reduction node here, immediately after the Color Space Transform, before any contrast or saturation moves.
5. Node 3, primary correction. With the clip sitting in DaVinci Wide Gamut, set your white balance using an eyedropper on a neutral reference in frame if you have one, then bring your black point and white point in toward the edges of your waveform using the Lift and Gain wheels, watching for clipping on the scopes rather than by eye alone.
6. Node 4, creative grade. Do your actual look here: contrast shaping, color balance between shadows and highlights, any secondary qualifiers or power windows the shot needs. Nothing about S-Log3 changes how you grade once you're in a normal working space.
7. Node 5, Color Space Transform out. Input Color Space DaVinci Wide Gamut, Input Gamma DaVinci Intermediate, Output Color Space Rec.709, Output Gamma Rec.709 or Rec.709-A. If this project also needs an HDR deliverable, duplicate the timeline here and swap this node's output settings on the copy instead of regrading.
8. Check the result against the troubleshooting table below before you call the grade final, particularly if this A7 IV clip is intercut with footage from a different camera or a different recording method.

Five nodes handle the entire mechanism from flat Log source to finished Rec.709 delivery, with Noise Reduction as the one optional insertion depending on how the clip was shot. A common mistake worth naming directly: adding a third or fourth Color Space Transform "just to see" what a different combination looks like, then forgetting to remove it. Two conversions per clip, one in and one out, is correct.

Why does S-Log3 footage still look wrong after you've applied the Color Space Transform?

If you've followed the settings above and it's still off, work through these in order before assuming your footage is somehow bad.

First, the S-Gamut3 versus S-Gamut3.Cine mixup covered earlier. Confirm your Color Space Transform's Input Color Space dropdown actually says S-Gamut3.Cine, not the wider S-Gamut3, since the two produce noticeably different results from the same source file and Resolve's dropdown lists both.

Second, the HDMI mismatch covered earlier. Confirm you're not applying S-Gamut3.Cine to a clip that your external recorder actually tagged Rec.2020, or the reverse.

Third, log-on-log. If a clip looks oversaturated, hue-shifted, or has crushed color that doesn't respond normally to your color wheels, check whether a LUT is stacked on top of a Color Space Transform doing the same conversion, or whether Resolve Color Management is set to automatic tagging while a manual node is also applying its own transform to the same clip.

Fourth, timeline color space mismatch. If your project's overall Color Management is set to a working space your output node doesn't actually match, Rec.709 versus Rec.2100 being the most common version of this mistake, footage can look correct in isolation and wrong the moment it's viewed against your monitoring setup or exported.

Fifth, and easy to miss because the symptom looks like a color problem: check whether the clip actually decoded at full quality, or whether you're grading a low-resolution proxy that never got relinked to full-resolution media before export.

When the menus alone don't get you there fast enough

Everything in this reference is a settings problem with a settings answer, but finding the right menu on a deadline is its own kind of friction, especially the first few times you're bouncing between Project Settings, the node graph, and Clip Attributes trying to confirm exactly what a clip is before you touch its color.

TryUncle is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words, and Uncle points at the exact control on your screen. If you're on a Mac asking "why does my S-Log3 footage look grey" out loud at your screen, that's a faster route to the Color Space Transform panel than searching this page a second time mid-session. It's a paid app, currently in founder pricing, and macOS only, so it won't help a Windows editor working through Resolve's menus. Check TryUncle for current pricing before deciding if it fits your workflow.

It's worth knowing the category has other tools built on a different premise. Sottocut, PremiereCopilot, heyeddie.ai, and cutagent.ai automate parts of an edit or answer chat questions about your footage, rather than watching your live screen and pointing at controls. If your goal is automating a cut, those solve a different problem. If your goal is finding the right Color Space Transform setting faster while you're mid-grade, on-screen guidance is the more direct tool for that specific job.

What's the full settings cheat sheet at a glance?

Before the table, here's the one-line version of everything above. Use Resolve Color Management if your project is entirely A7 IV footage shot the same way. Switch to a manual Color Space Transform node the moment you're mixing internal and HDMI-recorded clips, or mixing cameras. Stay at ISO 800 or jump cleanly to ISO 3200 rather than sitting in between, lock your white balance instead of trusting auto, and set Gamma Disp. Assist Type so what you're seeing on set actually matches what you shot. And if a clip stutters or won't decode at all, that's a codec problem, not a color space problem, and belongs in the import-performance section above, not in your node tree.

Match S-Gamut3.Cine and S-Log3 on your first Color Space Transform, keep your exposure near ISO 800 or ISO 3200 even when S&Q slow motion tempts you to push higher, lock your white balance instead of trusting auto, confirm your HDMI recorder's actual color tag before trusting your internal-recording settings on an externally captured clip, and the rest of this workflow is two nodes doing exactly what they're built to do. Most A7 IV footage that "looks wrong" in Resolve isn't broken. It's one dropdown, one habit from the shoot day, or one mismatched HDMI tag, away from correct, and now you know which one.