iPhone HDR to SDR in DaVinci Resolve

To convert iPhone HDR to SDR in DaVinci Resolve, start by finding out what the phone actually recorded. Standard iPhone HDR video, Dolby Vision metadata, Rec.2100 HLG, Apple Log, Apple Log 2 and ordinary Rec.709 are different inputs, and each one needs its own treatment. Assign the matching input transform, convert once to a defined SDR output, then grade and check the rendered file in the player or platform that matters.

When a clip looks washed out, the phone usually isn’t to blame. Resolve or the playback app is reading the source with the wrong transfer function, or the project has no controlled HDR-to-SDR mapping at all. If Apple Log looks flat before its input transform, that’s normal. If highlights clip or colors turn electric after the conversion, look at the tone and gamut mapping before you reach for more contrast or saturation.

Identify the iPhone Recording Before You Grade

Start with how the clip was recorded. Apple documents that supported iPhones can record HDR video in Dolby Vision. On supported current Pro models, ProRes recording can also offer Log or Log 2, depending on the device and software version. Each of those labels describes a different capture and encoding path, so “shot on iPhone” doesn’t give you enough to pick a transform.

In Resolve, open the clip metadata and check its assigned color space. The useful clues are codec, bit depth, color primaries, transfer characteristic, HDR metadata and the camera setting used during capture. An HEVC file can be HDR or SDR. A ProRes file can be Log or another recording mode. Container and codec alone won’t tell you which color transform the clip needs.

If the metadata disagrees with what you remember shooting, go back to the original file and the iPhone’s recording settings. Social downloads, messaging apps and some handoff tools can strip or rewrite metadata along the way. A file that’s already been converted to SDR shouldn’t get the same transform as the untouched HDR original.

Resolve also lists Rec.2100 HLG and Rec.2100 HLG (Scene) as separate choices, and the two interpret HLG material differently. Pick the one that matches the source and your workflow, and don’t let a brighter viewer make the decision for you. When you’re unsure which interpretation is right, keep a copy of the original, note the metadata you have, and judge the transform on known scene content: skin, neutral objects and highlight rolloff.

Choose One Color-Management Route

You can run the conversion through Resolve Color Management or through a Color Space Transform node. Either one works. Trouble starts when the project applies an automatic managed transform and the node tree then adds a second CST or LUT for the same conversion.

I reach for Resolve Color Management when a timeline mixes several cameras, more than one iPhone recording mode, or HDR and SDR clips. Each source gets its own input assignment while the timeline keeps one working space and one output. A CST makes more sense when the project is otherwise unmanaged, when the conversion belongs at a specific point in the node tree, or when you want the transform settings visible right on the clip.

Our guide to Resolve Color Management and CST covers the wider decision. Here the rule is simpler: give the input-to-output transform one owner and keep its settings out in the open. Don’t stack an input LUT, automatic color management and a CST unless you can say why each one is there.

Method 1: Convert iPhone HDR With Resolve Color Management

Open Project Settings > Color Management and set up a color-managed project. For a flexible grading pipeline, DaVinci Wide Gamut / DaVinci Intermediate is a practical timeline working space. Blackmagic describes it as a wide working space intended to retain image information whether the project ends up in SDR or HDR, and the 21.1 manual recommends it for HDR output. For an SDR-only job, any working space you’re comfortable grading in is fine.

For an SDR job, set the timeline working luminance to an SDR target such as SDR 100, the conventional SDR setting with a 100-nit maximum. That menu only appears when the color management preset is set to Custom Settings. Then set the output color space for the actual delivery. Rec.709 Gamma 2.4 is a common grading and video-delivery target in a controlled viewing room. It won’t suit every web, broadcast or computer-display path, so go by the destination spec and your calibrated monitoring target.

Assign the correct Input Color Space to every source clip:

• For an HLG source, choose the Rec.2100 HLG interpretation that matches the footage and the project.
• For Apple Log, use the Apple Log input transform available in your Resolve build.
• For Apple Log 2, pick a separate Apple Log 2 input only when your installed Resolve version lists one and the clip really was recorded in Log 2. Apple documents the recording mode, but that doesn’t guarantee every current Resolve build ships a matching transform.
• For SDR Rec.709, assign the correct Rec.709 interpretation and keep those clips away from HDR input transforms.

In the Media Pool, select clips that share the same verified source, right-click them and choose the Input Color Space from the contextual menu. That’s faster and more consistent than correcting each clip by eye. Mixed folders need separate assignments. One mislabeled SDR clip in an HLG batch can come out too contrasty; one mislabeled HLG clip in an SDR batch can stay pale or clip once you start correcting it.

Custom Settings also exposes the Output DRT. Set to DaVinci, it rolls off shadows and highlights smoothly and desaturates the very brightest and darkest values in a controlled way, which is exactly what HDR highlights need when they have to fit into the SDR range. Setting the DRT to None is handy for diagnosis. As a delivery setting, though, a plain 1:1 conversion with no tone or gamut handling can clip bright detail and push saturated colors outside Rec.709.

Grade in the managed working space once the input assignment is right. Exposure, balance and creative contrast then act on a predictable image. Crush the blacks and pull gain down on a misread HLG clip, and you’ve spent your corrections compensating for a technical error before the actual grade even begins.

Method 2: Use a Color Space Transform Node

For a CST workflow, keep the project’s color-management behavior clear and place one Color Space Transform at a deliberate point in the node tree. A basic HLG-to-SDR example uses:

