FLUX.1 Kontext [dev]

AI Image Editing Model

Image $$ · 2.5¢

Black Forest Labs' open-weights multimodal flow transformer for in-context image generation and editing, available for non-commercial use with character consistency and style transfer capabilities

FLUX.1 Kontext [dev] API OpenAI-compatible

Integrate FLUX.1 Kontext [dev] into your application via the Lumenfall OpenAI-compatible API to perform advanced text-to-image generation and precise image editing using flow transformer technology.

Base URL
https://api.lumenfall.ai/openai/v1
Model
flux.1-kontext-dev

Code Examples

Text to Image

/v1/images/generations
curl -X POST \
  https://api.lumenfall.ai/openai/v1/images/generations \
  -H "Authorization: Bearer $LUMENFALL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "flux.1-kontext-dev",
    "prompt": "",
    "size": "1024x1024"
  }'
# Response:
# { "created": 1234567890, "data": [{ "url": "https://...", "revised_prompt": "..." }] }

Image Edit

/v1/images/edits

Parameter Reference

Required Supported Not available

Core Parameters

Parameter Type Description Modes
prompt string Required. Edit instruction for the image
T2I Edit
seed integer Random seed for reproducibility
T2I Edit

Size & Layout

Parameter Type Description Modes
size string Image dimensions as WxH pixels (e.g. "1024x1024") or aspect ratio (e.g. "16:9")
WxH determines both shape and scale (aspect_ratio and resolution are ignored when size is provided). W:H format is equivalent to aspect_ratio.
T2I Edit
aspect_ratio string Aspect ratio of the output image (e.g. "16:9", "1:1")
Controls shape independently of scale. Use with resolution to control both. If size is also provided, size takes precedence. Any ratio is accepted and mapped to the nearest supported value.
T2I Edit
resolution string Output resolution tier (e.g. "1K", "4K")
auto 1K
Controls scale independently of shape. Higher tiers produce larger images and cost more. If size is also provided, size takes precedence for scale. Any tier is accepted and mapped to the nearest supported value.
T2I Edit
Output size aspect_ratio + resolution
Flexible
Auto "auto" Model chooses optimal dimensions
Custom
1–14142px per side
"WxH" Any pixel dimensions within model constraints
1K 11 sizes
Output size aspect_ratio + resolution
1183 × 887 "1183x887" or "4:3" + "1K"
916 × 1145 "916x1145" or "4:5" + "1K"
1145 × 916 "1145x916" or "5:4" + "1K"
1024 × 1024 "1024x1024" or "1:1" + "1K"
887 × 1182 "887x1182" or "3:4" + "1K"
836 × 1254 "836x1254" or "2:3" + "1K"
1254 × 836 "1254x836" or "3:2" + "1K"
768 × 1365 "768x1365" or "9:16" + "1K"
1365 × 768 "1365x768" or "16:9" + "1K"
670 × 1564 "670x1564" or "9:21" + "1K"
1563 × 670 "1563x670" or "21:9" + "1K"

How these parameters work

size

Exact pixel dimensions

"1920x1080"
aspect_ratio

Shape only, default scale

"16:9"
resolution

Scale tier, preserves shape

"1K"

Priority when combined

size aspect_ratio + resolution aspect_ratio resolution

size is most specific and always wins. aspect_ratio and resolution control shape and scale independently.

How matching works

Shape matching – we pick the closest supported ratio. Ask for 7:1 on a model with 4:1 and 8:1, you get 8:1.
Scale matching – providers use different tier formats: K tiers (0.5K 1K 2K 4K) or megapixel tiers (0.25 1). If the exact tier isn't available, you get the nearest one.
Dimension clamping – if a model has pixel limits, we clamp dimensions to fit and keep the aspect ratio intact.

Media Inputs

Parameter Type Description Modes
image file Required. Input image(s) to edit
Supports PNG, JPEG, WebP.
T2I Edit

Output & Format

Parameter Type Description Modes
response_format string How to return the image
url b64_json
Default: "url"
T2I Edit
output_format string Output image format
png jpeg gif webp avif
Gateway converts to requested format if provider doesn't support it natively.
T2I Edit
output_compression integer Compression level for lossy formats (JPEG, WebP, AVIF)
T2I Edit
n integer Number of images to generate
Default: 1
Gateway generates multiple images in parallel even if provider only supports 1.
T2I Edit

Additional Parameters

Parameter Type Description Modes
cfg_scale number Classifier-free guidance scale — higher values stick more closely to the prompt
T2I Edit
acceleration fal string The speed of the generation. The higher the speed, the faster the generation.
high none regular
T2I Edit
disable_safety_checker replicate boolean Disable NSFW safety checker
T2I Edit
enable_safety_checker fal boolean If set to true, the safety checker will be enabled.
T2I Edit
enhance_prompt fal boolean Whether to enhance the prompt for better results.
T2I Edit
num_inference_steps integer The number of inference steps to perform.
T2I Edit
output_quality replicate integer Quality when saving the output images, from 0 to 100. 100 is best quality, 0 is lowest quality. Not relevant for .png outputs
T2I Edit
resolution_mode fal string Determines how the output resolution is set for image editing. - `auto`: The model selects an optimal resolution from a predefined set that best matches the input image's aspect ratio. This is the recommended setting for most use cases as it's what the model was trained on. - `match_input`: The model will attempt to use the same resolution as the input image. The resolution will be adjusted to be compatible with the model's requirements (e.g. dimensions must be multiples of 16 and within supported limits). Apart from these, a few aspect ratios are also supported.
T2I Edit
sync_mode fal boolean If `True`, the media will be returned as a data URI and the output data won't be available in the request history.
T2I Edit

Parameter Normalization

How we handle parameters across different providers

Not every provider speaks the same language. When you send a parameter, we handle it in one of four ways depending on what the model supports:

Behavior What happens Example
passthrough Sent as-is to the provider style, quality
renamed Same value, mapped to the field name the provider expects prompt
converted Transformed to the provider's native format size
emulated Works even if the provider has no concept of it n, response_format

Parameters we don't recognize pass straight through to the upstream API, so provider-specific options still work.