Overview
Luminar Neo takes the edits that normally need a careful mask and does the masking for you. Sky replacement, relighting by depth, subject isolation, skin and eye work, atmospheric haze and structural enhancement all run against an automatic segmentation of the frame, which means the tool that would take ten minutes of brushwork in a general editor takes one slider here.
It is a layer based editor underneath, not a preset applier. Adjustment layers, image layers, blend modes, masks and per-layer opacity all behave the way a photographer would expect, and every automated edit lands as an editable layer with its own mask rather than being burned into the pixels. The catalogue side handles folders of images with non-destructive edits held separately from the files.
The extension set included here covers the additions sold separately: noise reduction, upscaling, background removal, focus stacking, HDR merging and supersharpening. Together with the core toolset that covers most of what a landscape, portrait or property photographer needs, and the plug-in mode means it can also sit inside a heavier editor as one step in an existing workflow.
What it does well
Automatic masking
The frame is segmented into sky, subject, skin, background and depth layers, and every relevant tool masks itself to the right region.
Relighting by depth
Adjust foreground and background exposure independently using a depth estimate, which recovers shots that were lit badly at capture.
Sky replacement
Swap a flat sky with horizon detection, relighting of the scene to match, and reflection handling on water.
Layer based editing
Adjustment and image layers with blend modes, masks and opacity, so nothing an automated tool does is permanent.
Extension set
Noise reduction, upscaling, background removal, focus stacking, HDR merge and supersharpening all included.
Changes in this build
- Segmentation model updated, which improved edges on hair and fine foliage.
- Relighting performance roughly doubled on current GPUs.
- Catalogue browsing reworked so large folders load without a stall.
- New sky library entries and better horizon blending on complex skylines.
- Fixed a plug-in return path defect that could flatten layers in the host document.
What is in the package
- Luminar Neo installer, 64-bit
- Full extension set with all add-on modules
- Sky, texture and look libraries
- Host editor plug-in module
- Multilingual interface files, 12 languages
System requirements
| Processor | Intel or AMD 64-bit, quad core recommended |
| Memory | 8 GB minimum, 16 GB for large raw files |
| Graphics | GPU with 4 GB VRAM for the masking and relighting tools |
| Storage | 10 GB free plus catalogue and cache space |
| Display | 1920 x 1080, colour accurate panel recommended |
| System | Windows 10 or Windows 11, 64-bit |
Installation
- Close any host editor before running setup.
- Extract the archive and run the installer to the default path.
- Apply the included configuration step before the first launch.
- Open the extensions panel and confirm every module is listed.
- Turn the update check off in preferences.
Before you start
The masking tools need a GPU, on integrated graphics they fall back to a slow software path.
Catalogue edits live outside the image files, back the catalogue up separately.
Updating replaces the configuration and takes the extensions back out.
Questions about this title
Are the extensions included?
Yes, the full add-on set is present rather than sold as separate modules.
Does it work as a plug-in?
Yes, it can run inside a host editor and return the result as a layer.
Is editing non-destructive?
Yes, edits are held in the catalogue and the original files are never rewritten.
Does it handle raw files?
Yes, raw processing is built in with profiles for current camera bodies.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.