What happened?

On 8 September 2026, OpenAI shipped ChatGPT Images 2.5. The volume number is the one that makes the rest of the post make sense: more than 3 billion images a week across ChatGPT Images and the GPT-Image API models. The consumer SKU is on for every ChatGPT, ChatGPT Work, and Codex seat - desktop, mobile, web.

The API split is two model ids at one rate card. gpt-image-2.5-flare is the default: OpenAI says higher quality than GPT-Image-2 at 50% lower latency, and "up to 50%" versus Images 2.0. The API clip is slightly different: Flare is over 50% faster than GPT-Image-2 at equal quality. gpt-image-2.5-sunburst is the slow twin - tighter control across edits, longer generation. List price is the same as GPT-Image-2: image $8 / $2 cached / $30 per 1M tokens, text $5 / $1.25 cached. Sunburst is not a dearer SKU. You pay in wall-clock. The public batch table still lists gpt-image-2, not 2.5.

ChatGPT got a control surface, not just a sharper decoder. Sketch (@Sketch) lets you draw a layout in-chat and use it as the reference. Templates cover formats such as posters and merch. You can drop comments on a generated image and share the prompt so someone else reruns it on their own photos. Both API models do transparent backgrounds.

Early pipes already swapped it in: Adobe Firefly, Runway, Higgsfield, Manus. Manus's eval is the outlier on speed - Flare two to four times GPT-Image-2 in their tests. Higgsfield's line is the product claim: it understands what not to change.

Why this is interesting

  • The un-edit is the product: At 3 billion images a week the bottleneck is not "can it draw a tuxedo." It is whether the child, the logo, and the lighting survive the next instruction. OpenAI's own pitch is surgical: change one product, one background, one line of copy; keep subject, composition, brand. Multi-turn is the production test - earlier edits should not rot. That is how you stop regenerating the campaign from scratch every comment.

  • Two clocks, one sticker: Flare and Sunburst bill identically. The SKU choice is latency versus precision, not a price tier. OpenAI's 50% figure and Manus's 2-4x are not the same measurement; do not flatten them. If your loop is high-volume social and UGC, Flare is the pipe. If the asset has to survive a brand review, Sunburst is the one that costs you minutes, not extra dollars.

  • Control left the prompt box: Sketch, templates, in-image comments, remixable prompts. The lab is productizing the brief - layout, format, local notes - because a paragraph of English is a bad spec for a flyer. @Sketch is ChatGPT-side. The API still speaks prompt plus reference image. That gap is the next surface.

  • Image gen is a component now: Firefly, Runway, Higgsfield, Manus. The interesting distribution is not "people open ChatGPT to make a picture." It is that Adobe and Runway will serve 2.5 inside tools that already own the timeline. Provenance follows: C2PA metadata plus Google DeepMind SynthID on ChatGPT, Codex, and the API. The system card is explicit that 2.5's realism raises deepfake risk; the watermark is the receipt, not the policy.

  • Do not read the safety table as a win: On an adversarial set (not production traffic), unsafe images presented: Sunburst 1.09%, Flare 1.41%, Images 2.0 1.64%. OpenAI's own footnote: no unsafe-shown difference versus 2.0 meets p < 0.05. Bio/Cyber High: not crossed; they still treat biological risk as High and block it. The stack is prompt refusals plus input/output monitors. It is not a new safety story. It is the same stack, sharper pixels.

Bottom line

Images 2.5 is not a new aesthetic. It is OpenAI admitting that at this volume the job is identity-preserving edits, then shipping two clocks at GPT-Image-2's sticker so you can pick speed or control. Sketch and comments are the consumer version of that brief. Firefly and Runway are the distribution. If your workflow is "generate until it looks right," Flare just got cheaper in time. If your workflow is "change the headline, keep the talent," that is the actual launch.