• Input Color Space: Rec.2020
• Input Gamma: the appropriate Rec.2100 HLG choice
• Output Color Space: Rec.709
• Output Gamma: Gamma 2.4 when that is the chosen SDR target
• Tone Mapping Method: DaVinci
• Gamut Mapping Method: Saturation Compression on the Color page CST (the Fusion version calls it Saturation Mapping), which adds Saturation Knee and Saturation Max sliders

That example only fits the named HLG source. Don’t copy its input values onto Apple Log or Apple Log 2. For Apple Log, choose the matching Apple transform in your Resolve build. For Apple Log 2, use a distinct Log 2 input only if your installed version provides one. If it doesn’t, resist swapping in HLG or the older Apple Log transform because the names look close. Check the current Blackmagic release notes or support guidance and use a color workflow whose input transform you can verify. The output can stay Rec.709 if that’s the delivery.

A sensible node order puts the technical input transform first, then balancing and creative work, with any output transform wherever the project design calls for it. In a simple CST-to-display tree, the transform can sit after scene-referred corrections so they keep more of the source range. In other trees, a group or timeline-level output transform keeps clip nodes consistent. Either way, know where the scene-to-display conversion happens and do it once.

Keep an eye on the waveform while you tune tone mapping, and keep looking at the picture too. HDR highlights squeezed into SDR still need a visual hierarchy: faces, practical lights, sky detail and specular reflections shouldn’t all pile up at the same level. Good gamut mapping tames harsh color excursions and still leaves the scene’s vivid colors alive.

Why iPhone HDR Looks Washed Out in Resolve

A washed-out image usually means HLG or another HDR transfer function is being shown as if it were ordinary SDR. Midtones land in the wrong place and the contrast relationship shifts. Fix the input interpretation and the output mapping first. An aggressive contrast curve on the first node only hides the mistake.

If the project is color managed, verify the clip’s Input Color Space and the project output. If the project is unmanaged, verify the CST inputs. If both are active, temporarily bypass the CST and confirm whether the project is already doing the conversion. The companion guide to fixing a washed-out Resolve export covers data levels, tags and player differences after the image pipeline itself is correct.

Apple Log is meant to look low-contrast before its transform. If it stays flat after the correct input transform, check that the node is enabled, that the clip really was recorded in Apple Log or Apple Log 2, and that a project-level transform isn’t being bypassed. And don’t diagnose every flat iPhone clip as HLG.

Why Highlights Clip or Color Becomes Too Strong

Clipped highlights can come from missing tone mapping, a double transform, or corrections made on the wrong side of the transform. Disable nodes one at a time. If bypassing the CST brings highlight detail back, the source assignment or mapping settings are wrong. If the detail is already gone in the source scopes before conversion, no output setting will recover information that was never recorded or didn’t survive a transcode.

Oversaturation usually shows up when wide-gamut HDR colors get pushed into Rec.709 with no gamut compression. A creative LUT built for a different input can cause it too. Reach for gamut mapping before you pull the global Saturation control down. A global cut can make skin and everyday objects dull while the few out-of-gamut colors still look wrong.

Once the technical transform is stable, use our shot-matching workflow to line up exposure and color across several iPhone clips. Match after the inputs are normalized. Otherwise you may be comparing an HLG interpretation with a transformed Log clip.

QuickTime and macOS Can Still Look Different

A correct Resolve viewer and a correct render can still look different in QuickTime Player, a browser or another app. The player, display profile, output tags, macOS color management and the room you’re watching in all change what you see. That’s why switching a gamma tag sometimes changes the look without proving the grade or transform was wrong.

Nobody can hand you one universal “Rec.709-A fix.” Decide which delivery path matters most. Render a short representative section, check it in the required player or platform, and compare it on the intended display. Confirm that the export carries the color-space and gamma metadata that path expects. Then make a deliberate call on output tags or target gamma and keep the master workflow documented.

If the video goes to several destinations, keep one managed master and make destination-specific deliverables where the requirements differ. A social platform, a broadcast handoff and a file played locally on a Mac don’t necessarily share one ideal tagging and monitoring path.

Export and Verification Checklist

1. Confirm the original recording mode: HDR/Dolby Vision, Rec.2100 HLG, Apple Log, Apple Log 2 or SDR Rec.709.
2. Check the clip metadata. HEVC, ProRes, MOV or MP4 on their own don’t tell you the color.
3. Choose Resolve Color Management or CST as the owner of the transform.
4. Assign the matching input color space and gamma to each source type.
5. Use DaVinci Wide Gamut / Intermediate or another documented working space when the project needs a scene-referred managed timeline.
6. Define the SDR output from the delivery specification; use Rec.709 Gamma 2.4 only when it matches that target.
7. Enable suitable tone mapping and gamut mapping for HDR or wide-gamut sources.
8. Check that no input LUT, CST or managed transform duplicates the conversion.
9. Balance and grade after the input is interpreted correctly. The broader DaVinci Resolve color-grading guide covers primary correction and scope use.
10. Render a representative section and then the final file.
11. Inspect highlights, skin, saturated colors, shadows and gradients on the required playback path.
12. Record the input assignment, project working space, output target, mapping method and export tags so the result can be revised without guesswork.

A dependable conversion starts from the source. Identify the iPhone recording, apply one matching input-to-SDR transform, protect highlights and wide-gamut color with deliberate mapping, then judge the exported file where people will actually watch it.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.