What each tool is actually reading
The confusion isn't your fault. Photoshop puts both tools one menu apart and both get described as "masking" in tutorials, but they're built on completely different data.
Color Range: a color-similarity selector
When you use Select → Color Range with "Sampled Colors," you click a pixel, and Photoshop selects every other pixel within a Fuzziness tolerance of that color, in hue, saturation and lightness together. It's a color-matching tool first. That's exactly why it's good at selecting a blue sky, a green screen, or a red shirt: you're asking "give me more pixels like this one," and color is the thing that defines "like this one."
Luminosity mask: a brightness-only selector
A real luminosity mask, built by Ctrl-clicking the RGB composite thumbnail in the Channels panel, ignores hue and saturation completely. It only reads how bright each pixel is, on a 0-255 (or 0-32,768 in 16-bit) scale, and builds a grayscale selection from that single value. Two pixels can be a completely different color and still belong to the exact same luminosity mask, as long as they're equally bright. That's the entire point: it lets you target a tonal range, like "the brightest 20% of the image," regardless of what color those bright areas happen to be.
Where the confusion actually comes from
Since Photoshop 2020, Color Range has had a "Select" dropdown with Highlights, Midtones and Shadows options built in, sitting right next to Sampled Colors. On the surface, this looks like Adobe gave you a one-click luminosity mask inside Color Range. It's close, but it's a different, cruder algorithm.
The Highlights/Midtones/Shadows presets in Color Range still run through the same fuzziness-based selection engine the tool uses for color matching, tuned to approximate a tonal range instead of a hue. In practice that means: less predictable edge quality than a true composite-channel selection, no ability to refine the result the way you'd refine a mask with Levels, and a selection that can shift slightly depending on the Range and Fuzziness sliders rather than being tied directly to the pixel's actual brightness value. It's a reasonable quick approximation. It's not the same selection you'd get from Ctrl-clicking the RGB thumbnail.
A test you can run in thirty seconds
Open any image with a clear tonal range, like a backlit landscape. Build a luminosity mask the native way: Ctrl-click the RGB composite thumbnail in the Channels panel, save that selection as a mask. Then, on a duplicate, run Color Range with Select set to Highlights. Zoom into a transition zone, like where a bright sky meets a mid-tone mountain ridge, and compare the two masks in the Channels panel side by side. The composite-channel mask reads as a clean, continuous gradient that matches the image's actual brightness map. The Color Range version is noticeably rougher at the edges and less proportional to the real luminance values underneath.
When to actually reach for each one
Use Color Range when the thing you want to isolate is defined by color, not tone: a specific sky for a sky replacement, a green screen for compositing, skin tones for a portrait retouch, a red product against a neutral background. The question you're answering is "which pixels share this color," and Color Range is built to answer exactly that.
Use a luminosity mask when the thing you want to isolate is defined by brightness, not color: exposure blending across a wide dynamic range, dodge and burn that should apply only to shadows or only to highlights, contrast work that needs to protect already-bright or already-dark areas from further pushing. The question you're answering is "which pixels are in this tonal range," regardless of hue, and that's a question Color Range's presets only approximate.
They're not mutually exclusive
The most precise selections often combine both. Build a luminosity mask for "brightest 20%," build a Color Range selection for "anything blue," then intersect the two (Shift+Alt-click a mask thumbnail loads it as a selection you can further modify) to get "the bright parts of the sky specifically," without touching bright clouds or a bright building facade elsewhere in the frame. Treating them as competitors misses the actual workflow: they answer different questions, and the best edits usually need both answers at once.
Quick answers to a few related questions
Can Color Range select by luminosity at all?
Only approximately, through the Highlights/Midtones/Shadows presets described above. For a selection that's actually proportional to pixel brightness, Ctrl-click the RGB composite thumbnail instead.
Does the "Localized Color Clusters" option in Color Range change this?
No, that option only changes how Color Range handles multiple sample points spatially. The underlying selection is still color-based, not brightness-based.
Which one should I use for exposure blending?
A luminosity mask, every time. Exposure blending is fundamentally a tonal problem (which parts of each exposure are correctly exposed), not a color problem, so a brightness-based selection will always track the actual exposure data more accurately than a color-similarity approximation.
EN
IT