A product family should look like a family. The fastest way to get that look, once a first hero is approved, is to reuse the lighting setup rather than inventing a new mood for each object. In a generated workflow, a lighting setup is a written clause plus one approved still, not a physical room you can leave standing. You have to be more explicit than you would be in a studio.
Capture the setup in six parts: source, direction, hardness, color, background level, and reflection rules. If the approved hero was “large window from the left, soft shadows, slightly warm daylight, mid-gray paper, no glare on the label, those words are the setup. Save them in the brief template for the family, and do not decorate them with new adjectives when you change the product.
Save the camera as well. Lighting reuse fails when the next product is shot from a completely different height. A family that shares light but jumps from overhead to table level will still look like mixed campaigns. Write the camera height and the lens feel next to the light clause, and treat both as locked unless a product physically cannot fit that view.
When the next object is a different size or material, do not throw the setup away. Adjust one thing: the distance, the reflection rule, or a fill that keeps a dark object from sinking into the background. A black device and a white box can share a window, but they may not share the exact background brightness. The family look comes from the source and the direction more than from an identical gray value.
Run a small test of two or three drafts on the new object before you generate a full set. If the light does not transfer, decide whether the object needs a documented exception or whether the original setup was more fragile than it looked. An exception should be rare and written. If every object needs an exception, you do not have a family setup yet.
Compare the new drafts against the approved hero at the same size, not only against the prompt. Side-by-side is how you see a color shift or a harder shadow that the text of the prompt did not reveal. If you do this from memory, you will approve a slightly different sun in each still and notice it only when the grid is built.
A more careful model pass can help when a new material stresses the setup, for example a chrome object that needs the same window but a controlled highlight. a reusable lighting setup is a reasonable place to do that careful pass without changing the written setup. The point is to keep the family rule, not to chase a more dramatic light just because the object can take it.
Keep typography in mind when you reuse light. A setup that was safe for a pack with a large, high-contrast label may be unsafe for a pack with thin foil type. If a new object has more delicate type, add a typography check to the family review rather than silently hardening or softening the light in an undocumented way.
Name the setup and date it. “Family daylight v2, May, left window, warm, mid paper” is enough. When someone later makes a still that does not match, you can ask whether they used v2 or invented a new mood. Unnamed setups cannot be reused, because no one can point to them.
Do not mix two family setups in the same grid unless the campaign says so, for example a daylight row and a night row. Accidental mixing happens when a late still is generated in a hurry with a shorter prompt. The short prompt should still include the setup name or the six-part clause. Speed is not a reason to leave the family.
At the end of a family project, export a small board of approved stills and the written setup. That board is the brief for the next product that joins the line. Without it, a new teammate will write a pretty new light and slowly break the set you already approved.
Reusable lighting is a written, named, six-part clause, a locked camera, a small transfer test, a side-by-side check against the hero, and rare documented exceptions. It is one of the less glamorous parts of generation work, and it is what makes a product family look finished rather than like a folder of separate ideas.
Top comments (0)