Guide · 7 min read
Flux image prompting: Dev, Schnell, and Pro
How to write Flux-friendly prompts, tune guidance and steps, and when to switch between Dev, Schnell, and Pro.
Natural language first
Flux models (Dev, Schnell, Pro, Kontext) respond well to descriptive prose with explicit materials and lighting. Unlike older SD tag soups, write scenes as art direction notes.
Model selection
- Schnell — layout exploration, storyboards, fast A/B
- Dev — default quality for most social and concept work
- Pro — hero assets, print-bound detail, client delivery
- Kontext — edit existing images while preserving subject identity
Parameter hygiene
Document in your prompt or curator note:
- Steps — higher for fine texture; lower for drafts
- Guidance — too high causes waxiness; too low drifts from prompt
- Aspect ratio — set in UI or embed in workflow JSON
Negative prompts
Flux often needs short negatives ("no watermark, no text overlay") rather than SD-style walls of exclusions.
Building a reusable template
- Lock composition language (camera height, subject placement)
- Parameterize nouns (
{PRODUCT_NAME},{COLOR_PALETTE}) - Attach proof images from the exact settings you document
Library starting points
Browse Flux Dev, Flux Schnell, and Flux Pro collections on My Copyprompt — each listing includes parameters where curators tested them.
Submitting Flux prompts
When you submit an image prompt, upload real outputs (HTTPS URLs). Placeholder stock images delay approval and hurt site quality standards.