How Does Lightroom Classic HDR Merge Work - and When Should You Actually Use It?

By David · May 18, 2026 · 7 min read

Most tutorials about Lightroom's HDR merge tell you to select your brackets, hit Photo > Photo Merge > HDR, click Merge, and call it done. That's the mechanical steps. But they skip the part that actually explains why the result looks different - and why the sliders behave differently when you're editing it.

I work inside the Lightroom SDK, and I've dug into how Lightroom handles DNGs at a technical level. Here's the version of this guide that explains the mechanism, not just the clicks.

What Lightroom Classic Actually Creates When You Merge to HDR

The output of an HDR merge is a 32-bit floating-point linear-light DNG. That's a mouthful, but each word matters.

32-bit floating-point means the file stores pixel values as floating-point numbers, not the integer values (12-bit or 14-bit) that a camera sensor captures. Floating-point can represent a vastly wider range of values - and crucially, it has no hard upper ceiling. A standard 14-bit RAW clips at the sensor's maximum exposure. The HDR DNG just keeps going.

Linear-light means luminance values are stored proportionally to the actual light in the scene. Double the light, double the value. This is how physics works, not how display-referred images work. It's what makes HDR DNGs so well-suited to holding highlight detail that's 3, 4, or even 8 stops brighter than middle gray.

So when you move Lightroom's Exposure slider on an HDR DNG and it goes all the way to +10 instead of the usual +5 - that's not a bug or a UI curiosity. The file genuinely contains that information. The slider range is wider because there's more to reveal.

Single-RAW Recovery vs. True Bracket Merging - When Does Bracketing Actually Win?

Here's the thing most people miss: modern camera sensors are very good, and Lightroom's shadow recovery is legitimately impressive. A Sony A7R V or Nikon Z8 can pull 5+ stops of shadow detail from a single underexposed frame. So when does bracketing actually beat single-RAW recovery?

The rule I use: if the histogram on my darkest bracket still shows clipping on the right side, bracketing will help. If my single exposure holds the highlights already, merging adds file size and processing time for no real gain.

Shadows lifted from an HDR merge also stay cleaner than shadows lifted from a single underexposed bracket. When you pull shadows from a dark bracket, you're amplifying noise that was baked in at capture. When you pull them from an HDR DNG, the shadow data came from a brighter bracket where those pixels were properly exposed - so the signal-to-noise ratio is much higher from the start.

The Deghost Options Explained - What "Medium" Really Does

Deghosting exists to handle moving subjects across brackets - a person walking through a scene, leaves blowing, water moving. The algorithm works by identifying pixels that don't align between exposures and compositing those areas from a single bracket instead of blending them.

What most tutorials don't say: Lightroom anchors the deghost composite to whichever bracket you designate - and the choice matters. By default it uses the bracket closest to 0 EV (the "normal" exposure), but you can change this in the dialog by clicking the thumbnail of your preferred anchor frame.

Here's the non-obvious part: the darkest bracket is almost always the worst deghost anchor for skies, even though it has the cleanest sky tones. If there's any cloud movement between shots, ghosting artifacts will appear in the sky at full noise level from that dark exposure. Use the 0 EV bracket as your anchor in most cases, and bump deghost to Medium if you're shooting near water or vegetation.

The four deghost settings in practice:

• None: Blends all brackets equally. Use for completely static scenes (architecture, product).
• Low: Catches obvious large-movement ghosts (people walking). Good default for landscapes with minimal wind.
• Medium: Handles fast-moving elements - water, leaves, birds. Usually what I reach for.
• High: Very aggressive. Useful if there's significant motion but can degrade image quality in high-movement areas.

The "Show Deghost Overlay" checkbox highlights the pixels that got composited. Turn it on at least once per session until you trust your intuition - it's genuinely useful for learning where the algorithm is intervening.

Batch HDR Merging - Processing Multiple Sets at Once

If you shot a session with consistent bracketing (say, 3-shot AEB throughout), you can merge entire sessions in one go. Here's the workflow:

1. In Grid view, select all images you want to merge. Lightroom will automatically group consecutive frames that match your bracket count.
2. Go to Photo > Photo Merge > HDR with multiple sets selected.
3. In the dialog, check "Auto Stack Merged HDR" - this collapses each original bracket set into a stack with the merged DNG on top.
4. Check "Auto Settings" to apply a starting Develop point automatically.
5. Click Merge All.

Lightroom queues the merges and processes them in the background. For a 200-image session (roughly 67 HDR sets at 3 brackets each), budget about 20-30 minutes on a modern Mac or PC. Let it run overnight if you have a larger batch.

One catch: Lightroom needs Auto-Align to work, and that means it needs the original RAW files on disk. Smart Previews alone aren't enough for HDR merging. Make sure your drive is connected before you kick off a batch.

Editing an HDR DNG - Which Sliders Behave Differently

Once you have an HDR DNG in Develop, several things work differently from a regular RAW:

• Exposure range is ±10 instead of the usual ±5. This isn't a coincidence - it reflects the extra bit depth the file actually holds.
• Highlights and Whites recover much more. Dragging Highlights to -100 on an HDR DNG can pull back clouds that look completely blown in the preview. On a regular RAW, that slider often hits a wall.
• Shadows stay cleaner when pushed. As described above - the shadow data came from a better-exposed bracket at capture.
• The Tone Curve is still output-referred. Point-curve adjustments work fine, but you're now mapping a wide scene-referred range onto a display-referred output. Be conservative with S-curves on HDR DNGs or the result can look over-processed fast.

So what does this mean in practice? Start with Highlights pulled all the way down and Shadows pushed up, then use Exposure to set your overall brightness. That order of operations tends to reveal more usable dynamic range before you start making decisions.

Managing File Size After a Merge: Build Smart Previews and Archive Brackets

Merged HDR DNGs are large. A full-resolution 24 MP merge typically lands between 80 and 150 MB - roughly 5-10x the size of the original RAW files. Batch a weekend landscape session and your catalog can balloon by several gigabytes in one go.

Two habits that keep things manageable:

1. Build Smart Previews immediately after merging. In Library, select your new HDR DNGs, then go to Library > Previews > Build Smart Previews. Smart Previews are compressed DNG derivatives (2540px long edge, ~1 MB each) that let Develop stay responsive even when the originals are on a disconnected drive. For 80 MB files you're editing on a laptop, the difference is noticeable. If you want the full breakdown of how Smart Previews work, I wrote a dedicated guide here.

2. Archive original brackets separately. Once a merge is confirmed good, the bracket originals become archival - you don't need them in your active catalog. Move them to an archive folder on your main drive (or a NAS), remove them from the catalog, and let the HDR DNG be your working file. This keeps your catalog lightweight without losing the safety net of originals.

HDR merging is one of Lightroom's genuinely powerful features when it's used for the right scenes. The 32-bit DNG isn't marketing language - it's a fundamentally different file with a wider editing envelope. Use it on scenes where the dynamic range genuinely exceeds what your sensor captured in a single frame, pick your deghost settings deliberately, and manage the resulting file sizes or they'll quietly fill your drive.