These Lightroom Changes Actually Matter

The best crop is often the one you almost didn’t make.

(my favourite quote this week)

You know the shot. You had about a second and a half, you pulled the camera up, and you clipped the top of the doorway. Or the subject ended up jammed against the left edge with a metre of dead ground on the right. Back at the desk the file is sharp, the light is right, and the composition is a couple of centimetres short of working.

For most of the time I’ve been editing photographs, the answer to that was simple and annoying. Crop tighter and lose more of the picture. Or bin it.

Lightroom’s August release removes that rule, and a few other small irritations along with it. Lightroom Classic went to 15.5, the desktop app to 9.5, the phone and tablet apps to 11.5. Most release notes are lens profiles and bug fixes. This one has four changes that alter how you work.

Generative Expand has landed in Lightroom desktop and on the phone. Point at a photo, choose a wider aspect ratio, and it builds the missing edges rather than cutting into what you already have.

That sounds like a party trick until you count how many shapes one photograph has to fit these days. A 3:2 for your site, a 4:5 for the feed because tall images take up more screen, a 16:9 for a header, a 9:16 for a story. Every one of those used to be paid for by cutting further into the subject, and by the fourth crop your composition was gone.

Now you extend outwards instead. Same subject, same breathing room, four different shapes. If you shoot for a blog, a client or any kind of feed, that’s the most useful thing in this update by a distance.

The Crop panel on desktop and phone is now called Crop & Expand, and the Constrain Crop for Transparency button has moved up there with it. Two catches. Generative Expand is not in Classic yet. And it runs on generative credits, which are metered and don’t roll over month to month.

There’s a subtler cost. Before Lightroom expands a frame it flattens any AI edits already on that file and uses the flattened result as its starting point. That saves credits, because it isn’t regenerating everything each time you nudge an earlier slider. It also means those earlier edits can’t be adjusted one by one afterwards. To change one, you go back to a version or snapshot and redo the expansion. Lightroom has been proudly non-destructive for two decades, so this is a real departure. Fair trade, but take your snapshot before you expand, not after.

A photograph becomes stronger when every edit has a reason.

Select Subject and Select Sky have been good for a while and slightly wrong at the edges for just as long. Hair, branches against a bright sky, the rim of a shoulder. You’d get a faint halo and no way to soften it.

Classic and desktop now have Feather and Edge sliders for AI-generated masks. Feather blurs the boundary, Edge pushes it outwards or pulls it in. Two sliders, about four seconds of work, and the edit stops announcing itself.

It only applies to AI masks, not brushed ones, which is a shame. Still, if you edit skies or people, this is the change you’ll use every single session.

Right-click a photo and there’s a new Render to DNG option. It bakes your current edits into a new file next to the original.

Read the small print. Despite the extension, this is not a raw file. It’s a TIFF wearing a DNG jacket. You can’t pull highlight detail back out of it later, because that data is gone. It is smaller than the equivalent TIFF, though not small: one full-frame raw of around 50MB came out near 128MB once rendered.

The reason to care is workflow order. Denoise and Super Resolution have always fought over which goes first. Now you can run Denoise, render to DNG, then run Super Resolution on the clean file. It’s also the setup step for Generative Expand: crop away the distraction at the edge, render to DNG, then expand the new composition outwards.

The better frame is almost always one step to the left of where you are standing.