Does --style raw Still Work in Midjourney? (2026 Answer)

TL;DR: Raw mode still works — the spelling changed. Midjourney documents --style raw only for V5 and V6. On V7, V8.1 and V8.2 the documented parameter is --raw, and the Version chart marks Raw as supported on all three. Use --raw. Verified against Midjourney's docs, August 25, 2026.

Does --style raw still work in Midjourney?

The feature works. The syntax you learned probably does not — at least not according to anything Midjourney publishes today.

--style raw appears in exactly one place in Midjourney's current help centre: the Parameter Version Compatibility table inside the Legacy Features article, where the "Style" row lists raw under the V5 and V6 columns and nothing under V7 or V8. That is it. I searched the whole help centre for the phrase on August 25, 2026 and no current article documents it.

Meanwhile the Raw article says: "Add --raw to the end of your prompt in the Imagine bar." The Parameter List has an entry called "Raw Mode" whose syntax is --raw. It contains no --style entry at all. And the Discord settings article states that clicking the RAW Mode button "automatically add[s] --raw to all your prompts."

So Midjourney's own tooling emits --raw. If you are on a current model, that is the token to type.

Here is the part I cannot tell you, and I would rather say so than guess: Midjourney does not publish whether --style raw is still accepted as an alias on V7 or V8. There is no deprecation notice, no alias table, and no parameter-error reference in the docs. Undocumented is not the same as broken. The parser may still swallow it, or it may error, or it may silently do nothing. The 30-second self-check further down settles it for your account.

Which Midjourney versions accept --style raw?

Directly: V5 and V6 are the only versions Midjourney documents it for. Everything from V7 onward uses --raw.

The table below merges two primary sources — the Legacy Features compatibility table and the feature chart in the Version article — both read on August 25, 2026.

Two honest wrinkles in that table, both of which are Midjourney's own inconsistencies rather than mine.

First, the Legacy table's V5 column lists raw, while the Raw article says raw mode is compatible with "versions 5.1 and later." Midjourney does not reconcile those two statements. If you are working in plain V5.0 for some reason, treat raw as unconfirmed.

Second, the Legacy Features article still opens its compatibility section with "For information on the current default version (V7)." V7 stopped being the default on June 9, 2026. That sentence has been stale for over two months as of this writing. Worth knowing, because it tells you something about how quickly that particular page gets maintained.

What is the difference between --style raw and --raw?

Same feature, different spelling. --style raw passed raw as a value to a --style parameter. --raw is a standalone flag.

What the flag does has not changed. Midjourney's description: "In Standard mode, Midjourney automatically adds its own creative touch to your images, which can transform simple prompts into a wide range of artistic styles. When you switch to Raw, you're essentially turning off this 'auto-pilot.'"

That is the whole mechanism. Raw does not make images more photographic by adding realism. It removes a layer of house-style interpretation that sits between your prompt and the render. The docs are careful about this: with simple prompts you'll "often" get more realistic results, and with stylistically detailed prompts you can "really dial in and control the final look."

The practical consequence catches people out. Raw mode makes your prompt matter more, which means a thin prompt gets worse, not better. If you strip the auto-pilot and give the model three words, you get three words' worth of image. That is the same failure pattern covered in why Midjourney prompts don't work, just triggered by a parameter instead of by phrasing.

--style raw vs --stylize: not the same control

These get conflated constantly, and the confusion is understandable because both reduce stylisation. They are separate parameters that do separate jobs.

--stylize (or --s) is a slider. Per Midjourney's Stylize article, the default is 100 and the range is 0 to 1000 on current versions. Low values keep the render literal to your prompt. High values give Midjourney more licence to interpret. The Discord presets are Low 50, Med 100, High 250, Very High 750.

Raw is a mode, not a slider. It has no value. It is on or off.

You can run them together. --raw --s 50 is a legitimate combination and a reasonable starting point for product or reference photography, where you want neither the house aesthetic nor much interpretive freedom. If you want the opposite — maximum house flavour — leave raw off and push stylize up. Our Midjourney style modifiers reference covers what to put in the prompt text itself once you have the parameters settled.

Why am I getting an "invalid parameter" error?

Start by checking format, then check version compatibility. Version mismatch is the more common cause in 2026 and almost nobody looks there first.

Midjourney publishes three formatting rules in the Parameter List, and they cause more failures than they should:

1. Parameters go at the end, after all your prompt text.
2. Leave a space between the prompt text and the dashes.
3. No commas, periods, or other punctuation inside a parameter.

a red barn--ar 3:2 fails. a red barn --ar 3:2, fails. a red barn --ar 3:2 at sunset fails, because text follows the parameter.

The second category is the one that bites people migrating prompts forward. Several parameters that worked fine on V6 or V7 are marked unsupported on V8.1 and V8.2 in Midjourney's own compatibility chart:

• --quality / --q — supported on V6 and V7, marked unsupported on V8.1 and V8.2.
• --turbo — Turbo Mode is marked unsupported on V8.1 and V8.2.
• --niji — --niji 6 works with V6 and --niji 7 with V7; the Niji row is marked unsupported for V8.1 and V8.2.
• Multi-prompts (the :: weighting syntax) — supported on V6, marked unsupported on V7 and V8.
• --stop — Midjourney's Legacy article states it is "compatible with versions 6 and earlier."
• --oref / Omni Reference — a V7 feature; the chart notes V8 runs it via V7.
• Character Reference and --cw — V6 only; unsupported on V7 and V8.

Midjourney does not publish a canonical list of the error strings it returns for any of these, so I cannot tell you which produce a hard error versus a silent ignore. What I can tell you is that if a prompt you saved in 2024 suddenly fails, the version chart is the first place to look, not your typing.

