"Golden hour" works everywhere — but it's just the floor

"Golden hour" works everywhere — but it's just the floor

The same lighting intent — warm sunset light on a portrait — requires completely different prompt syntax depending on the tool. Midjourney V7/V8.1 takes lighting as a label; Flux takes it as a behavioral description of how light moves through the scene. Includes a per-tool table, the candle/neon object-vs-effect quirk, and SD3's documented prompt-adherence problem.

AI Image Prompt Tip
AI Image Prompt Tip@NeoDrop Official
2026/5/23 · 0:22
購読 1 件 · コンテンツ 16 件
You wrote golden hour lighting in your Midjourney prompt and the image looked gorgeous. So you pasted the same phrase into Flux and the result was decent but somehow flatter, less specific — like the model acknowledged the label without fully committing to it. The keyword wasn't wrong. You were using MJ syntax on an engine that speaks a different language.
Lighting vocabulary in AI image generation splits along a fundamental line: labels versus behaviors. Midjourney responds to lighting labels. Flux responds to lighting behaviors. Using the wrong mode on either tool won't cause errors — the output just stops improving past a certain point.
リンクプレビューを読み込んでいます…

The two lighting syntaxes

MJ V7 and V8.1 are trained to map named lighting conditions directly to visual output. golden hour, blue hour, volumetric lighting, neon ambient light — these read like camera directions and the model treats them that way. Lighting sits as one discrete layer in the prompt formula: Subject + Environment + Style + Lighting + Camera + Parameters. 1
Flux dev/schnell/pro uses a T5-XXL text encoder (~4.6B parameters) that processes natural language at the sentence level. 2 The model doesn't just map labels — it parses how light moves and interacts with the scene. The fal.ai Flux guide states:
"There's a big difference between naming a lighting condition and describing how light interacts with the scene. The more you describe light as something that moves through and interacts with the scene, the more realistic and intentional your results will look." 2
SDXL accepts keyword labels with optional weight syntax. SD3 is a special case covered at the end.

The universal starting points

Before tool-specific syntax, there's a core vocabulary that works across all three ecosystems. These are the natural lighting descriptors that multiple independent sources confirm as effective everywhere: 3 4
  • golden hour — warm amber raking light, sun near the horizon, soft long shadows
  • blue hour — post-sunset or pre-dawn indirect light, deep blue-indigo sky, no hard shadows
  • magic hour — synonym for golden hour; either works
  • overcast (or overcast lighting) — diffuse, shadowless daylight; even exposure across the subject
  • harsh midday sun / harsh sunlight — high-contrast, overhead, hard shadows
  • backlighting — light source behind the subject; rim glow and silhouettes
One distinction worth making on golden hour: writing just sunset gets you a nice sky but doesn't guarantee the light actually falls on your subject. golden hour cinematic lighting tells the model both the time of day and the quality of light hitting the subject — two different constraints in one phrase. 3

Per-tool syntax for the same intent

Here's how to express the same lighting idea — warm sunset light on a portrait — across each tool:
ToolSyntax modeExample
MJ V7Label + modifiergolden hour cinematic lighting, soft long shadows --style raw --stylize 250
MJ V8.1Label only (no --no; --raw for literalism)golden hour cinematic lighting --raw
Flux dev/schnellBehavioral prosewarm golden sunset light streaming through the window, casting long shadows across the hardwood floor, dust particles visible in the light beam
SDXLKeywords + optional weightgolden hour lighting, warm side light, (golden hour:1.3)
SD3Positive rewrite onlywarm amber side lighting, long soft shadows, sun near horizon
The Flux example is longer than the Midjourney version intentionally. Flux weighs earlier tokens more heavily, and the model expects to parse the description of light's behavior rather than receive a named effect. 2 One thing that does not work in Flux: weight syntax like (golden hour:1.5) or (golden hour)++ — the model ignores these constructions entirely. 2

Practical light sources: object vs. effect

Candles, neon signs, and fire have a quirk that time-of-day keywords don't: they describe both a physical object and a lighting effect. How each tool handles this split changes what you need to write.
Midjourney tends to generate the light source and the effect when you use these terms. PromptDervish documented the behavior in 2023 on MJ V5: adding candlelight to a teacup prompt caused Midjourney to "insistently add candles" to every generation, not just cast candlelight on the scene. 5 The same object-association pattern appears in V7 community usage, though a direct controlled comparison across versions hasn't been published. The same logic applies to neon: neon sign places a sign object in the frame, but neon ambient light or drenched in neon ambient light tells MJ to use neon as fill light for the entire scene. 3
To get only the lighting effect without a visible candle or sign:
  1. Name the light quality, not the object: warm flickering amber glow, soft volumetric candlelight.
  2. In MJ V7, add --style raw to reduce the model's tendency to surface ambient objects. In V8.1, --no was removed — use --raw and reframe in positive terms: room lit entirely by a single candle flame, no additional objects visible.
Neon ambient is worth showing as a complete example. The prompt structure that works in MJ V7/V8.1 combines a specific light color, an atmospheric keyword, and a scene condition that amplifies the effect: 3
cinematic still, a person in a futuristic jacket on a city balcony,
drenched in neon ambient light, cyberpunk aesthetic,
vibrant cyan and pink glow, rainy night
--ar 16:9 --style raw --stylize 200
The rainy night addition isn't decoration — wet surfaces reflect neon, making the ambient effect visible across the entire frame rather than only near a single sign.
Midjourney-generated image showing neon ambient lighting — vivid cyan and pink light filling an urban night scene
MJ-generated example showing neon ambient fill vs. a single neon sign object 6
リンクプレビューを読み込んでいます…

The SD3 footnote

SD3 has a documented prompt-adherence problem: the r/StableDiffusion community ran comparison tests and found that changing lighting descriptors frequently produces near-identical outputs regardless of the wording. 7 One tester reported: "Even in very low CFG settings, results always keep roughly similar viewing angles" — and this extends to lighting. For SD3 specifically, IC-Light (a ComfyUI node by lllyasviel) gives more reliable relighting control than text keywords alone. Text-based lighting control works considerably better in SDXL than in SD3.

The one-line version

Write lighting labels for Midjourney. Write lighting behaviors for Flux. For neon and candle, name the effect — not the object — unless you want both in the frame.
Cover image: AI-generated illustration

参考ソース

  1. 1SurePrompts: Midjourney V7 Prompting Guide
  2. 2fal.ai: How to Use FLUX AI — Prompts, Settings & Tips
  3. 3Promptaa: 10 Masterful Midjourney Lighting Prompts to Try in 2026
  4. 4Tim Fajardo: How to Prompt AI Image Tools Like a Professional in 2026
  5. 5AI Mind / PromptDervish: Midjourney Explorations #3 — Lighting
  6. 6OpenArt: The Best 25 Midjourney Prompts for Lighting
  7. 7Reddit r/StableDiffusion: Let's talk about style adherence in SD3
AI Image Prompt Tip
AI Image Prompt Tip

このコンテンツについて、さらに観点や背景を補足しましょう。

  • ログインするとコメントできます。