Luminance HDR Crashing? Fixes for Common Crashes & Freezes (2026)

Nothing kills a creative flow like a crash halfway through an HDR merge. The good news: most Luminance HDR crashes are not random. They cluster around a handful of known causes — memory pressure, the anti-ghosting step, and full-resolution tone mapping — and each has a practical workaround. Work through the symptoms below in order.

1. Luminance HDR crashes while merging brackets

This is the most common crash, and it is almost always about memory. Merging five 45-megapixel RAW files into a 32-bit HDR image can easily need several gigabytes of RAM, and if the system runs out, the program goes down without much warning.

What to try

• Merge fewer brackets at a time. If seven exposures crash, try the merge with three or five first. You can always re-run with the full set once you know the stack is healthy.
• Close other applications before a big merge — browsers with dozens of tabs are notorious memory hogs.
• Use the 64-bit build. A 32-bit build cannot address more than about 4 GB of RAM no matter how much your machine has. Check the download page for the right version.
• Convert RAW to 16-bit TIFF first if RAW decoding itself is the choke point. It adds a step, but TIFFs are far cheaper to load than RAW files.
• Check free disk space. Temporary files during a merge can balloon; keep several gigabytes free on the drive holding your temp folder.

2. Luminance HDR crashes when anti-ghosting is enabled

Anti-ghosting is the most computationally fragile part of the merge pipeline. On stacks with large motion, water, or foliage in wind, the deghosting pass can fail where a plain merge would succeed.

What to try

• Turn anti-ghosting off and merge again. This isolates the problem: if the merge completes without it, you know exactly which step was failing.
• Use it selectively. If only one or two frames contain the moving object, consider excluding those frames from the stack instead of deghosting the whole set.
• Shoot to avoid the problem. Faster burst shooting and a tripod reduce the motion that makes deghosting necessary in the first place — see our exposure bracketing guide.

Be aware of the honest limit here: the anti-ghosting implementation handles moderate motion reasonably, but it is not magic on scenes with heavy movement. For our full walkthrough, see how to fix ghosting in HDR photos.

3. Tone mapping freezes when you press Apply

Tone mapping recalculates the entire image every time you apply settings. On a high-resolution file with an operator like Mantiuk ’06, that recalculation can take long enough to look like a freeze — and on weaker machines it can tip over into a real crash.

What to try

• Dial in parameters on a smaller preview first. Get the look right at reduced size, note the settings, then apply once at full resolution and walk away while it processes.
• Start with lighter operators. Drago and Reinhard ’05 are much cheaper to compute than Fattal or Mantiuk ’06. If you only need a natural result, you may never need the heavy ones.
• Do not stack heavy operations. Applying tone mapping, then immediately re-applying with tweaked settings five times in a row, multiplies the load. Settle the parameters, then commit.
• Update your GPU and chipset drivers. Stale drivers are a classic cause of freezes during compute-heavy image operations.

General stability checklist

• Run the latest stable release from the download page — crash fixes do land between versions.
• On Windows, try running as administrator once to rule out permission issues with temp folders.
• Keep source files on a local drive, not a network share or a nearly-full SD card.
• If a specific file always crashes the program, test whether that file opens in another RAW viewer — a corrupt frame can poison the whole merge.

Symptom, likely cause, and fix at a glance

When to wait for an update instead

Luminance HDR is a community-maintained open-source project, which means bug fixes can take a while to land. If you have ruled out memory, drivers, and corrupt files and the crash is reproducible, the most useful thing you can do is report it on the project’s GitHub issue tracker with your OS version, the steps to reproduce, and — if possible — a sample file set. Vague “it crashes” reports are hard to act on; reproducible ones get fixed.

Frequently Asked Questions

Why does Luminance HDR crash when merging?

In most cases it is memory pressure: merging several large RAW files into a 32-bit HDR image needs gigabytes of RAM. Merge fewer brackets at once, close other applications, and make sure you are running the 64-bit build.

Why does anti-ghosting crash Luminance HDR?

The deghosting pass is the most fragile step of the merge, especially on stacks with heavy motion, water, or wind-blown foliage. Turn it off to confirm it is the culprit, then either exclude the problem frames or accept a manual workaround.

Why does tone mapping freeze when I press Apply?

Every Apply recalculates the whole image at full resolution, which can take a very long time with heavy operators on large files. Set your parameters on a small preview first, then apply once at full size.

How much RAM does Luminance HDR need?

There is no fixed number — it scales with file size and bracket count. As a rule of thumb, 8 GB is a comfortable minimum for 24-megapixel brackets, and 16 GB or more is advisable for 40+ megapixel stacks. When in doubt, merge fewer frames at a time.

Where do I report a Luminance HDR crash?

On the project’s GitHub issue tracker. Include your operating system and version, the exact steps that trigger the crash, and whether it happens with every file set or just one — reproducible reports are the ones that get fixed.

Luminance HDR is free and open source (GPLv2).