Sony FX3 S-Log3 DaVinci Resolve Import Settings, Explained

Flexible ISO, Cine EI Quick, or Cine EI, which log shooting mode should you use on the FX3?

Flexible ISO fits solo hybrid shooting where you want ISO to behave like a normal dial; Cine EI and Cine EI Quick fit a multi-camera or scripted production where a locked, known noise floor across every camera on set matters more than convenience.

Sony's own Log Shooting Setting page defines all three plainly. Flexible ISO is "a shooting mode that allows you to record S-Log material by adjusting the exposure settings including ISO sensitivity according to the shooting scene," which gives you direct, per-scene control over both exposure and sensitivity the way you'd adjust ISO on any other camera. Cine EI locks the sensor to one of the two Base ISO values covered above and instead lets you dial in an Exposure Index, described as "a shooting mode that allows you to shoot with two Base ISO settings that can express clear images with the maximum dynamic range and suppressed noise." Cine EI Quick works the same way but automates the base switch: "the Base ISO switches automatically according to the adjusted EI value," per the ILME-FX3's own Log Shooting Setting documentation.

The practical difference shows up on set, not in the Color Space Transform. Flexible ISO is the mode most solo FX3 owners default to, since it behaves the way they're already used to from stills cameras and doesn't require understanding EI at all. Cine EI and Cine EI Quick exist for productions where multiple FX3, FX6, or FX9 bodies need to sit at an identical, predictable noise floor, and where a DIT or colorist downstream is deliberately rating exposure differently from the recorded signal for creative or safety reasons.

None of the three modes change your Color Space Transform's Input Color Space or Input Gamma values. S-Gamut3.Cine and S-Log3 stay exactly the same regardless of which log shooting mode produced the file. What changes between Flexible ISO and Cine EI is how the camera lets you set exposure on the day, not what Resolve needs to see when you convert the footage afterward. If you're not sure which mode a clip was shot in, check your shoot notes before assuming the color conversion needs to differ, because it won't.

What EI value should you dial in for S-Log3 on the FX3?

Match your EI to your actual Base ISO by default, and only rate it lower when you deliberately want to overexpose the recorded signal for extra shadow protection at the cost of highlight headroom.

Exposure Index doesn't work like a normal ISO setting. Sony's own documentation defines it as a value that "is reflected on the monitor when Display LUT is set to On," and the available range depends on which Base ISO you've locked. At Base ISO 800, EI can run from 200 to 3200. At Base ISO 12800, EI runs from 3200 to 51200, per the ILME-FX3's Exposure Index help page. In Cine EI and Cine EI Quick modes, that EI value changes how bright the monitor and preview show the image, letting you evaluate a post-production exposure decision live on set, while the sensor itself keeps recording at the fixed Base ISO regardless of what EI you've dialed in.

That decoupling is the entire point of Cine EI, and it's also the thing that trips up shooters coming from a Flexible ISO or stills-camera background. Rating your EI below your Base ISO, say EI 400 while your Base ISO sits at 800, tells the monitor to preview the image as if it were brighter, which means you're actually recording a darker signal than what you see, then pulling it back up in the grade. That protects highlights, since less of the true dynamic range gets pushed toward clipping, at the cost of shadow noise once you brighten the file back up in Resolve. Rating EI above your Base ISO does the opposite: you're recording a brighter signal than the monitor shows, protecting shadows at the cost of highlight headroom.

For most FX3 work, the practical default is rating EI equal to your Base ISO, which is functionally the same exposure behavior as Flexible ISO at that same ISO value. Reach for a different EI only when you have a specific reason: a scene with blown-out windows you need to protect, or a low-light interior where shadow detail matters more than a clean highlight rolloff.

Exposure Index changes what you see on the monitor while shooting Cine EI, never what value your Color Space Transform's Input Color Space or Input Gamma should be set to in Resolve. S-Gamut3.Cine and S-Log3 apply the same way to a clip shot at EI 400 as one shot at EI 3200; the EI value is metadata about your exposure decision, not a different color space.

How do you judge exposure on the FX3 with zebras, since the LCD looks flat and grey?

Zebras tied to specific brightness percentages give you a repeatable, numeric exposure reference on a camera whose S-Log3 preview looks intentionally low-contrast by design.

