FLUX 3 Image free editing demo: a 4-edit test list before you pay

Test recolor, move, replace and swap in the reported free FLUX 3 precise-editing demo, then carry the winners to an API. Sume has no FLUX 3.

4 min readSume
All posts

Use the free FLUX 3 precise-editing demo to run four edit types (recolor, move, replace, swap) on your own image before you pay for API calls. The demo address, flux-tools.bfl.ai/precise-editing, comes from press coverage, not from a BFL page I read, so confirm it works. FLUX 3 Image is not in the Sume image catalog today; check GET /v1/images/models for the live list. The catalog lists FLUX.2 Pro and FLUX.2 Flex.

Four tests that map to real jobs

BFL's overview page lists recolor, replace, move and swap as edit examples, and says references are addressed as <ref_image_0>, <ref_image_1> and so on. A good test plan uses one image per edit type so you can score each separately.

FLUX 3 Image edit tests, read 2026-10-05
TestWhat to checkSume route to compare
RecolorOnly the target colour changesReference edit, ChatGPT Image 2.5
MoveObject lands where intended, gap is filledMask edit, ChatGPT Image 2.5
ReplaceNew object matches lightingReference edit
SwapTwo references trade placesReference edit with 2+ input_references

What to record

Write down each result before you leave the demo: keep the input, the prompt, the output and a yes or no on whether untouched areas stayed the same. Those four items are what you will hand to an API test later.

Carry it to an API

Sume accepts input_references on reference-capable models (max 10, or 16 on ChatGPT Image 2.5) and a mask_url on ChatGPT Image 2.5 only. Test the same four edits there with a prompt that names the change, then compare against what the demo gave you. The Sume docs state no preservation figure, so judge by eye and by pixel diff.

  • Models: openai/gpt-image-2.5, openai/gpt-image-2.5-sunburst.
  • Reference URLs must be publicly reachable.
  • Read usage.cost on each response to see what the test billed.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume