Image to Flux Prompt Generator
Flux hates keyword tags. Flux ignores (weight:1.3) syntax. Flux doesn't use --ar. What Flux wants is a 30–80 word natural-language scene description with the subject first. That's what this tool outputs — purpose-built for Flux 1.1 Pro and Flux Dev.
Your image
Flux resultPNG, JPG or WebP · Max 5MB
Drag & drop or click to select
PNG, JPG or WebP · Max 5MB
Paste image from clipboard (⌘/Ctrl + V)
Your uploaded image will appear here
Preview will appear after you upload an image.
Alignment spacer
Select AI Model
Click the button to generate AI prompts for all 5 models
Ready to generate prompts?
Upload an image first to get started
Default: Quick Draft in seconds. Refine later for more detail.
Loading...
Your Generated Prompts Will Appear Below:
General Prompt
Base prompt extracted from your image.
Quick Draft
This is your fast first draft. Use it now, or refine it for more detail.
Your General Prompt prompt will appear here... This prompt works with any AI image model and provides a versatile description.
This is your fast first draft. Use it now, or refine it for more detail.
- Target models
- Flux 1.1 Pro · Flux Dev · Flux Schnell
- Output style
- Pure natural language (no tags)
- Ideal length
- 30–80 words
- Free daily runs
- 2 (no signup)
Why Flux prompts are completely different
Flux was architected around the T5 text encoder, which understands full sentences the way GPT-4 does. This is why Midjourney and SDXL habits actively hurt Flux output. The tool below generates prompts in Flux's native 3-part structure: subject & scene → photographic detail → mood & style.
Subject & scene (first sentence)
A woman in a red silk dress standing barefoot on a sandy beach at sunsetFlux weights earlier tokens heavily. Lead with who, what, where in one coherent sentence.
Photographic specifics
shot on Hasselblad X2D, 85mm lens, shallow depth of field, soft bokeh across the waterFlux's T5 encoder recognizes real camera/lens names and applies their aesthetic signatures — sensor size, dynamic range, color science.
Light interaction (not conditions)
warm golden sunset light streaming low across the scene, casting long shadows, dust particles visible in the beamInstead of 'golden hour', describe what the light *does*. Direction, quality, interaction with surfaces — this is where Flux outperforms everything else.
Mood / style (optional closer)
cinematic, moody, editorial fashion photographyAdd context flags at the END — Flux uses them as style anchors after the scene is set. Putting them first wastes attention on abstraction.
What NOT to include
No --ar 16:9. No (beautiful:1.4). No 8k, masterpiece, best quality tags. No negative prompt.All of these are Midjourney/SDXL syntax. Flux ignores them at best, prints them as literal text at worst (especially Flux Dev with --flags).
Real Flux prompts from real images

Photoreal surreal → Flux prompt
A young woman floating weightless in a sunlit forest clearing, wearing a flowing white dress, eyes closed serenely. Shot on Hasselblad X2D with 80mm lens, f/2.8, natural late-afternoon light filtering through the canopy and catching dust particles in visible beams. Soft focus falls off around her, creating an ethereal halo against the deep green background. Cinematic, dreamlike, editorial photography.

Text-in-image → Flux prompt (Flux's killer feature)
A vintage hand-painted wooden sign hanging above a cafe doorway, reading 'OPEN ALL DAY' in weathered cream serif letters on a dark teal background. Shot on a Leica M6 with 35mm Summicron lens, golden hour sidelight picking out the texture of chipped paint and aged wood grain. Warm tungsten glow from inside the shop softly illuminates the frame. Street photography, natural color, quiet atmosphere.

Macro concept → Flux Dev prompt
A single honeybee mid-flight over a clover blossom, wings frozen by high-speed capture, golden pollen particles suspended in the air around it. Shot on a Canon R5 with 100mm macro lens at 1:1 magnification, f/5.6, sunlit meadow background softly blurred. Afternoon backlight rims the bee's fuzzy thorax in gold, making every hair visible. National Geographic documentary style, sharp, alive.
Tips most beginners miss
Treat Flux like you're briefing a photographer
Write prompts as if you're describing the shot you want to a human with a camera. Tell them the subject, the setting, the light, the feel. This maps directly to how Flux's T5 encoder processes your input.
Real camera names unlock real aesthetics
'shot on Hasselblad X2D' produces different output than 'shot on iPhone 15 Pro' — Flux knows these sensors' color science. Specific gear > generic 'professional camera'.
No negative prompts — describe positively instead
Flux Dev/Schnell doesn't support negative prompts. If you want a clean background, don't negative-prompt 'cluttered'; write 'minimal, empty background' in the positive prompt.
Flux Dev hates 'white background'
A known Flux Dev quirk: plain 'white background' produces flat, unclear outputs. Add environment detail instead: 'seamless studio backdrop under soft key light' or 'pure white cyclorama'. Flux Pro/Schnell don't have this issue.
Guidance 3.0–3.8 for Flux Dev, default for Pro
If you're running Flux Dev locally: steps 24–32, guidance 3.0–3.8, resolution 768–1024. Flux 1.1 Pro's API handles these automatically — you only pass width/height and optional seed.
Flux vs other image models
| Capability | This model | Midjourney | SDXL |
|---|---|---|---|
| Prompt style | Natural language (prose) | Sentence + --flags | Sentence + tags + negative |
| Text rendering | ✅ Best in class | ✅ Good | ⚠️ Improving |
| Runs locally | ✅ Dev (12GB+) / Schnell | ✅ 8GB+ | ❌ Cloud only |
| Negative prompts | ❌ Not supported | ✅ Full | ❌ Not supported |
Frequently asked questions
What's the difference between Flux 1.1 Pro, Dev, and Schnell?
Pro is API-only (cloud) with Ultra and Raw modes, fastest, best quality, tolerates simpler prompts. Dev is open-weight (non-commercial license), needs 12GB+ VRAM, requires detailed prompts. Schnell is a 4-step distilled version of Dev, open-weight (Apache 2.0), great for iteration. All three use the same prompt style (natural language, no tags).
Why doesn't the output include --ar 16:9 like Midjourney?
Because Flux doesn't use Midjourney flags. Pass width and height as separate API parameters (for Pro) or ComfyUI node settings (for Dev/Schnell). --ar in the prompt text will appear as literal characters in the generated image.
Can Flux generate text correctly in images?
Yes — this is Flux's strongest differentiator vs Midjourney and SDXL. To get clean text, describe it in quotes in natural language: 'a sign reading "OPEN" in red neon letters'. Flux 1.1 Pro handles up to ~10-word text blocks cleanly; Flux Dev is slightly worse.
What's the prompt length sweet spot?
30–80 words. Under 30 words leaves Flux guessing and it fills in average interpretations. Over 100 words starts to dilute the important early tokens (Flux weights earlier words more heavily). The tool targets ~60 words by default.
Do I need a negative prompt for Flux?
No. Flux Dev and Schnell don't support negative prompts. Flux 1.1 Pro's API has a nascent negative prompt field but it's not well-documented and most practitioners don't use it. Describe what you want positively instead.
Flux Pro vs Flux Dev — which prompt approach?
Same structure (natural language, 30–80 words, subject first), but Dev punishes sloppy prompting much more. Pro tolerates shorter, simpler prompts; Dev needs all three parts (subject & scene, photographic detail, light & mood) to produce its best output.