The same prompt, with and without raw

Here is a matched pair. Same subject, same lighting, same aspect ratio, same seed. The only variable is the flag.

Control, no raw — Midjourney applies its default aesthetic on top of your description:

a ceramic pour-over coffee dripper on a pale oak counter,
morning window light from the left, shallow depth of field,
matte glaze, single subject --ar 3:2 --v 8.2 --seed 1234

Raw, same prompt — the default aesthetic pass is removed and your description carries the whole render:

a ceramic pour-over coffee dripper on a pale oak counter,
morning window light from the left, shallow depth of field,
matte glaze, single subject --ar 3:2 --v 8.2 --seed 1234 --raw

And the legacy form, which is what Midjourney documented for V6 and still lists in the legacy table:

a ceramic pour-over coffee dripper on a pale oak counter,
morning window light from the left, shallow depth of field,
matte glaze, single subject --ar 3:2 --v 6 --style raw --seed 1234

I am not going to tell you what the two images look like, because I have not generated them for you and inventing a described result would defeat the point of this page. What Midjourney documents is the behavioural difference: the second prompt has no auto-pilot styling applied, so every stylistic decision in the output traces back to a word you wrote. The first prompt has a layer of Midjourney's aesthetic judgement sitting on top.

One caveat on the seed. The Version chart marks the Seed parameter as supported on V8.1 and V8.2 with the note "99% identical" — so a seeded pair on V8 is a close comparison, not a pixel-locked one. On V6 and V7 seeds are marked as plainly supported. Run each side two or three times before drawing conclusions.

If you want more matched-pair structure to work from, the V7 prompt examples post and the aesthetic Midjourney prompts collection are both built around swapping one variable at a time.

Does raw still matter now that V8.2 renders at 2048 pixels?

Yes, because resolution and styling are unrelated controls. A sharper render of an over-stylised image is still over-stylised.

The resolution facts, from Midjourney's Image Size & Resolution article: "when you use the default 1:1 aspect ratio, Midjourney version 8.2 creates HD images that are 2048 x 2048 pixels (px) and SD images that are 1024 x 1024px." HD is invoked with --hd, standard with --sd, and the Version chart marks HD Images (2048px) as available on V8.1 and V8.2 and unavailable on V6 and V7.

Now the part where the sources disagree, which I would rather flag than smooth over.

Midjourney's V8.1 Alpha announcement, dated April 14, 2026, says HD mode became "3x faster and 3x cheaper. It's so cheap we're making it default for V8.1." But the current Version help article, read August 25, 2026, describes HD as something "you can turn on" in the settings panel and prices it at 1.3 minutes of GPU time against 0.8 for SD. It does not restate that HD is the default.

Both statements are from Midjourney. They were published four months apart, and the announcement was written when V8 was alpha-only. I cannot tell you from published sources which mode your account defaults to today. Check your own settings panel — that is authoritative for you in a way that either article is not.

What is not in dispute: HD changes pixel count, raw changes styling, and the maximum aspect ratio on V8.1 and V8.2 is 14:1 in general but 4:1 for HD. So the "2048 x 2048" figure is a 1:1 number, not a universal one.

How to check this yourself in 30 seconds

This page will age. Midjourney shipped V8.0, V8.1 and V8.2 inside five months. Here is how to re-verify without trusting me:

1. Check your model. On the web, the version pill sits in the prompt bar. In Discord, run /settings and read the version dropdown. Midjourney states that web and Discord settings are synced, so you only need to look in one place.
2. Run the documented form. Append --raw to any prompt. If the job runs and the parameter shows up in the returned job's prompt, raw is live on your model.
3. Test the legacy form directly. Run the identical prompt with --style raw instead. Three outcomes: it errors, it runs but the parameter is stripped from the returned prompt, or it runs and the parameter persists. That answers the question for your account with certainty, which no blog post can.
4. Read the source, not a summary. Open Midjourney's Parameter List and the Feature Compatibility chart in the Version article. Both carry a last-updated date. If that date is newer than this post's, believe them over me.

That last step is the one that matters. Midjourney has quietly moved parameters between the current docs and the Legacy Features article more than once — the old dedicated "Style Parameters" help article is a 404 as of August 25, 2026 — and a dated primary source beats a confident tutorial every time.

Writing prompts that earn raw mode

Raw shifts the burden onto your prompt text. That is the trade. If you turn off the house aesthetic and your prompt is a noun and two adjectives, the render has nothing to work from.

A prompt that holds up under raw usually names all five of these explicitly: subject, camera or medium, lighting, composition, and finish. Miss one and Midjourney fills the gap with whatever the training data suggests, which is precisely the arbitrariness you turned raw on to avoid. This is ordinary prompt engineering applied to pixels rather than tokens.

That structural discipline is what Prompt Architects automates. Our image prompt feature takes a short description and expands it into a structured prompt with the roles, subject detail, and constraints spelled out, so you are not hand-writing five clauses every time you want a raw-mode render. It generates the prompt text; Midjourney still generates the image, and you still paste the parameters yourself. There is a free plan if you want to try it before deciding, and current pricing is on the pricing page.

If you also work in Niji, note that the Version chart marks the Niji row as unsupported on V8.1 and V8.2, so anime work still routes through V7 with --niji 7. We compared the two model families in Niji vs Midjourney.

The short version

--style raw is legacy syntax. Midjourney documents it for V5 and V6 and nowhere else. Raw mode is alive and well on V7, V8.1 and V8.2, and the parameter Midjourney's own settings panel writes into your prompt is --raw. Type that.

Whether the old spelling still parses on a current model is genuinely unpublished, and anyone telling you otherwise without a source is guessing. Run the 30-second test above and you will know for your account in less time than it takes to read a forum thread about it.