Cinematographer and DIT Alister Chapman, who has written extensively about Sony's log workflow across the Cinema Line, is direct about which tool he reaches for on this specific camera: "With the FX3 and a7S III, zebras are in my opinion the best way to check your S-Log3 exposure levels," he writes in his guide to correctly exposing S-Log3 across the a7S III, FX3, FX6, and FX9. His recommended zebra values give you a specific number to chase rather than judging a flat image by eye: 61% for a white card, 41% for a grey card, and 52% for skin tones, with the zebra range narrowed to plus or minus 2 percent so the pattern only appears over a tight band around your target value.

That numeric approach matters more on the FX3 than it does on a normally-graded picture profile, because a flat S-Log3 image compresses the visual difference between correct exposure and a stop under or over into something genuinely hard to see on a small monitor or EVF. Chapman's zebra method sidesteps that entirely: point the zebra pattern at a known reference in frame, chase the target percentage, and you have a repeatable exposure check that doesn't depend on how flat or contrasty the preview happens to look that day.

Sony's own Gamma Display Assist feature, available on FX3 firmware that supports it, offers a second, complementary check: a normal-contrast preview overlay on the monitor and EVF only, without touching the recorded file. It's a useful sanity check alongside zebras, but it's a visual approximation, not a number. Zebras give you a percentage you can write down and repeat across a whole shoot day; a display assist preview only gives you an impression. On a scene where lighting changes between setups, having an actual number to re-check against saves you from exposure drift that a flat preview alone would hide.

Resolve Color Management or a manual Color Space Transform node, which one fits an FX3 project?

Both reach the same result. Which one to use depends on how much of your project is FX3 footage shot the same way versus a mix of cameras, log formats, or recording modes.

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 FX3 footage shot under one consistent Log Shooting mode, since you tag the camera's color space once and let Resolve handle every clip the same way.

A manual Color Space Transform node gives you more control per clip or per group, which matters the moment your project mixes FX3 footage shot in Flexible ISO with a second camera, a different EI setting, or externally recorded RAW. You can normalize each source 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 FX3-only.

To set up Resolve Color Management on an FX3 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 FX3 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.

Why does the FX3 give two gamut options, S-Gamut3 and S-Gamut3.Cine?

S-Gamut3.Cine is the narrower of Sony's two log gamuts, deliberately scaled to stay closer to what a standard Rec.709 or DCI-P3 delivery can actually reproduce, while plain S-Gamut3 covers a wider theoretical color space built for a heavier VFX or digital cinema pipeline.

Most Sony LUTs, including nearly every third-party S-Log3 pack sold for the Cinema Line and the free technical LUTs Sony itself publishes, are built for S-Gamut3.Cine specifically, not the wider S-Gamut3. Picking the wrong one in your Color Space Transform's Input Color Space dropdown produces a conversion that's mathematically valid but tuned for the wrong starting gamut, which shows up as a result that's close but visibly off, usually first in skin tones and highlight rolloff.

The practical rule is simple: if you shot S-Log3 on an FX3 and didn't deliberately change the color mode away from the default, you shot S-Gamut3.Cine. Sony's default Picture Profile presets for S-Log3 on this camera pair the gamma with S-Gamut3.Cine specifically, which is the gamut this entire guide's settings are built around. Choosing S-Gamut3.Cine over S-Gamut3 as your Color Space Transform input is not a stylistic preference, it's matching the actual gamut your camera recorded, and getting it backward produces a transform that looks almost right, which is harder to catch than one that looks obviously wrong.

Does auto white balance work for S-Log3 on the FX3, or should you lock it manually?

Auto white balance isn't wrong on S-Log3 the way an incorrect gamut or gamma setting is wrong. It's 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. 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 bigger issue on the FX3 than on a normally-graded picture profile, because the low-contrast image already makes small color shifts harder to spot by eye, and 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. This matters more on the FX3 specifically when you're running Cine EI across multiple cameras, since a mismatched white balance between two bodies pointed at the same scene turns a color-matching problem into a two-step fix instead of a single node adjustment.

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.

Why do some FX3 clips stutter or refuse to decode smoothly in DaVinci Resolve?

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 FX3 records its 10-bit 4:2:2 S-Log3 footage in XAVC S-I, XAVC S, or XAVC HS depending on your codec setting. XAVC S-I is an intraframe codec running from 200 up to 600 Mbps at frame rates up to 59.94p, XAVC HS is Sony's H.265 long-GOP option covering higher frame rates up to 119.88p at a smaller file size, and the camera also offers an 8-bit 4:2:0 XAVC-L proxy format at 16 Mbps purely for a lightweight monitoring copy, according to cinematographer analysis of the FX3's data rate table. XAVC HS specifically 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 FX3's XAVC HS mode produces, confirmed directly in Puget Systems' hardware decoding analysis.

