How Does PixelPeeper Read Lightroom Edits from a Photo?

PixelPeeper reads Lightroom edits in two different ways depending on what the file contains. If the photo still has its embedded XMP metadata, PixelPeeper recovers the actual saved adjustments — exposure, contrast, highlights, shadows, tone curve, and color mixer values — and can export them as an XMP preset. If that metadata is missing, it falls back to Look Match, a machine-learning estimate based on how the photo looks. The first path gives you real settings; the second gives you a starting point, not a recovery.

The two paths, side by side

The distinction matters because only one of these tells you what the photographer actually did.

Path 1: Recovering embedded edits

When a photo contains Lightroom metadata, PixelPeeper surfaces the saved adjustments rather than guessing. The sample photos on the site show what this looks like in practice — for example, a Sony ILCE-7M2 shot at 55.0 mm, f/2.0, 1/100, ISO 200 with embedded edits of Exposure +0.40, Contrast 0, Highlights 0, Shadows 0, and color mixer values of Red −10, Green +26, Blue +13.

The reported items include:

• Camera settings — body, focal length, aperture, shutter speed, ISO
• Lightroom edits — Exposure, Contrast, Highlights, Shadows
• Tone curve — RGB curve adjustments
• Color mixer — Hue shifts per color channel (Red, Orange, Green, Blue)

You can open a full inspector for each photo and download the settings as an XMP preset to load into Lightroom and explore yourself.

Why the metadata is there in the first place

Lightroom can write your adjustments into the exported file's XMP data. When that happens, the edit information travels with the image. PixelPeeper reads from that embedded XMP data — it isn't reverse-engineering the pixels to find your sliders. This is why the recovered values are exact when present, and why they're simply unavailable when the export stripped or omitted that data.

Path 2: Look Match when edits are missing

Not every photo carries edit metadata. When it doesn't, PixelPeeper offers Look Match: a custom machine-learning model that suggests Lightroom adjustments based on the photo's appearance.

Two things to keep in mind:

• These are estimates, not recovered settings. The model is inferring a plausible set of adjustments from the visual result.
• Results vary by photo. A clean, well-lit image may yield a more usable starting point than a heavily stylized or low-quality one.

Treat Look Match as a way to explore a similar look, not as a claim about what the original photographer did.

Using PixelPeeper with an AI assistant

PixelPeeper can be connected to Claude or ChatGPT. In the example conversation shown on the site, a user asks the assistant to show how a photo was edited; the assistant calls PixelPeeper and returns a photo report covering camera settings, Lightroom edits, and a color palette, then explains that the soft, matte look comes largely from the tone curve and selective color adjustments — lifted blacks and airy highlights, with the curve lifting the black point from 0 to 50.

This is useful when you want the settings interpreted in plain language rather than just listed.

What to check before trusting a result

• Did the file keep its edit metadata? If yes, you're seeing recovered settings. If no, you're seeing a Look Match estimate.
• Does the photo match your intent? Look Match estimates are appearance-based, so a similar-looking photo with different underlying edits can produce different suggestions.
• Do you need the preset or just the idea? Embedded edits can be downloaded as an XMP preset; Look Match gives you adjustments to try, not a recovered file.

PixelPeeper Premium is listed at $49 for 12 months, with no automatic renewal.