CartVisualCreate account

Why Does My Midjourney V7 Omni Reference Fail in V8 Product Images?

A seller may have a V7 Midjourney recipe using an Omni Reference to guide a product’s appearance. For V7, Omni Reference uses one reference and can be supplied through the appropriate image interface or the --oref parameter in Discord.

Published · By CartVisual editorial team

Read the version before debugging the reference

A seller may have a V7 Midjourney recipe using an Omni Reference to guide a product’s appearance. Copying that recipe into V8.X is not a model-neutral migration. Midjourney explicitly limits Omni Reference to V7 and directs V8.X work toward its Edit Model, which documents support for up to four reference images. V7 remains a distinct route; the issue is compatibility, not proof that every earlier image or workflow has been retired. Preserve the old prompt and source image before changing model versions.

Rebuild the input contract rather than translating one flag

For V7, Omni Reference uses one reference and can be supplied through the appropriate image interface or the --oref parameter in Discord. The older reference weight and related prompt behavior should not be assumed to transfer to V8 Edit Model. Inspect the current V8 interface, attach only authorized source images, and define which image is authoritative for the product. The fact that V8 supports more images is not evidence that four references outperform one, or that their roles are automatically resolved. A visual source may suggest an appearance without preserving an exact SKU.

Fictional migration: a travel bottle

An accessories seller has a V7 concept with a travel bottle and warm kitchen setting. The approved source shows a particular cap shape and a vertical measurement scale. The team wants a new V8.X scene without losing those details. The old V7 Omni setup is kept as a historical recipe. The proposed V8 route uses Edit Model with the approved bottle source and, only if needed, a separate scene reference. The reviewer writes down that the bottle image is product evidence and the kitchen image is atmosphere. No Midjourney generations or comparison were executed.

Decide what constitutes failure

If the V8 result changes the cap, reject it for that SKU even when the scene looks appealing. If the lighting is unsuitable but the bottle remains accurate, revise the scene instructions or supporting visual reference without replacing the authoritative bottle source. If the request fails before generation, inspect the selected model and actual reference mode rather than assuming a V7 parameter is supported. If the merchant needs reversible product positioning after editing, preserve the source composition separately: submitted composite layers explains the flattening boundary.

Approve the migration as a new workflow

Record model version, input mode, source-image revisions, visible prompt, expected product features, result identity and reviewer decision. Do not call the migrated output a reproduction merely because it resembles the old image. The separate reference roles guide discusses another provider’s model-specific inputs, not Midjourney limits. CartVisual image remix can be a separate creative starting point but does not expose Midjourney Omni or Edit Model controls. Release only after checking the actual product and intended destination.

Sources

  • Midjourney version-specific references — official help — Omni Reference only V7, one reference; V8.X Edit Model replaces it and supports up to four. Version-specific route migration, not generic reference advice. Verify exact current compatibility; do not call V7 universally retired. Source checked 2026-11-16.

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. Fictional examples only; no third-party account accessed, output generated, export executed or product fidelity measured.

Related decisions

Explore the AI image remix workflow