How should I choose between flux-2-max and flux-2-pro?
max is better suited for tasks that prioritize overall quality, complex prompt execution, and editing consistency; pro emphasizes a balance between quality and speed. For large volumes of everyday assets, compare pro first; for key hero visuals or work that requires repeated fine-tuning, try max first.
Can flux-2-max edit existing images?
Yes. When calling it, select action=edit and provide image_url, prompt, and size in aspect-ratio format. The prompt should describe the specific changes and indicate the subject or composition that needs to be preserved. After completion, obtain the result through the returned image link; count does not apply to editing tasks.
Should size be written in pixels or as an image aspect ratio?
This model uses image aspect ratios, for example, enter 1:1 for a square image, 16:9 for a landscape image, and 9:16 for a portrait image. Do not enter pixel dimensions such as 1024x1024; both generation and editing requests should explicitly provide size and describe the composition around the target canvas ratio.
Do I still need design tools when generating packaging text?
It is recommended to keep design tools for final layout work. max can participate in visual creation that includes text, but precise labels, long copy, and small-font content need to be checked; when text and details are the priority, you can also compare flex. The final version should proofread the text, positioning, and product information.
How do I integrate flux-2-max into backend image tasks?
Submit model=flux-2-max to POST /flux/images, and provide the operation, prompt, and aspect ratio. You can use async=true to obtain task_id and then check progress, or configure callback_url to receive the completed result, then read image_url in data to deliver the image.