Midjourney V8.2 is being promoted this week as newly available. Midjourney’s own documentation says it "released as the default version on July 24, 2026."
That gap is not a scandal. It is a useful reminder that a marketing email announces attention, not availability, and that the vendor’s docs are a better source than the vendor’s mailing list. If you have generated anything on Midjourney since late July without specifying a version, you have already been using this model.
What the documentation says changed
Working from the model versions reference rather than the promotional copy, the summary is short.
V8.2 focused on "aesthetics, image quality, and Personalization." The characterization of the output is that "V8.2 images are more creative, bold, sophisticated, and edgy." Personalization now understands aesthetic tastes better, with the documentation noting this applies especially to profiles with substantial activity. Moodboards are supported.
That is the whole documented delta. There is no benchmark, no comparison table, no measured claim of any kind, which is normal for this category and worth registering rather than glossing over.
The promotional framing adds that this is the biggest aesthetic improvement in more than a year. Treat that as a vendor characterization of its own taste, because that is exactly what it is.
V8.1 was the default for six weeks
The version history is more interesting than the feature list, and it is where the useful planning information lives.
V8.1 released on April 14, 2026 and became the default on June 10. V8.2 took over on July 23 and 24. So V8.1 held the default position for roughly six weeks after waiting nearly two months to get it.
V8.1’s pitch was speed: the docs describe it as "our fastest model so far, with standard jobs rendering about 4–5 times faster than earlier versions," along with strength at "reading your prompt and holding on to small details." Our look at what V8.1 brought covered that release.
Read the two together and a pattern appears. V8.1 optimized for speed and prompt fidelity. V8.2 optimizes for aesthetics and personalization. Those are not the same objective, and a model tuned to be "bold" and "edgy" is not obviously the model you want when you need it to follow a long, constrained brief exactly. If your workflow depends on precise adherence rather than flair, that is worth testing rather than assuming the newer default is better for you.
--v followed by the version number to the end of a prompt selects a specific model. If your pipeline was tuned against V8.1 output, pin it and change deliberately rather than discovering the new default through a batch that no longer matches your house look.
Personalization is the real feature, and it has a prerequisite
Here is the part that deserves more attention than the aesthetics headline, because it changes who benefits.
The documentation is specific that improved Personalization applies especially to profiles with substantial activity. Read plainly, the headline capability of Midjourney V8.2 works best for people who have already used Midjourney a great deal.
That is technically reasonable. A system inferring your taste needs evidence of your taste, and there is no way around that. But it has consequences that nobody selling it will lead with.
A new account gets the aesthetic changes and comparatively little of the personalization benefit. An agency onboarding a new client, or a team spinning up a fresh workspace for a project, starts from the same cold position. And the improvement is not portable: it lives in a profile, on a platform, attached to a history you cannot export. The better it gets, the more it functions as a switching cost.
That is worth naming clearly. A feature that improves with accumulated history is also a feature that penalises leaving, and it is the same dynamic we traced when a neutral routing layer changed hands: the useful thing and the sticky thing are the same thing.
Aesthetic claims cannot be checked, and that is the point
Every serious model release in the past year has come with numbers. Coding benchmarks, reasoning evaluations, context measurements. We have written repeatedly about how those numbers need their evaluation conditions before they mean anything.
Image aesthetics have no equivalent. There is no FrontierCode for taste. "More creative, bold, sophisticated, and edgy" is not a measurement and cannot be made into one, and a competitor could ship an identical claim tomorrow with equal justification.
So the honest position is that the only evaluation that matters here is your own, run on your own prompts, against your own output from the previous version. That is more work than reading a score and it is the only thing that will tell you whether Midjourney V8.2 is better for what you actually make. The same is true across this category, which is why our comparisons of Recraft and other generators lean on capability differences rather than quality rankings.
What Midjourney V8.2 does not change
Worth being clear about the boundaries of this release, because a default-model change is easy to over-read.
The documented delta covers aesthetics, image quality and Personalization. It does not describe changes to plans or pricing, and Midjourney’s site and documentation present the version as one option among several rather than a replacement for everything before it. Older versions remain selectable.
It also does not close the capability gaps that decide tool choice for a lot of production work. If you need editable vector output, reliable typography inside an image, or a specific licensing posture, those are selection criteria that a taste improvement does not touch. Teams tend to pick an image generator on what it can produce structurally, then argue about aesthetics second, and this release only moves the second thing.
The trap personalization sets for anyone producing in batches
This one is first-hand, and it is the argument I would most want a working team to take away.
This publication generates its own featured images from written prompts. We keep a documented rule requiring variation across six axes: format, camera, scale, light, ground and subject, with no more than two repeated values per axis in a batch. That rule exists because of a specific failure. A run of ten images once passed a medium-only variety check with ten different materials, and every single one turned out to be an overhead macro photograph of a handmade object under raking light. Ten distinct media, one visual idea, and it looked like a template.
Now consider what a system that adapts to your taste does to that problem. It optimizes toward the choices you have already made. If your history is full of moody, high-contrast, shallow-focus compositions, a personalization profile will read that as your taste and give you more of it, more reliably, with less prompting effort.
For a single striking image, that is exactly what you want. For a body of work published on a schedule, it is a monotony engine with better manners. The tool gets better at producing the thing you have already produced, which is the opposite of what a batch needs.
The mitigation is not to avoid personalization. It is to keep an explicit variation discipline that lives outside the model, in your brief, so that the axes are set by an editorial decision rather than inferred from history. Moodboards help here precisely because they are deliberate: you are choosing the reference rather than accumulating one.
What to do this week
Five positions, in the order I would take them.
Check what you have been generating since late July. If you did not pin a version, it has been V8.2. Any drift in your house look since then has an explanation.
Run your own before-and-after. Same prompts, --v 8.1 and --v 8.2, on work that represents your actual output. That is twenty minutes and it settles the question better than any writeup, including this one.
Decide whether you want flair or fidelity. V8.1 was built around speed and holding small details. V8.2 is built around aesthetics. If your prompts are long and constrained, the older model may still serve you better, and you can pin it.
Treat the personalization profile as an asset with a lock-in cost. It improves with history, does not travel, and quietly raises the price of switching platforms. Worth knowing before it becomes load bearing.
Keep your variation rules outside the tool. A model that learns your taste will reinforce it. If you publish in volume, the discipline that stops everything looking the same has to be written down somewhere the model cannot see.
One footnote worth carrying into any AI image workflow this year: provenance metadata such as C2PA is separable from the file and routinely stripped by upload pipelines, so do not assume a generated image arrives anywhere still carrying its origin. Our explainer on how AI content watermarking works covers why.
Frequently Asked Questions
When did Midjourney V8.2 actually launch?
Midjourney’s model versions documentation states that V8.2 released as the default version on July 24, 2026. Promotional messaging circulating in mid-August describes it as newly available, which reflects a marketing push rather than a release date. If you have generated images without specifying a version since late July, you have been using V8.2.
What changed in V8.2?
Per the documentation, the release focused on aesthetics, image quality and Personalization, with output characterized as more creative, bold, sophisticated and edgy. Personalization is described as understanding aesthetic tastes better, particularly for profiles with substantial activity. Moodboards are supported. No benchmark or measured comparison is published, which is standard for image models.
How do I use a specific version?
Add the version flag to the end of your prompt, in the form of two dashes followed by v and the version number. That lets you pin an older model deliberately rather than following whatever the current default is, which matters if a pipeline was tuned against a particular version’s output.
Should I switch from V8.1?
Test rather than assume. V8.1 was built around speed and holding small details from your prompt, while V8.2 is tuned for aesthetics. Those are different objectives, and a model optimized to be bold is not automatically better at following a long constrained brief. Run the same prompts through both and compare against work that represents your real output.
Why does personalization work better for some accounts?
Because it infers your taste from what you have already made, so it needs history to work from. The documentation notes the improvement applies especially to profiles with substantial activity. New accounts, new client workspaces and fresh team setups therefore see less of the headline benefit until they have built up a record.
Does personalization make my images less varied?
It can, and this is worth planning for if you publish in volume. A system that adapts to your taste optimizes toward choices you have already made, which is ideal for one striking image and unhelpful across a body of work that needs to look different from itself. Keeping an explicit variation rule in your brief, rather than relying on the model, is the practical answer.
Can I move my personalization profile elsewhere?
No mechanism for that is documented. The profile is tied to your account and accumulates from your usage there, so its value grows the longer you stay and does not transfer if you leave. That is worth factoring into platform decisions before the profile becomes something you would be reluctant to lose.
How should I evaluate an image model with no benchmarks?
On your own prompts, against your own previous output, judged by whoever signs off your work. There is no aesthetic equivalent of a coding benchmark and vendor descriptions of their own taste are not measurements. Comparing capability differences, such as text handling, vector output or format support, is more tractable than comparing quality claims.
