Find every active style code
A merchant approves a warm paper-grain poster treatment, opens Midjourney Style Creator from a prompt containing that style, and develops a cleaner variation. The new preview looks different because the old and new style-reference codes can both be active. Midjourney explicitly says these codes stack rather than merge. The new code is not an in-place revision of the old code, and recording only the newest code cannot reconstruct the combined preview.
Write a complete, inspectable recipe
Use hypothetical codes 111111 and 222222 solely as placeholders, not as actual approved styles. Keep the descriptive prompt constant when comparing their effects:
| Variant | Illustrative prompt structure | Purpose |
|---|---|---|
| A: old only | ceramic soap bottle on a neutral plinth --sref 111111 --v 7 | Reference treatment |
| B: new only | ceramic soap bottle on a neutral plinth --sref 222222 --v 7 | Isolate new style |
| C: combined | ceramic soap bottle on a neutral plinth --sref 111111 222222 --v 7 | Review stacked-style appearance |
These strings illustrate the documented multiple-code structure; no prompt was submitted and no appearance outcome is claimed. Save the complete actual prompt copied from the Create Page, not just a screenshot of the newest code.
Distinguish previews from production output
Style Creator uses V7 to make its previews. The prompt entered there drives the preview content, while the style choices shape the code. A later production image with a different prompt, model version or composition may look different even when the style codes match. A preview is therefore not a guaranteed appearance contract for every downstream version.
| Mismatch | Check first | Action |
|---|---|---|
| New poster lacks the earlier warmth | Was only the new code copied? | Compare A, B and C with identical content prompt |
| Same codes, different product arrangement | Was the content prompt changed? | Separate composition from style evaluation |
| Production differs from Creator preview | Model version and full prompt | Review as a new version-specific candidate |
| Product label altered | Actual source versus generated pixels | Reject factual product mismatch; style codes do not preserve SKU identity |
Illustrative poster approval
For a fictional soap launch, the brand wants softer paper grain but identical bottle proportions. The reviewer would compare the three proposed recipes for grain, palette and contrast, then inspect bottle shape and logo independently. If combined style C best expresses the desired mood but invents a new cap, the image still fails the product check. Do not infer the preferred style from a visually attractive but inaccurate product.
Archive the recipe, not a supposed merged code
Record source poster revision, Creator session, both real codes, complete prompt, preview version, production version and selected candidate. Keep pricing and campaign text editable outside generated imagery. The poster destination guide covers print suitability; the Midjourney layer guide covers a different editable-state boundary. Neither replaces this stacked-code record. Style Creator previews use provider GPU time; this is a proposed small comparison, not a paid test.