Flux 1 Dev Edit
bfl/flux-1/dev/editFlux 1 Dev Edit is BFL's intelligent image editing model. Transform, retouch, and reimagine existing images using text prompts - from background replacement to artistic style conversion.
- Base price
- $0.03USD / run
- Execution
- async
- Model type
- image
- Input fields
- 7
Try the model
Playground
PNG, JPEG, WebP, or GIF · 20 MiB maximum
Your output will appear here
Complete the inputs, then click Run.
Model card
Specifications
Pricing
- Base price
- $0.03 / run
Context & modalities
- Input
- Schema-defined
- Output
- image
Capabilities
- Chat
- Not supported
- Vision
- Not supported
- Reasoning
- Not supported
- Structured output
- Not supported
- Function calling
- Not supported
- Audio input
- Not supported
Access
- Provider
- BFL
- Model ID
- bfl/flux-1/dev/edit
- Execution
- async
- Base URL
- https://api.sandbase.ai
- API
- Unified Run API
- Endpoint
- /v1/run
API README
Flux 1 Dev Edit
Flux 1 Dev Edit uses the development-oriented FLUX model for source-image revision, allowing object, background, style, color, and composition changes while retaining the reference as visual context. It brings editable behavior into experimental and customizable pipelines rather than limiting FLUX.1 Dev to prompt-only creation.
Use it for local editing prototypes, custom tools, research, and adapted revision workflows. Explain the desired final state, identify what must stay unchanged, and describe how new content should match perspective, material, light, texture, and subject identity across the edited image.
Highlights
- Development-grade image editing. Applies natural-language changes inside a customizable FLUX workflow.
- Source-context understanding. Uses the existing image to guide geometry, identity, and appearance.
- Preservation-aware reconstruction. Keeps unrequested regions connected to the original composition.
- Custom editing research. Supports experimentation with adaptation and source-led generation behavior.
Pricing
| Billing unit | Price |
|---|---|
| Per request | $0.025 |
When to Use
| ✅ Good fit | ❌ Consider alternatives |
|---|---|
| The model's named workflow matches the source material and intended output | A different input modality or model route is required |
| A managed asynchronous result is suitable for the production pipeline | A synchronous, interactive editor is essential |
| The documented controls cover the required duration, framing, or format | The project needs controls outside this endpoint's schema |
| Creative iteration benefits from a repeatable request structure | Exact deterministic pixels, frames, geometry, or samples are mandatory |
| A finished downloadable media asset is the desired deliverable | Editable source layers or a native project file are required |
Prompt Guide
For image-conditioned generation, state the intended result first, then add the subject or source treatment, progression, style, and delivery constraints. Keep one creative variable per phrase, use the documented field names for controls, and change one setting at a time when comparing results.
{
"image": "https://example.com/start-frame.png",
"output_format": "jpeg",
"prompt": "A cat dressed as a wizard with a background of a mystic forest."
}
Technical Specs
| Spec | Value |
|---|---|
| Model ID | bfl/flux-1/dev/edit |
| Inputs | guidance_scale, image, num_inference_steps, output_format, prompt, seed, strength |
| Required inputs | prompt, image |
| Output fields | content_type, url |
| Execution | Async (submit, then poll for result) |
| Output Format | jpeg / png |
Related Models
bfl/flux-1/dev— Compare this concrete local family route.bfl/flux-1/dev/image-to-image— Compare this concrete local family route.bfl/flux-1/dev/redux— Compare this concrete local family route.
Start building
Send your first request
OpenAI-compatible endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"model": "bfl/flux-1/dev/edit",
"image": "https://static.sandbase.ai/examples/bfl/flux-1/dev/edit/input_image_0.png",
"prompt": "A cat dressed as a wizard with a background of a mystic forest.",
"strength": 0.95,
"output_format": "jpeg",
"guidance_scale": 3.5,
"num_inference_steps": 40
}
SANDBASE_JSON
)
run_id=$(printf '%s' "$result" | jq -r .id)
for attempt in $(seq 1 120); do
status=$(printf '%s' "$result" | jq -r .status)
case "$status" in completed|failed|timeout) break ;; esac
sleep 2
result=$(curl --fail-with-body --silent \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
"https://api.sandbase.ai/v1/run/$run_id")
done
status=$(printf '%s' "$result" | jq -r .status)
[ "$status" = completed ] || { echo "Generation ended: $status" >&2; exit 1; }
printf '%s\n' "$result"Choose your model
Compare models
| Model | Type | Default price | Released |
|---|---|---|---|
Flux 1 Dev EditThis model BFL | Image | $0.03 / run | Jul 11, 2024 |
BFL | Image | $0.05 / run | Oct 1, 2026 |
BFL | Image | $0.05 / run | Oct 1, 2026 |
BFL | Image | $0.02 / run | Jan 15, 2026 |
BFL | Image | $0.02 / run | Jan 15, 2026 |
BFL | Image | $0.01 / run | Jan 15, 2026 |
Questions
FAQ
How do I call BFL Flux 1 Dev Edit through SandBase?
Create a SandBase API key, then send requests with the model ID "bfl/flux-1/dev/edit" to Unified Run API (/v1/run) at https://api.sandbase.ai. The request examples on this page show the exact payload.
Do I need a separate BFL account?
No. One SandBase API key and balance gives you access to BFL Flux 1 Dev Edit and the other models in the catalog; you do not need to sign up with BFL separately.
