A practical workflow for diagnosing double edges, checking bracket alignment, and deciding when to re-merge, request manual editing, or capture the room again.
The living room looks bright. The window view is visible. The shadows are balanced.
Then you zoom in.
The window frame has a second edge. A curtain looks transparent. The leaves outside appear in two positions at once.
The immediate reaction might be to sharpen the image, run another enhancement tool, or ask AI to “make it clean.”
Before doing that, return to the source photographs.
HDR ghosting in real estate photos is a merging problem that needs diagnosis—not simply a more attractive final render. The right next step might be better alignment, a different deghosting setting, a source-based manual repair, or a reshoot.
This guide explains how to make that decision in seven checks.
Editorial disclosure: This article was prepared for Pixel Perfects Solutions and includes relevant first-party references to EstateAI and Dotera. The examples are hypothetical. The workflow is an editorial recommendation, not a report of hands-on software testing.
Quick answer
To troubleshoot HDR ghosting, first verify that the correct exposures belong to the same bracket set. Inspect the individual photographs, distinguish camera movement from moving subjects, and then test the merge software’s alignment and deghosting controls.
If a usable source exposure contains the affected detail, consider a targeted, source-based repair. If the necessary detail was never captured clearly, consider reshooting rather than generating an unverified replacement.
Fix the photographic foundation before adding another transformation.
In this article, HDR means combining exposure-bracketed photographs. It does not refer to an HDR monitor or an HDR export setting.
First, make sure the problem is actually ghosting
Ghosting is not a catch-all name for every unnatural-looking HDR result.
Research on ghost-free HDR imaging identifies object movement and image misalignment as important sources of merging artifacts.
Use the following table as a starting point—not a diagnosis from appearance alone.
| What you notice | First possibility to investigate | Where to look |
|---|
| Repeated edges across fixed features | Bracket mismatch or alignment problems | Source grouping and stationary architectural details |
| A curtain or tree appears in multiple positions | Movement between exposures | The affected subject in each source frame |
| Detail is soft in the original photographs too | A capture or focus problem | Individual files before merging |
| A broad bright or dark fringe surrounds an edge | Tone-mapping or sharpening artifacts | Processing settings rather than only deghosting |
| A window disappears after a later AI edit | A separate generative alteration | The approved merge compared with the AI output |
The distinction between halos and ghosting matters. HDRsoft’s Photomatix FAQ discusses halos as a tone-mapping issue with different corrective settings.
Do not keep increasing deghosting simply because every unwanted edge has been labeled a “ghost.”
1. Confirm that the bracket set contains the right photographs
Start here before changing processing settings.
Check that every source image represents the same composition and belongs to the intended exposure sequence.
Review the thumbnails, capture times, exposure information, and visible framing together. Treat metadata as supporting evidence, not a substitute for looking at the photographs.
Why a complete folder is not enough
Imagine a hypothetical batch processor that groups every three consecutive files.
One exposure is missing from the first sequence.
The next group can now include photographs from two different compositions. The processor may still receive three valid image files, but they are not a valid bracket set.
This is a grouping error, not a problem that should be solved by stronger deghosting.
What to verify
Confirm the intended number of exposures, whether any source file is missing or duplicated, and whether the camera moved to a different viewpoint between groups.
Do not apply one assumed bracket count to an entire shoot without checking that the capture pattern stayed consistent.
Review action: Open the exact input set used for the failed merge. Confirm that it contains one composition and the intended exposure sequence before retrying.
2. Inspect the source photographs before blaming the merge
A finished HDR image can make a capture problem more noticeable, but that does not mean the merger caused it.
Inspect each original at full size, especially around window frames, cabinet edges, curtain patterns, and other fine details.
Ask:
Does at least one source photograph contain a sharp, usable version of the affected area?
That answer helps determine whether the next step should be reprocessing, manual repair, or a new capture.
Check consistency across exposures
Look for changes in focus, framing, and aperture.
HDRsoft notes that aperture changes can alter sharpness and depth of field between exposures, and recommends maintaining aperture when bracketing.
A repair plan should distinguish between a detail that is sharp in one source and a detail that is unclear in every source.
Do not treat a generated, sharper-looking replacement as evidence that the original detail has been recovered.
Improve the next capture
HDRsoft’s interior-photography guidance recommends stabilizing the camera, checking focus, and capturing the bracket sequence consistently.
Use those as capture checks rather than assuming that more post-processing will compensate for every source problem.
Review action: Identify the best available source for the problem area. Record when no source contains enough reliable detail to support the proposed repair.
3. Separate camera movement from subject movement
These problems can produce similar-looking artifacts, but they are not the same.
Camera movement changes the relationship between the frames.
Subject movement changes part of the scene between exposures.
For example, a camera may remain stable while a curtain moves in the airflow or leaves move outside the window.
A tripod does not make those subjects stationary.
Compare fixed details first
Choose several reference points across the image: a fireplace corner, a window-frame intersection, a cabinet edge, and a ceiling junction.
Compare their positions between source photographs.
Then inspect the moving subject separately.
If fixed features shift too, investigate alignment. If fixed features remain consistent but the curtain changes position, investigate local movement.
Both problems can occur in the same bracket set.
Avoid a one-label diagnosis
“Everything looks doubled” is not an actionable editing brief.
“Fixed window edges are offset across the bracket, while the curtain also moves independently” gives the editor two specific issues to address.
Review action: Mark whether the problem affects fixed geometry, moving subjects, or both. Use that distinction to choose the next test.
4. Re-merge with the appropriate alignment and deghosting controls
For a documented example, Adobe’s Lightroom Classic HDR guide provides separate controls for alignment and deghosting.
Select the bracketed photographs and open Photo → Photo Merge → HDR.
Auto Align is intended to help with small movements between source frames. It does not replace checking that the photographs belong together.
For ghosting, Lightroom Classic provides None, Low, Medium, and High settings. Adobe recommends trying Low first, increasing only when necessary, and avoiding deghosting when the preview does not contain ghosting.
Use the available deghost overlay to inspect the affected regions.
Do not make High the default for every property image.
Compare candidates instead of guessing
For your own workflow, keep the original failed merge and the revised candidate visible together.
Record which setting changed and whether it corrected the identified problem without introducing another visible issue.
These controls are specific to Lightroom Classic. Do not assume that every HDR application exposes equivalent settings or uses the same labels.
Review action: Approve the revised image based on the visible result—not the strength of the setting selected.
5. Consider a source-based repair when one area still fails
Sometimes the room merges acceptably while a small moving region remains problematic.
If a source exposure contains a usable version of that area, a targeted repair may be worth evaluating before reshooting the entire composition.
One proposed approach is to align that source with the merged image and reveal only the required region through a layer mask.
Adobe’s layer-mask documentation explains how masks hide or reveal selected parts of a layer.
Keep the repair tied to the actual photograph
For a hypothetical moving curtain, the goal would be to use a coherent curtain position from the source material—not to generate a new window and hope it resembles the property.
Check the repaired boundary, exposure, color, and any overlapping objects.
A sharp source region that does not blend correctly can create a different problem.
Do not replace the photographed exterior with a different view simply because it is easier to composite.
Know when this approach is unsuitable
A source-based repair requires suitable source material and sufficient alignment.
When those conditions are missing, forcing a composite may be less defensible than returning to the property.
Review action: Keep the source file and mask editable. Confirm that the repaired detail comes from the same photographed scene and that the join is visually consistent.
6. Approve the HDR merge before starting generative editing
Treat the merged photograph as a separate approval stage.
A later virtual-staging or redesign request should not be responsible for deciding what a damaged window edge was supposed to look like.
The proposed sequence is:
Source brackets → Photographic merge → Quality review → Approved base image → Optional AI treatment → Final review
This separation is relevant to EstateAI by Pixel Perfects Solutions and its HDR Merge workflow.
Its published product description separates photographic HDR processing from generative AI services. It describes bracket preparation, alignment, exposure fusion, and subsequent property-media workflows, including support for common three-, five-, and seven-exposure sets.
Those are first-party product descriptions—not proof that every difficult bracket will merge successfully.
Do not assume a control exists
The troubleshooting controls described earlier belong to Lightroom Classic.
This article does not claim that EstateAI exposes the same deghosting settings or that its HDR process guarantees artifact-free output.
For a broader explanation of capture and merge preparation, see the EstateAI HDR real estate photography guide.
Review action: Compare the approved base photograph with every subsequent transformation. A later attractive result must not hide an unresolved photographic error.
7. Decide between another merge, professional editing, and a reshoot
Not every failed result needs another generation attempt.
Use the evidence already collected to choose the next action.
| What the review establishes | Suggested next step |
|---|
| The wrong photographs were grouped | Correct the input set, then merge again |
| The sources are usable but fixed edges do not align | Test the available alignment controls |
| Local motion causes the remaining artifact | Evaluate deghosting or a source-based local repair |
| A suitable source exists, but the repair needs careful blending | Request manual editing with the complete bracket set |
| No source reliably captures the necessary detail | Consider a reshoot |
| An AI edit changed geometry after the merge was approved | Return to the approved base and revise or reject that separate edit |
These are proposed decision rules, not guarantees that a particular file is recoverable.
Send a useful professional-editing brief
Pixel Perfects Solutions provides professional property-visual services, including real estate image enhancement.
When asking an editor to assess a difficult merge, provide the complete bracket set rather than only the damaged export.
A practical brief could read:
Issue: Double edges around the right-hand window and a repeated curtain outline.
Source material: Complete original bracket set and the current merged output.
Required result: A natural photographic correction based on the supplied source images.
Preserve: Window geometry, exterior view, fixed fixtures, room proportions, and visible property condition.
Stop condition: Flag any area that cannot be verified or repaired from the available source material.
Professional editing can improve execution. It cannot establish a property detail that was never captured clearly.
Review action: Ask for an assessment of the source files before assuming the image can be repaired without another visit.
For PropTech teams: a completed merge is not an approved image
A merge job can finish successfully while its output still needs review.
For a property-media application, treat processing completion and editorial approval as different states.
A proposed workflow would distinguish:
Processing → Ready for review → Approved, revision requested, or new source required
“New source required” deserves its own outcome. It is not the same as a server error.
For each merged image, retain the source-file list, bracket grouping, processing version, and review decision.
If a source file or merge setting changes, require review of the new output rather than inheriting approval from an older version.
Also flag uncertain grouping instead of silently forcing every upload into a fixed number of images.
These are proposed software controls, not claims that every platform implements them.
Connect the repair to the delivery workflow
Dotera describes order management, communication, file delivery, and revision workflows in its Pixel Perfects portal case study.
That first-party case study illustrates the surrounding production software. It does not establish that the specific HDR checks proposed here are already implemented.
The design lesson is to keep the brief, source files, candidate outputs, and approved delivery connected.
For the separate review of generated listing images, read 15 AI Real Estate Photo Errors Humans Must Catch Before Publishing.
Final takeaway
HDR ghosting is a reason to investigate the source and merge—not immediately redraw the room.
Start with the bracket set. Inspect the originals. Separate camera movement from subject movement. Test the relevant controls. Use source-based repair where the evidence supports it.
When the necessary detail is missing, a reshoot may be the more reliable decision.
A clean merge should reveal the photographed property—not replace uncertain details with a convincing guess.
Which issue takes longer in your workflow: correcting bracket grouping, removing motion artifacts, or obtaining better source photographs?
Sources and further reading
Company-specific descriptions are linked to their first-party sources in the relevant sections.
Sources reviewed on September 10, 2026. Software interfaces and capabilities can change; check the documentation for the version you use.
About the Author
Waqas Ahmad — Content Creator & Software Engineer
Waqas Ahmad creates research-driven content covering real estate photography, property marketing, AI, PropTech, software, and digital visibility. Through his work with Pixel Perfects Solutions and its related products, he explores how technology and creative content can help businesses improve their digital presence and build stronger brands.
His writing combines technology, creativity, and practical industry insights to make complex ideas easier to understand and apply.
Building Brands Through Content & Technology