You ask an AI image editor to change one jacket to blue. Ten seconds later, the face looks different, the lighting shifted, and somehow the background changed too. This Reddit user in r/PromptEngineering, u/AbbreviationsLeast35, ran into that same problem so many times they finally cracked the pattern that stops it.
Here’s the shift. Stop telling the model what to change. Start telling it what to leave alone. Every prompt gets a target and a locked list of things that have to survive the edit untouched.
Old Way vs New Way 🔄
The old way: type the change and hope. “Change the jacket to blue” sounds precise enough, but the model has no idea what counts as “everything else.” Editors like GPT Image don’t touch a layer and leave the rest alone. They re-render the whole frame from scratch, every single time. No memory of the original, no protected zones, just a fresh guess at the entire image based on your words. That’s why a one-line edit can turn into a full reroll: the model isn’t editing pixels, it’s painting a new picture that happens to resemble the old one, and resemblance is not the same as preservation.
The new way: treat every edit as two lists, not one. The first list has exactly one item, the thing you actually want changed. The second list spells out everything the model isn’t allowed to touch: identity, pose, background, lighting, crop. The model can’t protect what you never asked it to protect, so you ask. It sounds almost too basic to matter, but that’s the whole trick: you’re not making the model smarter, you’re removing the guesswork it was never equipped to handle on its own.
The Four-Part Structure
The original poster’s pattern breaks into four pieces:
- 🎯 TARGET, the one change, stated precisely. Not “make it better,” but “change the jacket to blue.”
- 🔒 KEEP, an explicit list of immutables, each phrased “exactly as in the source”: face, pose, background, lighting, camera and crop.
- ✅ Lock line, one closing sentence: “keep everything else exactly as in the source image, unchanged.”
- Restate, for whole-frame renderers like ChatGPT. The model has no memory of what it just drew, so you re-describe the immutables inside the edit itself, not as a separate instruction.
Each piece is doing a different job, and skipping one usually shows up as a specific failure. Drop the KEEP list and you get random drift. Drop the lock line and the model treats your immutables as suggestions instead of constraints. Skip the restate step on a whole-frame renderer and you’re relying on a memory the tool simply doesn’t have.
Here’s the pattern applied to a real edit. Instead of typing “add falling snow,” it becomes this:
Add falling snow as atmosphere only. Keep the buildings, road, and their surfaces exactly as in the source. Don’t accumulate snow on any surface unless asked.
That’s the difference between snow drifting into every corner of the frame, changing textures and colors along the way, and snow that stays exactly where it’s supposed to be: floating in the air, not repainting the scene underneath it. The same structure works for weather, lighting swaps, clothing changes, and prop additions. It’s one template, applied consistently.
I’ve burned way too many re-rolls chasing a face that wouldn’t stay put after a one-line edit request. This structure is the kind of thing that feels almost too simple until you see the before-and-after, and then it’s hard to go back to writing single-sentence prompts.
What the Comments Added
A commenter named riverlane72 flagged a detail worth stealing: order matters inside the KEEP list. Put identity and face first, and the model seems to weight it more heavily than if it gets buried at the bottom of the list. Small change, easy to test on your own edits, and cheap enough that there’s no reason not to try it on the next batch you run.
Another commenter, According-Stable4487, pointed out where this pattern gets harder to hold: batch generation. Run nine images off one fixed scaffold and vary only the setting, and the people in the shot can quietly drift too, even when everything else about the request stayed the same. Single edits are one problem. Series are a different one, and the fix probably needs its own KEEP list per batch, not just per image. Worth remembering before you queue up a run and assume the first image’s fidelity carries through to the ninth.
Try It On Your Next Edit
Next time you’re fighting an AI editor that keeps redrawing a face you never asked it to touch, skip the one-line request. Write the TARGET, write the KEEP list, close with the lock line, and if you’re on a whole-frame renderer, fold the immutables back into the edit itself.
The original thread has more back-and-forth on which immutables people lose most often, worth a scroll if this pattern saves you a re-roll or two.
Frequently Asked Questions
Q: How do I keep the same people consistent when generating multiple images in a series?
Instead of just listing what to vary (like the setting), create an explicit CHANGE list for each variable you want different, ethnicity, hair color, outfit, camera distance. Stack these changes together rather than listing a single trait, since single traits can get averaged away by the model. Pair this with your KEEP list to lock everything else.
Q: Does the order I list things in the KEEP section actually matter?
Yes. Putting identity and face first in your KEEP list gives them more weight than burying them at the end. Lead with the most critical immutables to help the model prioritize preserving them.
Q: How do I stop the model from accidentally creating split panels when I mention two different locations?
Add an explicit safeguard to every prompt: “one single unified image, not a diptych or split panel.” Whole-frame renderers can silently create two-panel images when multiple locations are mentioned without this guard.
Q: Why does aspect ratio drift when I edit the same image multiple times?
Aspect ratio isn’t locked between edits unless you explicitly pin it in words each time. Add your desired ratio (e.g., “portrait 2:3 format”) to every prompt in the series, not just the first one.
The prompt pattern that stops AI image editors from changing everything when you only wanted to edit one thing
by u/AbbreviationsLeast35 in PromptEngineering