Midjourney V7 Not Working: Bugs, Errors and Fixes (2026)

V7 is Midjourney's biggest architectural shift in two years. Which means it also breaks in new and exciting ways that V6 users weren't prepared for.

I've been testing V7 since it rolled out and have hit most of these errors firsthand. Some are real bugs. Some are V6 habits that don't transfer. Here's how to tell the difference — and fix both.

The V7 vs. V6 Mental Model Shift

Before getting into specific errors, this is worth understanding: V7 isn't just V6 with better output. It's a different system. The parameter behavior changed. The queue architecture changed. The upscale pipeline changed.

If you're getting frustrated because V7 "doesn't work right," there's a real chance it's working exactly as designed — just differently than you expect. Some V6 prompting patterns don't translate directly. I'll call those out as I go.

Problem 1: Slow Queue — Images Taking 2+ Minutes

What you see: You submit a prompt and the bot just... sits there. The "Waiting to start" message hangs for 60, 90, 120 seconds or more.

Why V7 is slower: V7's diffusion model is substantially more complex than V6. The generation pipeline does more work per image. A 90-second generation time isn't a bug — it's normal for V7 at off-peak hours. During peak usage (roughly mid-afternoon to late evening Eastern), you can tack on another minute or two in queue.

Fixes:

• Switch to Fast mode. If you're on a paid plan with Fast hours remaining, /imagine jobs run in Fast mode by default but you can confirm with /settings. Fast mode cuts typical wait times roughly in half. Check your remaining Fast hours with /info.

• Use Turbo mode for iteration. If you're doing rapid iteration — testing prompts, trying variations — Turbo mode (available on Standard and above plans) costs 2x Fast hours but generates significantly faster. Worth it when you're in prompt-testing mode.

• Wait out peak hours. Sounds obvious, but V7 queue times during off-peak (midnight to 9am Eastern) are dramatically shorter. If your work isn't time-sensitive, schedule heavy generation sessions for off-hours.

• Check the status page. If your queue times are way longer than usual — 5+ minutes for a simple job — check status.midjourney.com. V7 server degradation events do happen.

Problem 2: --style Parameter Doing Nothing (or Wrong Thing)

This is the one that trips up V6 users the most.

What you see: You add --style raw or a style reference and the output looks identical to what you'd get without it, or it produces something totally unexpected.

The V7 parameter overhaul: Midjourney rewrote how style parameters work in V7. Here's the actual breakdown:

• --style raw — Still exists, but V7's default aesthetic is different from V6's. Raw in V7 doesn't produce the same output as raw in V6. V7's base aesthetic model is different enough that you need to recalibrate what "raw" means here.

• --stylize — This is actually your more powerful tool in V7. --stylize 0 gives minimal Midjourney aesthetic influence; --stylize 1000 gives maximum. If you were using --style raw in V6 to get more literal/less stylized results, try --stylize 0 to --stylize 200 in V7 instead.

• Style reference images (--sref) — V7 introduced improved style reference handling. If style references seem to be ignored, make sure your --sref URL is a direct image link (not a page link) and that you're using it in the correct position in your prompt.

• --style with text values — Some V6 style presets don't exist in V7. If you get "unknown style" errors, that preset was retired.

Fix: Don't port V6 style parameters directly to V7. Rebuild your style workflow using V7's --stylize range as the primary control. Use --sref for visual consistency across images.

Problem 3: Aspect Ratio Not Applying

What you see: You add --ar 16:9 but the output comes out square or at the wrong ratio.

V7 is stricter on syntax. Unlike V6, which was forgiving about parameter formatting, V7 enforces more precise syntax. Common causes:

1. Missing space before --: Write prompt text --ar 16:9, not prompt text--ar 16:9
2. Wrong separator: Use : not /. So --ar 16:9, not --ar 16/9
3. No space between parameter and value: --ar 16:9 not --ar16:9

Subscription tier limits also apply. Very wide or tall ratios (like --ar 21:9 or --ar 1:4) may be restricted on lower-tier plans. If you're on Basic, stick to more standard ratios.

Fix: Check your parameter syntax first — copy it from a working prompt if needed. If syntax is correct and it's still failing, try a more standard ratio to rule out tier restrictions.

Problem 4: Upscale Failing or Stuck

V7 upscaling is a different beast from V6. The quality is better. The process is slower and slightly more fragile.

What you see: You click the upscale button (U1-U4) and either nothing happens, the bot shows the job as queued indefinitely, or the upscale completes but the image is degraded.

The two categories of upscale failure:

Queue stuck / job never starts: If the upscale stays in "Waiting" for more than 4-5 minutes, the job has silently failed. This happens more in V7 than V6 because V7 upscale is compute-heavy and can time out during high server load.

• Fix: React with the same U button again to requeue. If it fails again, wait 15-20 minutes and retry.

Degraded upscale output: V7 has three upscale variants — Subtle, Creative, and the default. Subtle preserves the original more closely; Creative adds more detail but interprets the image more aggressively. If your upscales look wrong, you might be hitting Creative when you wanted Subtle (or vice versa).

• Fix: Be explicit about which upscale variant you want. If you just clicked U1 without specifying, you got the default. Try the Subtle variant button to get a more faithful upscale.

The degraded image issue specifically: V7 upscale at 2x can occasionally produce artifacts — strange texture patterns, smearing at edges — on images with very fine detail (hair, fabric, foliage). This is a known V7 issue, not user error. Lower --quality values in the original generation can sometimes help, counterintuitively, by giving the upscaler a slightly less complex base to work from.

Problem 5: V7 "Not Available" on Your Account

Some users report that V7 simply isn't showing as an option in /settings.

Why this happens:

• Free tier: V7 may not be available on free accounts. Midjourney has historically limited access to the latest version to paid subscribers first.
• Billing issue: If your subscription lapsed or had a payment failure, your account may have dropped to restricted access.
• Region: V7 rolled out in stages. Some accounts got it weeks after launch.

Fix: Run /settings in Discord. If V7 isn't listed, check your subscription status at midjourney.com/account. If you're on a paid plan and V7 still doesn't appear after a week of the rollout, contact Midjourney support.

Quick Fixes Summary

For V6-specific issues (if you've switched back), our Midjourney not working guide covers general troubleshooting. If you're evaluating whether the V7 upgrade is worth the wait on your specific use case, that's a different question — but the answer for photorealistic work and character consistency is generally yes.