Last spring I was onboarding a new e-commerce client, a mid-size apparel brand, and their in-house retoucher handed me a folder of 300 product images that had already been “color graded.” Every single one looked different. Same white background, same product line, same photographer. Three hundred shots, and the whites ranged from warm cream to cool blue-grey depending on which mood the retoucher had been in that week. When I asked what process they were using, the answer was: adjustment layers, applied manually, by eye, one image at a time.

That’s not color grading. That’s hoping.

Color lookup tables, CLUTs or LUTs depending on who you’re talking to, solve this problem at a mechanical level. But most people using them in Photoshop don’t fully understand what they’re doing to the image data, which is why the results feel inconsistent or go wrong in subtle ways that are hard to diagnose.

What a LUT Is Actually Doing to Your RGB Values

A color lookup table is exactly what it sounds like: a table. Your image has pixels with RGB values. The LUT says “wherever you find RGB value (210, 180, 160), replace it with (205, 175, 155).” It maps every possible input color to a specific output color, across the entire tonal range of the image simultaneously.

In Photoshop, you apply a LUT through the Color Lookup adjustment layer (found under Layer > New Adjustment Layer > Color Lookup). The file formats you’ll encounter are .cube, .3dl, and .look. The .cube format is the most universally compatible and what I recommend building your library around. A standard .cube file maps a 33x33x33 grid of color values, covering 35,937 individual color points across the RGB spectrum. Photoshop interpolates everything between those points.

The critical thing to understand: LUTs are not smart. They don’t know what’s in your image. They apply the same mathematical transformation to every matching pixel value, regardless of context. That white dress and that white wall get the same treatment. This is a feature when your inputs are consistent. It becomes a liability when they aren’t.

Why Your LUT Results Look Wrong Half the Time

If you’re applying a LUT and the results feel unpredictable, the problem is almost always happening before the LUT, not inside it. LUTs are built to expect a specific input state. A LUT designed for a log-encoded image applied to a standard sRGB image will look terrible. A LUT built for a D65 white point applied to images shot under tungsten will pull everything green.

The fix is profile consistency before application. Every image going through the same LUT needs to arrive in the same color space, at a matched exposure baseline, with neutralized white balance. In my commercial workflow, I normalize everything to Adobe RGB (1998) at 16-bit before any LUT touches it. That means Camera Raw or Lightroom first, LUT second, output profile conversion last.

The other issue I see constantly is opacity. The default Color Lookup adjustment layer sits at 100% opacity, which is almost always too heavy for commercial work. For product photography, I rarely go above 60-70%. For skin tones in advertising work, sometimes as low as 30-40%. The LUT sets the direction; the opacity sets how far you travel.

Building a LUT Into a Reusable Photoshop Action

This is where the real time savings live. A Color Lookup adjustment layer applied through a Photoshop action takes roughly 0.3 seconds per image in a batch sequence. Applied manually, with a human opening the dialog, selecting the file, adjusting opacity, and clicking okay, that’s closer to 45-60 seconds per image. On a 300-image job, that’s the difference between 90 seconds of processing time and five-plus hours of clicking.

The action structure I use for product work runs like this: flatten and duplicate the background layer, convert to Adobe RGB (1998) via Edit > Convert to Profile, run a Levels auto-correction set to “Find Dark and Light Colors” with Snap Neutral Midtones checked, add the Color Lookup adjustment layer pulling from a specified .cube file, set layer opacity to 65%, flatten, convert to sRGB for output, and export as a TIFF at maximum quality. That entire sequence runs in about 2 seconds per file.

When I batch that against a 300-image folder using Photoshop’s Image Processor or a custom droplet, the job that used to occupy the better part of a day is done before lunch.

The .cube Files Worth Keeping in Your Library

Not all LUTs are created equal, and the free ones floating around forums are genuinely hit or miss. For commercial work I’ve landed on a small, tested library rather than a massive folder of options nobody uses.

The ones that earn permanent spots: Koji Advance for film-emulation work when clients want an editorial feel (around $99 for the full set, worth every cent), the free Technical LUT set from Lutify.me for log conversion work, and a set of custom .cube files I’ve built myself for specific client color profiles. Building a custom LUT from a 1D or 3D LUT editor like Lattice (free tier available) takes an afternoon the first time and saves hundreds of hours over years of use.

Keep your working LUT library small and documented. I have 14 LUTs in active rotation. I know what each one does, what input it expects, and which client situations it fits. I track this in a spreadsheet alongside my action runtimes, because if I don’t measure it, I don’t actually know if it’s working.

The One Thing That Will Make or Break Your LUT Workflow

I processed over 500 product images for a furniture client in a single afternoon using a batch system built around two custom .cube files and a four-step Photoshop action. The speed was the easy part. The hard part was the three days I spent beforehand standardizing the input images: matching exposures, correcting white balance, building a consistent camera profile. Without that upstream work, the LUT would have amplified every inconsistency instead of resolving it.

That’s the real lesson with color lookup tables. They’re multipliers, not fixers. Give them consistent input and they return consistent, scalable, fast results. Give them chaos and they’ll hand it back to you in a slightly different color.