共有:
Midjourney V8 Edit Model

Three editing tools became
one.

Keeping a style meant Omni Reference. Keeping a character meant Character Reference. Touching up a region meant a separate Editor. Midjourney's fragmented image-editing workflow now lives in a single interface with the new "Edit Model."

AI Navigate Editorial·2026.09.15·6 min read
V8.x — separate tools Omni Reference style consistency Character Reference character consistency Editor inpaint / outpaint Edit Model V8.2 — one unified interface
01
Why Now

Why fragmented editing tools
finally became one

Midjourney announced "Edit Model for V8" on its official updates blog, revealing that the editing features scattered across V8.x had been consolidated into a single model. Under V8.x, keeping a generated image's style and composition consistent meant using the "Omni Reference" parameter, while keeping a specific character's identity consistent meant switching to "Character Reference." Repainting part of an image (inpainting) or expanding the canvas (outpainting) required moving to a separate "Midjourney Editor" screen equipped with Pan, Zoom Out, and Vary Region (a region-select erase/change tool).

The new Edit Model brings these three roles — following written editing instructions, combining multiple reference images, and inpainting/outpainting — together into one unified interface. According to the official documentation, Pan, Zoom Out, and Vary Region are now all available on the same screen, removing the context-switching cost that came from constantly asking "which parameter, which reference image, which setting" every time you swapped tools.

Before (V8.x, separate tools)After (Edit Model, unified)
Style consistency set separately via Omni ReferenceFed directly to Edit Model as a reference image
Character consistency set separately via Character ReferenceCombined with up to 4 images in the same reference slot
Touch-ups and expansion on a separate Midjourney Editor screenPan, Zoom Out, and Vary Region unified on one screen
Switching parameters and screens per use caseEverything completed inside one Edit Model

Editing stops being about choosing a tool,
and becomes shaping intent directly.


02
What's New

Three capabilities, now folded
into one screen

Text-instruction editing, combining up to four reference images, and canvas editing — once separate operations, now continuous in the Edit Model.

Reference images (up to 4) Edit Model Unified in one generation
FIG. Up to four reference images, once separate parameters, are now composited by the Edit Model into a single generation
01

Edit with a written instruction

Just write a plain-language instruction against an existing image and the Edit Model changes it accordingly. No more switching to a different parameter first.

02

Combine up to four reference images

Omni Reference (formerly used for style consistency) and Character Reference (formerly used for character consistency) are now merged into the Edit Model, letting you specify up to four reference images at once to generate a single new image.

03

Inpaint and outpaint on the same screen

Pan (reposition the view), Zoom Out (expand the canvas), and Vary Region (change or erase a selected area) are now built into the Edit Model interface itself, with the same feel as the previous Midjourney Editor.

Combine Moodboards, Personalization, and Style References together and you can also convert an existing image into a different style — keeping the same composition while swapping out the look, using a targeted moodboard, a previously trained personalization profile, and a style reference all at once.

03
By The Numbers

The scale of the consolidation, in numbers

3 → 1
Omni Reference, Character Reference, and Editor merged into one model
up to 4
reference images combined into a single generation
1 screen
Pan, Zoom Out, and Vary Region on one interface

Midjourney isn't moving alone. That same week, OpenAI also shipped a similar precision-editing idea with GPT Image 2.5's "Sunburst" mode, which edits a targeted area while preserving the rest of the image — suggesting a broader industry pull toward consolidating fragmented editing features into a single model. The implementation details of Sunburst are limited from what's publicly confirmable at the time of writing, so it's mentioned here only as context.

04
Who Benefits

Who benefits, and how

Designers, marketers, and engineering teams each see the payoff differently.

Designers: faster concept iteration

Testing several directions from a rough concept used to carry a decision cost — "Omni Reference to hold the style, or Character Reference to lock the character?" With Edit Model you just swap the reference image and iterate, shortening each review cycle.

Marketers: easier on-brand asset variation

Feed an existing key visual as one of up to four references and it's easier to mass-produce variants that change only copy or layout. Well suited to "scale without breaking" work — keeping the brand's world (moodboard, personalization settings) intact while only the look changes.

Engineering teams: simpler tool integration

For teams building internal tools, moving from separate parameters for referencing, editing, and canvas operations to a single model matters. Fewer branches in call logic, and lower maintenance cost.


05
What Comes Next

What to watch next, and where to be careful

Three things are worth watching in the short term.

  1. Whether actual generation cost (credit consumption equivalent to GPU time) changes compared to the old Omni Reference and Character Reference. The official documentation explains the consolidation but doesn't fully spell out pricing changes, so operations teams should verify against their own usage.
  2. How much breakage (identity drift on faces, style conflicts) shows up when combining four reference images at once — worth testing with real production assets.
  3. How to position this against competing precision-editing modes such as OpenAI's GPT Image 2.5 "Sunburst" within an internal creative workflow.

This shouldn't be read with blind optimism. Folding three features into one lowers the learning curve, but it's unclear from the public announcement and documentation alone how precisely the fine-grained control once offered by separate parameters carries over into the unified interface. For commercial work that demands strict character identity, we'd recommend running a side-by-side comparison against the existing workflow before migrating.