Because the FX3 and the Sony A7S III share the same 12.1-megapixel sensor and the same XAVC codec family, they hit this exact decode bottleneck in nearly identical ways. Our dedicated guide on why Sony A7S III XAVC S footage won't play smoothly in DaVinci Resolve walks through the codec-by-codec breakdown, hardware decode requirements, and the fix in full detail. Everything in that guide applies to FX3 files shot in the same codec modes; the underlying cause, 10-bit 4:2:2 long-GOP or All-Intra footage being genuinely expensive to decode in real time, doesn't change based on which of the two camera bodies recorded it.

An FX3 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.

Does the FX3's built-in proxy recording help, or do you still need Resolve's own proxies?

The FX3's in-camera proxy recording gives you a small monitoring file for review on other devices; it doesn't replace the editing-performance proxies you generate inside Resolve.

Sony's own Proxy Settings documentation confirms the camera "allows you to select whether to simultaneously record proxy movies" alongside your main recording, choosing a format of "XAVC HS HD or XAVC S HD" at a bit rate of "16M 4:2:0 10bit, 9M 4:2:0 10bit, or 6M 4:2:0 8bit," per the ILME-FX3's Proxy Settings help page. That's a genuinely small file, built for quick review on a phone or a producer's laptop, not for grading. Proxy movies recorded this way can't even be played back on the camera itself, and deleting or protecting the original also deletes or protects the linked proxy, since the two are tied together as a pair rather than being independent files.

DaVinci Resolve's own proxy tools, Optimized Media and Proxy Media, solve a different problem: giving your editing system a lighter file to scrub and cut against while keeping your full-resolution original available for the final render. 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 FX3 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.

Does 16-bit RAW over HDMI change your Color Space Transform settings?

Yes, and it's a genuinely different pipeline from the standard S-Log3 workflow this guide covers, so confirming which one you actually recorded matters before you troubleshoot either the color or the decode.

The FX3 can output 16-bit RAW video over HDMI to a compatible external recorder, most commonly an Atomos Ninja V or V+, for capture as ProRes RAW. 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 gets processed than to the two-node CST setup covered throughout this guide.

Getting that pairing right depends on matching your camera's output settings to your recorder's input settings exactly. Rodrigo Polo, who publishes detailed camera-to-recorder setup guides for both Canon and Sony bodies, is direct about the underlying HDMI constraint that applies here too: "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 can affect a standard 10-bit 4:2:2 HDMI feed even when the underlying sensor data is genuinely S-Gamut3.Cine, in his December 2025 setup guide covering both Canon and Sony HDMI workflows. Polo's broader guidance applies directly here too: "If your camera settings match the Atomos Ninja settings, you'll always get the best quality and accurate colors," a principle written across his Canon and Sony coverage but equally true whichever brand's recorder is capturing your FX3's HDMI output.

Before assuming your FX3 footage is in this RAW category, confirm you deliberately enabled RAW HDMI output and that your specific recorder captured it as RAW rather than a standard 10-bit 4:2:2 video feed; the default HDMI mode on the FX3 is standard video, not RAW. If your external recorder captured a standard 10-bit file, you're in the two-node CST workflow covered throughout this guide, and Rodrigo Polo's warning about HDMI gamut tags is the one that applies: confirm your recorder's actual output tag before assuming your internal-recording S-Gamut3.Cine settings apply unchanged to the same clip captured externally.

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 ISO 12800, and how do you fix it in Resolve?

Every stop of ISO you add above the FX3'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. If you're already on Studio for other reasons, you already have access to these tools; if you're not, denoising a noisy ISO 12800 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.

The FX3's second base of ISO 12800 genuinely is a clean point relative to the ISO values around it, which is the entire reason it exists as a selectable base rather than just being the top of a continuous range. Footage shot at ISO 12800 will still show noticeably more grain than footage shot at ISO 800, since noise increases with sensitivity regardless of where the sensor's gain circuit resets, but it will look meaningfully cleaner than footage shot at, say, ISO 8000, sitting in the noisy middle ground between the two bases. 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.

The FX3's noise floor is a shooting-day problem first and a Resolve problem second. Staying near ISO 800 or jumping cleanly to ISO 12800, 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.

