Flux Kontext Dev

FLUX Kontext Dev — wavespeed-ai/flux-kontext-dev

FLUX.1 Kontext Dev is an open-weight, open-code image-to-image model built for instruction-based editing. Provide a source image plus a natural-language edit request, and the model rewrites the image while preserving the original context when asked—making it suitable for targeted retouching, object changes, background swaps, text edits, and controlled style transforms.

Key capabilities

• Instruction-based image editing from a single input image
• Strong subject and scene preservation when you explicitly request it
• Local and global edits: change specific regions or the whole image
• Iterative editing workflow: apply multiple edits step-by-step with minimal drift

Typical use cases

• Retouching: lighting, exposure, cleanup, blemish removal
• Object edits: add/remove/replace items, change colors/materials
• Background replacement: swap environments while keeping the subject consistent
• Text edits: add or replace words on signs, posters, packaging
• Style transforms: convert to clay, illustration, cinematic, etc., while preserving composition

Pricing

$0.025 per image.

Cost per run = num_images × $0.025 Example: num_images = 4 → $0.10

Inputs and outputs

Input:

• One source image (upload or public URL)
• One edit instruction (prompt)

Output:

• One or more edited images (controlled by num_images)

Parameters

• prompt: Edit instruction describing what to change and what to keep
• image: Source image
• width / height: Output resolution
• num_inference_steps: More steps usually improves quality but increases latency
• guidance_scale: Higher values follow the prompt more strongly; too high may over-edit
• num_images: Number of variations generated per run
• seed: Fixed value for reproducibility; -1 for random
• output_format: jpeg or png
• enable_base64_output: Return BASE64 instead of a URL (API only)
• enable_sync_mode: Wait for generation and return results directly (API only)

Prompting guide

Write prompts like an editor’s brief:

1. Preserve clause: what must stay the same
2. Edit clause: what must change
3. Constraints: realism level, lighting, placement, typography, materials
4. Consistency: match shadows/highlights to the new scene

Template: Keep [what must stay]. Change [what to edit]. Ensure [constraints]. Match [lighting/shadows/style consistency].

Example prompts

• Keep the person’s face, pose, and clothing unchanged. Change the background to a foggy gothic castle. Match lighting and shadows to the new environment.
• Change the car color to red. Preserve reflections and keep the rest of the scene unchanged.
• Add the text “COOL” on the sign in the same perspective, with realistic shadows, and do not alter anything else.
• Turn the image into a clay style with handcrafted texture and soft studio lighting, while keeping the composition and subject identity.
• Remove the background crowd and keep the main subject sharp and unchanged.

Best practices

• Start simple, then iterate: do one change per run for maximum control.
• If the edit is too aggressive, lower guidance_scale and strengthen the preserve clause.
• For A/B comparisons, keep seed fixed and change only one parameter at a time.
• Use aspect-matched width/height to avoid unintended stretching.