Midjourney V8 vs V7: What Changed, and What You Lost (2026)
Midjourney's current default model is V8.2, which became the default on July 24, 2026. If you were still running V7 — the default from June 17, 2025 to June 9, 2026 — most of what you'll read about the jump to V8 focuses on speed and image quality. That part is real: V8.1 renders roughly 4-5 times faster than earlier versions and introduced native HD output. But Midjourney's own feature compatibility chart shows something most coverage skips over. Moving to V8 doesn't just add capability — it removes tools V7 supported, including Omni Reference, Draft Mode, Turbo Mode, and the Quality parameter. If your workflow leans on any of those, "just switch to V8" is not a clean upgrade. Here's what actually changed, sourced entirely to Midjourney's Version documentation.
How we got to V8.2
The version history matters here because "V8" isn't one static thing — it's already had three releases. V8.0 launched as an early access alpha on March 17, 2026, available only on the separate Midjourney Alpha website until it was retired on July 24, 2026, the same day V8.2 became the default. Images generated under V8.0 stay in your website gallery, but the version itself is no longer available to run. V8.1 followed on April 14, 2026, and served as the default from June 10 to July 23, 2026. V8.2 replaced it as default on July 24, 2026, and is the version referenced through the rest of this article unless a feature is specific to V8.1.
Before that, V7 released April 3, 2025 and was default from June 17, 2025 to June 9, 2026 — the version this comparison is measured against. V7's own headline additions were Draft Mode and Omni Reference, both of which are relevant below because neither survived into V8. Further back, V6.1 (July 30, 2024) ran roughly 25% faster than V6 and was default until June 16, 2025; V6 itself (December 20, 2023) was default from February 14 to July 30, 2024. Separately, Midjourney also spun off Niji 7 on January 9, 2026 as its own anime and illustrative model, built with Spellbrush, with its own website and Discord rather than living inside the core version lineup.
What V8 actually gained
The speed and quality gains are genuine and documented. V8.1 is described in Midjourney's docs as its fastest model so far, with standard jobs rendering about 4-5 times faster than earlier versions. It's also better at reading prompts and holding onto small details, and it added a Raw toggle that strips out default styling for closer prompt adherence when you want it. Note that using V8.1 may require unlocking your Global V7/V8 Personalization Profile first.
The more concrete addition is HD: V8.1 introduced native 2048px image generation without a separate upscaling pass. You can toggle it in the Version section of the web settings panel, or attach --sd or --hd directly to a prompt. On the web, a "Run batch as HD" button lets you rerun a seedlocked standard-definition (SD) image in HD instead of retyping the prompt. HD isn't free in generation time — it costs 1.3 minutes of GPU time against 0.8 minutes for an SD job. One workflow wrinkle worth knowing up front: running inpainting or outpainting tools — Pan, Zoom Out, or Edit/Vary Region — on an HD image downscales the result back to SD; running an Upscale option afterward brings it back to HD resolution.
V8.2, the version live now, is aimed squarely at aesthetics rather than mechanics. Midjourney's documentation describes V8.2 output as "more creative, bold, sophisticated, and edgy," and says Personalization now "understands" a user's aesthetic taste significantly better, particularly on profiles that already have a large number of points logged. Building a new Personalization profile for V8.2 also draws from what the docs call a much larger and improved pool of images to choose from.
What you actually lose moving from V7 to V8
This is the part that gets buried under "V8 is faster and prettier" coverage. Midjourney's compatibility chart lists several features V7 supported that are simply absent from V8 — not degraded, not renamed, gone. The clearest case is Omni Reference and Omni Reference Weight, the tools V7 introduced for carrying a reference subject's likeness consistently across generations. Both are marked unsupported on V8, and the chart specifically notes they still "Use V7" — meaning the only documented way to keep using Omni Reference is to run that part of your workflow on the older version.
Draft Mode, also introduced with V7, doesn't carry over either. Neither does Turbo Mode, which had been available on both V6 and V7. The Quality parameter — which let V7 users dial rendering quality with values like 1, 2, or 4 — isn't supported on V8 at all. Niji version switching is gone too: V7 supported --niji 7 directly, but V8 doesn't list Niji version support in the chart, consistent with Niji 7 now existing as its own separate product with its own website and Discord rather than a flag inside the core Midjourney versions.
There's a subtler change in the Seed parameter. It's still supported on V8, but Midjourney's own chart flags it with a caveat — "(99% identical)" — that doesn't appear next to V6 or V7's seed listings. Practically, that means reusing a seed on V8 won't reliably reproduce a pixel-identical image the way locking a seed has typically been understood to work. And on aspect ratio: the maximum of 14:1 holds across versions, but HD images on V8 are capped at a 4:1 maximum aspect ratio — a real constraint if you're generating ultra-wide or panoramic compositions and want them in HD.
Two features often assumed to be V7 losses actually aren't — they were already gone before V7 existed. Character Reference and Character Weight were V6 features that V7 itself didn't support, and Multi-Prompting was also a V6-only capability absent from V7. If your workflow already adapted to their absence under V7, nothing changes there moving to V8. The real losses are specifically the tools V7 added or kept and V8 then dropped: Omni Reference, Omni Reference Weight, Draft Mode, Turbo Mode, the Quality parameter, and direct Niji switching.
Feature comparison: V7 vs V8
| Feature | V7 | V8 (V8.1 / V8.2) |
|---|---|---|
| Omni Reference | Yes | No (Uses V7) |
| Omni Reference Weight | Yes | No (Uses V7) |
| Draft Mode | Yes | No |
| Turbo Mode | Yes | No |
| Quality Parameter | Yes (1, 2, 4) | No |
| Niji Version (--niji 7) | Yes | No |
| Seed Parameter | Yes | Yes ("99% identical") |
| HD Images (2048px) | No | Yes (1.3 min GPU cost) |
| Max Aspect Ratio | 14:1 | 14:1 (4:1 for HD) |
| Variations, Remix, Style Reference, Style Weight, Image Prompts, Chaos, Raw, Stylize, Tile, Weird, Personalization, Moodboards, Relax/Fast/Conversational Mode | Yes | Yes |
| Pan, Zoom Out, Editor | Yes | Yes (runs on V6.1) |
That last row is easy to miss: per Midjourney's chart, Pan, Zoom Out, and the Editor tool don't actually run on V8's engine at all — they fall back to V6.1 even when you're editing a V8-generated image. Functionally they still work, but the model doing the work behind those specific tools isn't the one that generated your image.
Should you switch? It depends on what you actually use
Because Midjourney lets you set a version per prompt with --v # rather than forcing an account-wide switch, the honest answer for most people is "use both," not "pick one." What matters is knowing which parts of your workflow break if you default to V8.
Character-consistency workflows. If you've built a process around Omni Reference to keep a recurring character or subject consistent across a shoot, that tool is not available on V8 — the compatibility chart marks it "Uses V7" specifically. The documented option is to keep running those particular prompts with --v 7 appended, rather than assuming V8's Personalization features substitute for it; Personalization and Omni Reference are described as separate, differently-scoped tools in the chart.
Print and high-resolution work. V8's native HD output (2048px, no separate upscale step) is a genuine upgrade over V7, which had no equivalent. But two caveats apply directly to print use: HD is capped at a 4:1 aspect ratio, tighter than the 14:1 ceiling for standard images, which matters for panoramic or ultra-wide formats. And if your process involves inpainting or outpainting — Pan, Zoom Out, Edit/Vary Region — those tools downscale an HD image back to SD, requiring an extra Upscale pass afterward to get back to full resolution. Budget that extra step into a production pipeline rather than assuming HD stays HD through every edit.
Discord power users running Draft Mode or Turbo Mode. Both are absent from V8 per the chart. If your habit was fast, low-cost Draft Mode passes to rough out an idea before committing to a full render, that specific mode doesn't exist on V8 — you'd be relying on V8.1's baseline speed increase (roughly 4-5x faster than earlier versions on standard jobs) instead, which is a different mechanism than a dedicated draft toggle and won't behave identically.
Casual and general-purpose users. This is where the switch is closest to a straightforward upgrade. Variations, Remix, Style Reference, Style Weight, Image Prompts, Moodboards, Personalization, Chaos, Raw, Stylize, Tile, Weird, and Relax/Fast/Conversational Mode are all still supported on V8 per the chart. If your prompts don't touch Omni Reference, Draft Mode, Turbo Mode, the Quality parameter, or --niji switching, there's little reason not to run on the current default and pick up V8.2's aesthetic and Personalization improvements along with V8.1's speed gains.
If you're weighing Midjourney against other image generators rather than just choosing a version, our Midjourney review and Best AI Image Generators roundup cover how it compares more broadly, and Best Free AI Tools is a starting point if budget is the deciding factor. For a general primer on evaluating AI tools before you commit to one, start with our AI Tools Starter Guide.
Frequently asked questions
What did Midjourney V8 actually gain over V7?
Per Midjourney's Version documentation, V8.1 is Midjourney's fastest model so far, with standard jobs rendering about 4-5 times faster than earlier versions, plus better prompt reading and small-detail retention, and a Raw toggle to reduce default styling. V8.1 also introduced HD, native 2048px image generation without upscaling. V8.2, the current default since July 24, 2026, focuses on aesthetics and Personalization — Midjourney's docs describe V8.2 images as more creative, bold, sophisticated, and edgy, with Personalization understanding a user's aesthetic taste more accurately, especially on profiles with a large number of points.
What did Midjourney V8 remove that V7 users relied on?
According to Midjourney's own feature compatibility chart, V8 dropped Omni Reference and Omni Reference Weight (V7's tools for keeping a reference image's subject consistent across generations), Draft Mode, Turbo Mode, the Quality parameter, and direct Niji version switching via --niji 7. All of these were present and supported on V7. The chart marks Omni Reference specifically as "Uses V7," meaning it only functions if you fall back to that version.
Can I still use Omni Reference on Midjourney V8?
Not on V8 itself. Midjourney's compatibility chart lists Omni Reference and Omni Reference Weight as unsupported on V8, with both marked "Uses V7." If a workflow depends on Omni Reference for character or subject consistency, the documented path is to add --v 7 to the relevant prompts rather than expect the feature to work under the V8 default.
Is Midjourney V8 faster than V7?
Yes, according to Midjourney's documentation. V8.1 is described as Midjourney's fastest model so far, with standard jobs rendering roughly 4-5 times faster than earlier versions. V8.1 also introduced HD, generating higher-resolution 2048px images without a separate upscaling step; HD costs 1.3 minutes of GPU time versus 0.8 minutes for a standard (SD) job.
How do I switch between Midjourney V7 and V8?
Add --v # to the end of a prompt in the Imagine bar or in Discord to run that one generation on a specific version — for example --v 7 or --v 8. To change your account's default version instead, use the Version section of the settings panel on the web, or the settings command in Discord. Version selection is per-prompt, so you don't have to commit one version to your entire workflow.