FLUX Kontext Pro
Earlier model guide Explore current task guides ↗
Image editing. Edit a selected image with a written direction. Availability depends on your plan and configured models.
Start creating in Chat ↗Edit from one selected image
FLUX Kontext Pro uses an eligible image as the source for a separate whole-image result.
Bind the right revision
Select the exact coffee-bag image to change. Ask for a brighter kitchen setting, then verify the source, supported aspect and cost before submission.
Compare the result with its source
The edit is saved as another candidate. Inspect the bag, label, text and other details that may have changed along with the background.
An edit can change more than you requested
The source remains available if the new image drifts. Compare exact versions before choosing, or read the image-edit outcome for the full path.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartSelect an eligible exact coffee-bag image.
- Request or actionChoose Edit image and review the FLUX Kontext Pro route.
- ReviewCheck the bound source, settings, quote and packaging drift.
- Saved resultA new whole-image candidate.
- ContinueCompare it with the original.
Example AskGL request
Put this selected coffee bag in a warmer kitchen setting. Keep the bag as the main subject.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Continue from the output
Good to know.
Creation notes
Prepare your starting point
Choose the exact eligible source and inspect its visible attachment before describing a revision. Keep supporting inspiration separate from the image being changed. Explain a concrete lighting, setting or composition change and review the controls exposed by a compatible editing route.
Image editing workflowReview what you keep
Compare the intended change and the rest of the whole image. Check packaging, lettering, edges and subject proportions for drift. Keep the original available and choose an exact accepted revision before reusing it in a native design or preparing another operation.
Compare related modelsCommon questions
Does an earlier guide mean this model is deprecated?
Guide age and model lifecycle are different. Check current catalog status and workspace availability; do not infer retirement from the route name.
Can another model replace it silently?
Choose a compatible replacement explicitly and review a fresh quote. Keep the recorded original model and its saved results identifiable.