Clipwave
Media ForgeGenerate images & video, fastMedia StudioNewBuild images & video by chatting with AIWorkflowsAutomate pipelines at scaleClipperNewBreak a video down & cut the highlightsMarketing AgentDone-for-you UGC video ads
Explore NewMCPPricingFAQ
Log inStart free
AI Models/Flux/Prompting

How to prompt Flux AI

Flux reads a prompt front to back and weighs what comes first, so lead with the subject and push secondary detail to the end. It rewards long, concrete, descriptive prompts — camera and lens names, named light sources, hex codes for exact colors — and it has no negative prompt: describe what you want, never what to avoid. The family splits into generation models (Flux Pro, Dev, Pro Ultra, Flux 2, Flux 2 Pro, Flux 2 LoRA) and editing models (Flux Kontext, Flux 2 Edit) that change one thing while preserving the rest.

Anatomy of a Flux prompt

  1. 1

    Image type & subject

    Open with the kind of image and a specific subject: "macro product photograph of a stainless-steel dive watch", not "a watch, professional, high quality". Word order matters — Flux prioritizes what it reads first.

  2. 2

    Action or pose

    What the subject is doing, mid-moment: "mid-leap chasing a tennis ball", "leaning against the doorway, arms crossed". A frozen verb beats a static description.

  3. 3

    Setting & context

    Where and when: "in a cramped Lisbon tram at dusk". Environment words drive texture, reflections and background detail — the layer that makes Flux output read as photographed rather than rendered.

  4. 4

    Style & medium

    Name the art form and approach precisely: "fashion editorial photography", "oil painting", "risograph poster". Vague direction ("artistic", "beautiful") is filler and gets ignored.

  5. 5

    Camera & lens

    For photorealism, specify gear and settings: "shot on Hasselblad X2D, 80mm lens, f/2.8" or a photographic era ("2000s digicam flash photo"). This steers realism far harder than the word "photorealistic".

  6. 6

    Lighting

    Concrete source and direction: "soft window light from the left", "golden hour backlight", "single bare bulb overhead". Generic "good lighting" does nothing.

  7. 7

    Color & palette

    Palette direction ("muted beige and forest green tones") or exact hex codes tied to specific objects: "the sneaker upper is #0047AB". Hex codes only work when clearly attached to an object.

  8. 8

    Text in the image

    Put the exact words in quotation marks and describe typography and placement: "the sign reads 'OPEN' in red neon letters above the door". Keep in-image text short.

Template

[image type] of [subject], [action or pose], [setting], [style or medium], [camera and lens], [lighting], [color palette or hex codes], [text in quotes, if any]

10 example prompts that work

4K product hero shot

Flux 2 Pro · 4K · 1:1
Macro product photograph of a stainless-steel dive watch on wet black slate, water droplets beading on the sapphire crystal, dramatic single-source studio lighting from the upper left, deep shadows, subtle reflection under the case, shot on a 100mm macro lens at f/4, cold steel-blue palette with one warm highlight on the bezel.

Subject first, then material words (steel, slate, sapphire) that Flux turns into micro-detail. One named light source plus a lens spec produces catalog-grade realism without any "8K masterpiece" filler.

Editorial portrait with camera language

Flux Pro · 2K · 3:4 · guidance 3.5 · 28 steps
Fashion editorial photograph of a young woman with curly red hair and freckles, leaning against a sunlit concrete wall, wearing an oversized cream linen blazer, direct gaze, shot on Hasselblad X2D, 80mm lens, f/2.8, shallow depth of field, soft late-afternoon side light, muted warm film palette.

Camera, lens and aperture are the realism levers on Flux — "shot on Hasselblad, 80mm, f/2.8" beats "professional photo" every time. The concrete subject ("curly red hair and freckles") renders more consistently than a generic "beautiful woman".

Cinematic ultra-wide landscape

Flux Pro Ultra · 4K · 21:9
Cinematic long shot of a lone hiker crossing a black-sand ridge in Iceland, low storm clouds tearing open above, a single shaft of sunlight hitting the valley floor below, anamorphic framing, shot on 35mm film, desaturated teal-and-slate palette with one warm accent on the hiker's red jacket.

The 21:9 ratio plus anamorphic and film-stock words gives a widescreen film-still look. One accent color against a restrained palette is a Flux strength — state both explicitly.

Exact brand colors with hex codes

Flux 2 · 2K · 1:1
Studio product photo of a minimalist running sneaker floating at a slight angle over a seamless background, the sneaker upper is #0047AB, the midsole is #F5F0E6, the seamless background is a smooth gradient starting with #02eb3c finishing with #edfa3c, soft even lighting, crisp shadows underneath.

Hex codes work when each one is attached to a named object — "the upper is #0047AB", never a bare list of codes. Gradients take two hex endpoints. This is the reliable route to on-brand colors without post-correction.

In-image text and signage

Flux 2 · 2K · 3:2
Night street photograph of a narrow ramen bar entrance in the rain, the sign above the door reads "MIDNIGHT NOODLES" in warm yellow neon letters, a smaller vertical banner reads "OPEN" in red neon, wet asphalt reflecting the signs, shot on 35mm at f/1.8, steam drifting from the doorway.

Quotation marks around the exact words, plus placement ("above the door") and typography style (neon, color) — the three things Flux needs to render text correctly. Two short strings are reliable; dense paragraphs of copy are not.

Long-form scene, drafted cheap

Flux Dev · 1K · 4:3 · guidance 3.5 · 28 steps
A golden retriever mid-leap chasing a tennis ball across sunlit hardwood floor in a cozy living room, muddy paw prints trailing behind, a knocked-over plant in the background, warm afternoon light streaming through sheer curtains, dust motes in the light shafts, shallow depth of field, candid pet photography, 35mm lens.

An 80-plus-word prompt where every clause adds a visible element — action, evidence of action, environment, light behavior. Iterate a scene like this on Flux Dev at 1K, then rerun the winning prompt on Flux 2 Pro for the final.

Consistent brand style with a LoRA

Flux 2 LoRA · 2K · 1:1 · LoRA scale 1.0
Product lifestyle photo of a ceramic pour-over coffee set on a linen tablecloth, morning window light, minimal composition with generous negative space, in the brand illustration style of the loaded LoRA.

The LoRA carries the look; the prompt only supplies subject, composition and light. Load your LoRA weights by URL, keep LoRA scale at 1.0, and drop toward 0.7-0.8 if the style overpowers the subject or push to 1.2 if it barely shows.

Kontext edit: swap the background, keep the subject

Flux Kontext · 2K · match source ratio
Change the background to a sunlit Mediterranean beach while keeping the person in the exact same position, scale, and pose. Match the lighting on the subject to the new scene.

The preservation clause is the whole trick — without "exact same position, scale, and pose" the model treats the subject as editable too. Kontext edits from a single input image; upload it, then write only the change.

Kontext edit: replace text on signage

Flux Kontext · 2K · match source ratio
Replace "GRAND OPENING" with "NOW HIRING" on the storefront banner. Keep the font style, color, and banner position unchanged.

The Replace "[original]" with "[new]" structure is the documented, most effective way to edit text in an image — quote both strings exactly. Adding "keep the font style" pins the typography so only the words change.

Flux 2 Edit: restyle without losing the composition

Flux 2 Edit · 2K · match source ratio
Turn this photograph into an oil painting with visible brushstrokes and impasto texture, keeping the exact composition, subject placement, and color relationships unchanged.

Style transfer on the Flux 2 editing models works best as one clear medium instruction plus an explicit preserve list. Direct verbs ("turn this into", "change", "replace") outperform vague asks like "make it more artistic".

