Anyone who has managed dependencies will recognize the shape of this problem, even without touching an image generator.
I spent an afternoon running the same original character through Midjourney and PixAI, and the interesting result had nothing to do with image quality. It was a compatibility matrix.
The test subject
One character, described once in plain language: an adult woman in her mid-thirties, cropped ash grey hair with a thin braid, a scar through the left eyebrow, steel blue eyes, a brass monocle on a chain, a heavy navy coat with a high collar, a leather wrap on her right forearm, and a small brass clockwork falcon on her left shoulder.
Eight checkable attributes. Same description on both platforms, no cherry-picking between them.
The matrix
Midjourney's version dropdown, as of early August 2026, runs from 1 through 8.2, with 8.2 as the default since July 24. Below a divider sit the anime models: niji 7, niji 6, niji 5, niji 4. The compatibility that matters for character work looks like this:
feature available on
-------------------------- --------------------------------
current default model 8.2
anime models (niji) stops at niji 7
Omni Reference (character) version 7
Character Reference (old) version 6
editor, pan, zoom documented as running on 6.1
Read that as a dependency graph, and the problem is visible before you generate anything. The newest model, the anime models, and the character lock resolve to three different versions.
What the runtime actually does
Three behaviors showed up in testing that the matrix alone does not tell you.
Loading a reference silently changes your model. Midjourney's documentation states that adding a reference image runs the prompt in version 7. My reference runs came back in that model's rendering style rather than the painterly output the default model had produced minutes earlier. Nothing in the flow asks whether that tradeoff is acceptable.
The anime models reject the parameter outright. Loading a reference on niji works, and then a line comes back saying niji does not support OW, the weight setting that controls reference strength. Style reference is offered instead, and a style reference transfers a look rather than an identity.
Reference state does not persist. The reference has to be attached again for every run. I changed the scene, generated, and got a different woman: brown wavy hair instead of ash grey, different face, different age. Zero warnings, zero errors, just a batch produced without the input I assumed was still bound.
Set up correctly, version 7 handled the character well across two scene changes. The hair, the build, and the coat carried over. The brass falcon arrived as an ordinary bird every time, and the clothing color drifted from run to run.
The other path
PixAI approaches this as one runtime rather than a matrix. You pick an anime model, Tsubaki.2 in my case, and the reference tools, the LoRA layer, and the editing tools sit in the same generation panel. A LoRA is a small add-on file trained over a base model that teaches it a style, a character, or a detail treatment, and the platform supports both community LoRAs and training your own.
The result I did not expect: running the same written description across three scenes with no reference image loaded produced the same person each time. Market at noon, workshop at night, rain on a pier. Different outfits, different expressions, and the identifying details held, brass fittings on the falcon included.
It is imperfect. The scar migrated to her cheek in one image and coat details vary. What it removes is state management: nothing to re-attach, no version to switch, no feature that exists on one branch and not another.
When each one is the right call
Midjourney remains excellent, and for single images or style exploration the version matrix never comes up, because you stay on one model and generate. Its aesthetic tooling is deeper than most, and it needs a paid subscription before the first image, starting at ten dollars a month.
The matrix starts costing you when a character has to survive twenty images across six months. At that point, the question stops being which model renders better and becomes how much setup stands between you and image number twenty.
If that is the work you are doing, see how far one description gets you in PixAI. The quick start guide covers the interface basics.
Top comments (0)