Is S-Cinetone better than S-Log3 for the FX3?

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, built to match the look of the company's flagship VENICE cinema camera straight out of the box, designed to look natural and correctly saturated 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, which is exactly why so many run-and-gun FX3 owners default to it for social or documentary work with a fast turnaround.

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 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 Cinema Line cameras like the FX6 or FX9, S-Log3's extra latitude is worth the setup cost.

Choosing between S-Cinetone and S-Log3 on the FX3 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.

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

Most FX3 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.

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," and 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," 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. If your CST is quietly pulling saturation out of highlights or shadows when you didn't expect it, our guide to Color Space Transform desaturation walks through the exact Tone Mapping and Gamut Mapping settings responsible, and how to fix each one.

Branching an SDR and an HDR deliverable from the same FX3 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 FX3 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 or intercutting with other Cinema Line cameras natively.

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 Cinema Line has solid first-party ACES Input Device Transform coverage, since the FX3's 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 FX3 footage when you're intercutting with true Cinema Line cameras like the FX6 or FX9, or when your delivery pipeline downstream already expects ACES natively. For a single-camera FX3 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 FX3A exists, and what about the rumored FX3 II?

Yes, entirely, to both questions in slightly different ways.

Sony quietly released a revised model in May 2025, without a formal press release, distinguishing it in retail listings under the model number ILME-FX3A. According to Sony's own statement, the revision consists of exactly three hardware changes: an "LCD panel resolution change to 2,359,296 dots from 1,440,000 dots," the removal of NFC functionality, and the removal of "the infrared remote control light receiving element," made because the original LCD panel became unavailable to source, per CineD's coverage of the quiet FX3A release. The revision retains the FX3 name in Sony's marketing. Nothing about the sensor, S-Log3, S-Gamut3.Cine, the Base ISO values, or the XAVC codec options changed between the two. Every setting in this guide applies identically whether your camera shipped as an original FX3 or an FX3A.

A genuinely next-generation FX3 II is a different matter, and as of August 2026 it remains unannounced, with industry reporting describing it only as an expected camera rather than a confirmed one. If Sony does ship a new sensor generation with different base ISO points or a new gamut, treat that the same way this guide treats an FX3A: check the specific camera's own Sony help guide for its Base ISO and Picture Profile pages before assuming these exact numbers, 800 and 12800, carry over. The Color Space Transform mechanism itself, two nodes converting a Sony log gamut into DaVinci Wide Gamut and back out, will still apply; only the specific ISO and gamut values might need updating for a genuinely new sensor.

A minor hardware revision doesn't change the color science of the camera you already own, and every Color Space Transform setting in this guide applies to FX3A footage exactly as written. If you're shopping used or budget-conscious between an original FX3 and an FX3A, the color pipeline is identical either way; the LCD resolution difference is the only thing that should factor into that decision.

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 ISO 12800 clip, covered above; or hardware-accelerated H.265 decoding on Windows for the FX3's XAVC HS footage specifically, also covered above.

Getting Sony FX3 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 FX3 footage look right, unless you've actually hit one of the specific decode or noise reduction walls above.

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

Here's the full sequence in order, from a fresh FX3 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. Check your shoot notes or the clip's metadata for the Log Shooting mode, Base ISO, and EI value it was recorded at, and note whether it was recorded internally or over HDMI as RAW or standard video.
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 as standard video, not RAW), 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 near or above ISO 12800 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 FX3 clip is intercut with footage from a different camera or a different Log Shooting mode.

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, an EI mismatch specific to Cine EI shooting. If a clip was shot with an EI value significantly different from its Base ISO, the recorded signal is intentionally darker or brighter than a normal exposure, which can look like an exposure error in the grade if you're not aware the clip was rated that way on set. Check your shoot notes before assuming a dark or bright clip is simply a mistake.

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 FX3 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 FX3 footage shot the same way. Switch to a manual Color Space Transform node the moment you're mixing internal, HDMI, and RAW-recorded clips, or mixing cameras. Stay at ISO 800 or jump cleanly to ISO 12800 rather than sitting in between, choose Flexible ISO for solo work and Cine EI for a multi-camera set, and match your EI to your Base ISO unless you have a specific reason to rate it differently. 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 12800 even when a low-light EI temptation pushes you higher, lock your white balance instead of trusting auto, and confirm which Log Shooting mode and EI value a clip was actually recorded at before troubleshooting a color problem that's really an exposure decision from the shoot day. Most FX3 footage that "looks wrong" in Resolve isn't broken. It's one dropdown, one shoot-day setting, or one mismatched HDMI tag, away from correct, and now you know which one.