Settings that matter

  • Guidance scale

    On Flux Pro, Dev, Flux 2 and the LoRA/edit variants: 1-10, default 3.5. Higher follows the prompt more literally, lower renders looser and more natural. Stay at 3.5; nudge to 4.5-5 only when named elements are being dropped.

  • Steps

    1-50, default 28. Fewer steps render faster with less refinement — 16-20 is fine for drafts. Past the default the gains shrink quickly; raise it only for dense, detail-heavy scenes.

  • Seed

    Lock the seed while you iterate on wording so changes in the output come from your prompt, not the dice. Clear it again once the prompt is final and you want variations.

  • LoRA URL & scale

    Flux 2 LoRA and LoRA Edit only. Paste a direct URL to hosted LoRA weights; scale runs 0-2 with 1.0 default. 0.7-0.8 if the style crushes the subject, up to 1.2 if it is too subtle.

  • Safety tolerance

    Flux Pro Ultra and Flux 2 Pro expose a 1-6 tolerance, default 2. Higher is more permissive; leave the default unless legitimate prompts are being blocked.

  • Resolution & aspect ratio

    Draft at 1K, finalize at 2K — or 4K on Flux Pro Ultra and Flux 2 Pro. 21:9 ultra-wide is available on Flux Dev, Pro Ultra and Flux 2 Pro; the other variants top out at 16:9.

Do and don't

Do

  • Front-load the subject — Flux weighs the first words of the prompt hardest.
  • Use real photography language for realism: camera body, lens, aperture, film stock or era.
  • Tie every hex code to a named object ("the car is #FF0000"), and use two hex endpoints for gradients.
  • Quote exact in-image text and describe its typography and placement.
  • Start short and add only words that visibly change the image — specific detail helps, filler hurts.
  • In edits, pair every change with a preserve clause: what must stay in the exact same position, scale and pose.
  • Lock the seed while refining wording, so you compare prompts and not random draws.

Don't

  • Don't write negative prompts — Flux has no such input; "no text, no blur" just adds noise. Describe what you DO want.
  • Don't stack quality keywords ("8K, masterpiece, ultra detailed") — they change nothing on this family.
  • Don't drop bare hex codes without an object to attach them to; unanchored codes get ignored or misapplied.
  • Don't ask an edit model for five changes in one pass — one or two focused edits per generation, then iterate.
  • Don't re-describe the whole image in an edit prompt; describe only the change, or the model re-imagines the rest too.
  • Don't rely on vague style words ("artistic", "cinematic vibes") — name the medium, the photographer's toolkit, or the era.

Advanced techniques

Photography language is the realism dial

Flux responds to the vocabulary of working photographers more strongly than to quality adjectives. A prompt that specifies camera, focal length and aperture inherits the depth of field, compression and grain of that setup; a prompt that says "highly detailed professional photo" inherits nothing. Photographic eras work the same way — "80s film flash photo", "2000s digicam", "large-format analog" — each pulls a coherent bundle of color response, grain and contrast.

  • Lens language: "85mm portrait lens, f/1.8" for compressed, creamy backgrounds; "24mm wide, deep focus" for environmental shots
  • Light language: name the source, direction and quality — "single softbox camera-left", "hard noon sun overhead", "overcast even light"
  • Era language: film stock and decade references set palette and grain in one phrase

Exact color and structured prompts

Hex codes give Flux 2 pixel-accurate brand color when each code is bound to an object: "the label is #1A1A2E, the cap is #E94560". For complex multi-subject scenes or automated workflows, Flux 2 also accepts structured JSON-style prompts — separate fields for scene, subjects with positions, style and lighting — which keeps long specifications unambiguous where a paragraph would tangle.

Editing: Kontext and the Flux 2 Edit models

Flux Kontext edits from one input image with plain-language instructions and is strongest at surgical changes: recolor an object, swap a background, replace quoted text. The Flux 2 Edit family (Edit, Pro Edit, LoRA Edit) covers the same grammar on the newer generation and accepts multiple input images, so you can combine references — a product shot plus a scene, a garment plus a model. In every case the reliable pattern is the same: name the change directly, then state explicitly what must not move.

  • Object change: "Change the car color to red" — direct verb, one target
  • Text change: Replace "[old]" with "[new]" — both strings quoted
  • Background change: add "while keeping the subject in the exact same position, scale, and pose"
  • Style change: name the target medium and preserve composition explicitly
  • Character consistency: re-edit from the same source image; Kontext holds identity across successive edits

A repeatable brand look with LoRAs

A LoRA is a small weights file that bakes a visual style into Flux 2, so every generation lands in the same look without re-describing it. On Clipwave you attach one by URL on Flux 2 LoRA (generation) or Flux 2 LoRA Edit (editing). Keep prompts content-only — subject, composition, light — and let the LoRA own the style; describing a conflicting style in the prompt fights the weights. Tune the scale slider rather than the prompt when the look is too strong or too weak.

Which variant to use

  • Flux 2

    Default for new work. Second-generation quality at 1K-2K, up to 4 images per run, full guidance and steps control.

  • Flux 2 Pro

    Final assets and hero images — top quality up to 4K, 21:9 available, single image per run.

  • Flux 2 LoRA

    Brand-consistent output: Flux 2 with your own LoRA weights attached by URL, scale 0-2.

  • Flux 2 Edit

    Prompt-based editing on the current generation, multiple input images accepted.

  • Flux 2 Pro Edit

    The same editing grammar at top quality — client-facing retouches and composites.

  • Flux 2 LoRA Edit

    Editing while a LoRA enforces the house style on everything the edit touches.

  • Flux Kontext

    Single-image surgical edits — recolor, background swap, quoted-text replacement — with strong identity preservation across successive edits.

  • Flux Pro

    The classic high-fidelity generator; up to 4 images per run with guidance and steps exposed.

  • Flux Dev

    Drafting and exploration — flexible, supports 21:9, ideal for iterating prompts cheaply before a Pro rerun.

  • Flux Pro Ultra

    Legacy ultra-HD generation up to 4K with 21:9 — when you need maximum resolution on the first-generation engine.

Frequently asked

Does Flux support negative prompts?

No — nothing in the family does. Convert every exclusion into a positive description: instead of "no clutter", write "clean seamless background with generous negative space". Words about what to avoid just add noise.

How do I get exact brand colors?

Hex codes bound to named objects: "the logo is #E94560, the background is #1A1A2E". For gradients, give both endpoints. Unanchored hex lists get ignored — the binding to an object is what makes it work.

How long should a Flux prompt be?

Start at 10-30 words and grow only with words that visibly change the image. 30-80 words covers most real work; 80-300 is worth it only for complex multi-subject scenes. Filler adjectives never help.

Flux Kontext or Flux 2 Edit for editing?

Kontext for surgical single-image edits — it is exceptional at text replacement and holding a character steady across repeated edits. Flux 2 Edit for editing on the newer engine or when the edit needs multiple input images combined; Pro Edit when the result ships to a client.

How do I keep one character or style consistent across many images?

Three tools, in escalating order: lock the seed and vary the prompt minimally; edit repeatedly from the same source image with Kontext, which preserves identity; or train the look into a LoRA and run Flux 2 LoRA so every generation shares it by construction.

Can Flux render text inside images?

Yes, for short strings: put the exact words in quotes and specify typography and placement. A shop sign or a two-word headline is reliable; for dense paragraphs of copy or long layouts, GPT Image on Clipwave is the stronger pick.

Try Flux in Media Forge →About FluxAll models
Clipwave

Tell me what you need and grab a coffee. I'll have it ready before you finish the cup.

Product

Marketing AgentWorkflow StudioMedia ForgeTemplatesAI Models

Open in app

Workflow StudioMedia ForgeProjectsAvatars

Company

ContactPrivacy PolicyTerms of ServiceLegal Notice

© 2026 Clipwave

support@clipwave.io