Keep Style-Frame Variants in One Photoshop File Without Losing Their Differences
Keep Style-Frame Variants in One Photoshop File Without Losing Their Differences
A layer comp is a record of decisions about layers that already exist in your file: which ones are visible, where they sit, what style is attached to them. It is not a copy of the artwork. Adobe's Layer comps documentation describes the captured properties as visibility, position, appearance and a Smart Object's own comp selection, and warns that deleting, merging or converting layers can prevent a stored state from being restored (helpx.adobe.com/photoshop/using/layer-comps.html).
That distinction decides almost everything else. A difference the file can express as a selected layer state belongs in a comp. A difference that lives in the pixels themselves needs its own content, because every comp pointing at a given layer is pointing at the same pixels underneath.
The failure mode here is quiet. A lost file announces itself; a shared edit doesn't. You discover it two weeks later when a variant you exported no longer exists, and what you have is three comps that all show the newer bag.
Identify the difference before saving the variant
Before you name anything, sort every intended difference between variants into one of two bins. The first bin is state: this layer on or off, this layer here or there, this layer carrying one style or another. Those are the properties a comp records. The second bin is content: the photograph inside the layer, the texture painted on it, the words in a text layer.
The test is short. Can I create this difference by flipping a layer off, moving it, or switching a style? If yes, a comp can hold it. Would I have to change what is inside a layer that both variants share? If yes, you need separate content, not a separate comp.
A lot of the practical work happens before you open the Layer Comps panel at all. Take a background that needs to look different in two variants. If you build it as two layers — a photographed paper texture and a flat dark field — then one on and one off gives you both versions from state alone. If you build it as one layer and repaint it, you have a history problem rather than a variant.
Give each variant a purpose in one line before you build it. "Dark field, type reversed out" is a purpose. "Version 3" is a hope. If you can't state what makes two variants different from each other in a sentence, you probably have one variant and some earlier drafts, and drafts are what your history and save-as copies are for.
A caution about the property list. It is short, and it is specific. Read it literally. If a variant differs in something that isn't on it — an opacity value, a mask, the wording of a shared text layer — treat that difference as unproven until you've checked it in your own copy of Photoshop. Documentation states what a comp stores; your version's behavior is what you actually rely on.
Record named states and inspect what they restore
Create the comps from the organized file, recording deliberately the properties your variants really change. Name each one by its visual difference — A dark field, B paper field, C edge placement — rather than by an assumed winner. Names like final and final-good encode a decision you haven't made yet, and they make the eventual handoff harder to read.
Then do the inspection pass, because creating a comp and trusting a comp are different activities. Move between the states and compare each frame against the purpose you wrote down. You are checking three things: that the comp shows what you meant, that it doesn't also carry something you didn't mean, and that the layers doing the work are the layers you think.
This is also where the difference between a selected comp and your current working state matters. Clicking a comp applies what it recorded. Whatever you've rearranged on the canvas since then is not recorded anywhere until you update a comp. The ordinary version of this mistake: you nudge the product layer for the edge-placement variant, click over to another comp to check something, come back, and the product has returned to where it was. Nothing was destroyed. Nothing was saved either.
So update on purpose. An update is a deliberate act — "this revision is the variant now" — not a reflex after every drag. If you update a comp every time you touch a layer, you lose the ability to tell a worked-out state from an experiment you were about to abandon.
If your variants are placed as Smart Objects, one more recorded property applies: the documentation says a comp can store which comp is selected inside a nested Smart Object. That is useful when a master file holds several frame placements. It is also the same warning at another scale — editing that Smart Object's contents changes every placement that uses it.
Make a shared change and expose its reach
Everything below is a constructed walkthrough on an invented file. It is not a file I built or exported, and it isn't a test result; the documented behavior is Adobe's, the arrangement is mine.
The file is kestrel-coffee-frame-v7.psd, 1080 × 1350, six layers:
bg paper texture— scanned paper, cleanedbg deep field— a flat dark green shape covering the frameproduct pouches— a Smart Object holding the studio photographtype headline— live text with a layer styletype legal— live text, plainframe top rule— a thin shape
Three comps:
A dark field— deep field visible, paper texture hidden, headline carrying the light styleB paper field— paper texture visible, deep field hidden, product sitting lower left, headline carrying the dark styleC edge placement— paper texture visible, product pushed right until the bag edge meets the frame edge, top rule hidden
The shared base is product pouches, type legal and the rule. Every comp depends on them; only visibility, position and style differ across the three.
Now the client asks for the new 250 g bag. If all three variants should show it, edit the Smart Object's contents once. All three comps update together. This is comps working as intended — the shared base is shared on purpose, and one edit should reach three variants.
If only the edge-placement variant should show the new bag, you cannot record that difference as a state of the existing layer, because there is only one product pouches layer and one set of pixels inside it. You have two honest options. Duplicate the Smart Object into product 200g and product 250g, line them up, and record visibility per comp: A and B show the 200 g bag, C shows the 250 g one. Still one file, still three comps, and the pair of layers is now part of the shared base you have to document. Or, when the two bags need different crops, different retouching and a different frame around them, accept that the divergence is no longer about state and give the route its own source file. The cost of that is real: the type and rules you were maintaining once now exist twice, and they will drift.
The accidental shared edit is the one that hurts. Suppose you're refining the paper texture while B paper field is selected. The texture is on the canvas and your brushwork shows, so you judge the work against the comp in front of you. C edge placement draws on the same bg paper texture layer. Save the file and C is carrying your repaint — a change you never once looked at in the comp where it landed.
There is no per-variant undo for this. A comp cannot revert a repaint for one alternative, because the repaint happened to the layer, not to the state. Your recovery is Edit > Undo, the history panel, or an earlier saved copy of the file — which is another way of saying the comp was never a version.
The habit that prevents it costs a few seconds. Before touching anything on the shared base, ask which comps contain that layer. If you can't answer, that is your signal to check. And resist the urge to keep adding comps when a variant is missing. If the content was deleted or repainted, more comps will not reconstruct it.
Treat warnings and exports as a verification point
Keep one disposable copy of the file specifically for destructive demonstrations, and use it here. On that copy, delete bg paper texture. Comp B's stored state refers to a layer that no longer exists. Adobe's documentation says deleting, merging or converting layers can prevent a stored state from being restored, and that clearing a warning does not restore deleted content.
Read that last clause carefully. If Photoshop tells you something about restoring a comp, that message is information — a recorded state now points at something missing. Clearing it removes the notice. It does not bring the paper back. Dismissing a warning is not a repair, and it isn't a decision about whether the variant still matters.
Recovery runs through an intact source, not through the comp. Restore the layer from the pre-delete copy or a backup, or rebuild it and then update the affected comps so the recorded states match what's actually there. Both routes need something outside this PSD. That is the practical meaning of a layer comp is not a backup: it has nothing to restore from.
Then verify by exporting. Reopen the file rather than trusting the session you've been working in all afternoon, and export the intended comps — the documentation covers exporting comps as a set. Name the exports so they map directly onto comp names: kestrel-v7-A-dark-field.jpg and so on. Compare them under matching conditions: same viewer, same zoom, same surrounding background, ideally the same display. Check the image and its label together, because a tight-edge frame wearing a dark-field filename is the kind of thing that reaches a client.
Two last documents, and they take a paragraph. A short shared-base note — which layers every comp depends on, and which comps depend on which state — so the next designer opening product pouches knows the reach of an edit before making one. And one plain sentence about the content decision you made: whether the routes live in one file as states, or in separate sources because their content genuinely diverges.
What you hand over, then, is not three images with a vague sense that the file can regenerate them. It is three named variants, a stated shared base, and an explicit note about what is independent. The file's job is to keep the routes honestly separated while you compare them. It was never going to pick one for you.
Frequently asked questions
When does a difference between variants belong in a layer comp, and when does it need separate content?
A layer comp records state: which layers are visible, where they sit, what style is attached, and a Smart Object's own comp selection. It does not copy artwork. If you can create the difference by flipping a layer off, moving it, or switching a style, a comp can hold it. If you would have to change what is inside a shared layer, you need separate content.
Why can a shared edit change more than one variant, and how do you recover?
Every comp pointing at a given layer is pointing at the same pixels underneath. Editing a shared layer can therefore update several comps at once. There is no per-variant undo for a repaint, because the repaint happened to the layer, not the state. Recovery is Edit > Undo, the history panel, or an earlier saved copy. The comp was never a version.
What are honest ways to handle a new product image that only one variant should show?
You cannot record that as a state of the existing single layer. One route is to duplicate the Smart Object into per-product layers, line them up, and record visibility per comp. Another is to give the route its own source file when the products need different crops, retouching and frames. That costs duplication of type and rules, which will drift.
Are layer comps backups if a layer is deleted or merged?
No. Adobe's documentation warns that deleting, merging or converting layers can prevent a stored state from being restored, and clearing a warning does not restore deleted content. Recovery runs through an intact source or backup, or by rebuilding the layer and updating affected comps. The comp has nothing to restore from.
How should you verify and hand over a multi-variant file?
Reopen the file, export the intended comps, name each export so it maps directly onto its comp name, and compare them under matching conditions: same viewer, zoom, background and ideally display. Check image and label together. Also leave a shared-base note about which layers every comp depends on and a plain sentence about whether routes live in one file as states or in separate sources.