GPT Image 2.5 Flare vs Sunburst: what each model page says
OpenAI calls Flare its model for everyday image generation and Sunburst its most capable for generation and editing. What each page lists, and both ids on Sume.

GPT-Image-2.5 Flare and GPT-Image-2.5 Sunburst are two image models OpenAI lists side by side. OpenAI's Flare page calls it "our fastest model for high-quality, everyday image generation"; its Sunburst page calls it "our most capable model for image generation and editing". Both take text and image input, both return images, and both use the same token prices, so the choice is about the job, not the price sheet.
On Sume you pick between them with the model field of POST /v1/images: openai/gpt-image-2.5 is Flare and openai/gpt-image-2.5-sunburst is Sunburst. Model facts below come from OpenAI's two model pages and Sume's Image API docs, read 2026-09-29.
What does OpenAI say about each model?
Only what its model pages say. Neither page, as read, gives a side-by-side quality ranking, so this post makes no claim about which output looks better. Test both on your own prompts.
| Item | GPT-Image-2.5 Flare | GPT-Image-2.5 Sunburst |
|---|---|---|
| Positioning | Fastest model for high-quality, everyday image generation | Most capable model for image generation and editing |
| Inputs and outputs | Text and image in, image out | Text and image in, image out |
| Quality settings | low to max | low, medium, high, xhigh, max, auto |
| Image API endpoints | Generations and edits | Generations and edits |
| Token prices per 1M | Text in $5, image in $8, image out $30 | Text in $5, image in $8, image out $30 |
What does Sume list for each id?
The same request surface. The Image API docs say both ids support text-to-image, up to 16 image references, an optional mask_url, and background: auto|transparent|opaque, with quality from auto to max and high as the default when you omit it. They share the same token rates, so a request costs the same on either id at the same size and quality.
The docs add that Sume's Auto model routing continues to use Flare. Sunburst is only used when you name it.
How do I switch between them in one request?
Change only the model string. Everything else in the body stays valid, which makes a fair test cheap: send the same prompt and references to both ids and compare the results yourself.
curl -X POST "https://api.sume.com/v1/images" \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-image-2.5-sunburst",
"prompt": "Keep the person and pose. Change the jacket to dark green.",
"input_references": [
{ "type": "image_url", "image_url": { "url": "https://example.com/portrait.jpg" } }
],
"quality": "medium",
"aspect_ratio": "auto"
}'Which one should I start with?
If you mostly generate from text, start with Flare: it is the id Sume's Auto routing uses, and OpenAI positions it for everyday generation. If your workflow is a chain of edits to the same picture, add Sunburst to the test, because OpenAI describes it as its most capable model for generation and editing. That is a starting point drawn from vendor descriptions, not a measured result.
Sources
Related posts
More in Models
- GPT Image 2.5 quality levels: low, medium, high, xhigh, max and auto
GPT Image 2.5 has six quality values: auto, low, medium, high, xhigh and max. What each does to price on Sume and which one runs when you send nothing.
- GPT Image 2.5 release date and model ids: Flare and Sunburst
OpenAI's GPT-Image-2.5 Flare and Sunburst carry the snapshot date 2026-09-08. The model ids, dated snapshots, and how Sume names the same two models.
- GPT Image 2.5 resolution: the size rules and the 4K ceiling
GPT Image 2.5 takes custom sizes: both edges a multiple of 16, longest edge 3840, 655,360 to 8,294,400 pixels. What that means for 1080p, 1440p and 4K.
- Hailuo 3.0 release date: MiniMax H3 launched 2026-07-31
Hailuo 3.0 is the name people use for MiniMax H3, which MiniMax released on 2026-07-31. What the vendor pages call it, and the ids that reach it on Sume.
Written by Sume