GPT Image aspect ratios: Firefly's 10 vs Sume's 17
Firefly's September 2026 update gives GPT Image 2 ten aspect ratios instead of three. Sume's image API documents 17 ratios plus auto, and custom pixels.

Adobe's September 2026 Firefly update says GPT Image 2 now supports 10 aspect ratios on web and Boards, up from 3. Sume's image documentation lists 17 normalized ratios plus auto, and a model-specific image_size that accepts custom pixel sizes for ChatGPT Image 2.5.
The Firefly change
The Adobe Community post gives the count, not the list, so I do not name which ten ratios Firefly offers.
| Surface | Ratios before | Ratios now |
|---|---|---|
| Web and Boards | 3 | 10 |
The ratios Sume documents
The Image API reference lists these normalized values for aspect_ratio: 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3, 4:5, 5:4, 1:2, 2:1, 1:4, 4:1, 1:8, 8:1, 9:21 and 21:9. That is 17. Use auto to let the provider choose, which the docs recommend on edit and image-to-image calls so the result matches the source shape.
The 17 are the normalized vocabulary, not a promise that every model accepts every one. Each model's supported_parameters.aspect_ratio lists its own values, so read GET /v1/images/models for the model you plan to call.
Custom pixels on ChatGPT Image 2.5
For openai/gpt-image-2.5 and openai/gpt-image-2.5-sunburst, image_size accepts named presets, auto or custom pixels. Both edges must be multiples of 16, the longest edge is at most 3840, the aspect ratio is at most 3:1, and the total is between 655,360 and 8,294,400 pixels.
Do not put custom pixels in size. The docs reserve size for resolution tiers, and explicit pixel size there is rejected in v1.
Choosing between ratios and pixels
- Use a ratio when the platform cares about shape, such as 9:16 for vertical video covers.
- Use
image_sizewhen you need an exact deliverable, such as 1080 by 1350, and the model supports it. - Check the catalog first so a rejected parameter does not cost a retry.
Sources
Related posts
More in Models
- Hume Octave 2 covers 11 languages: is yours one?
Hume Octave 2 is reported to cover 11 languages. Before you pick a voice engine, check your language, then verify what Sume's tts_create recorded for the job.
- HunyuanVideo 1.5 on 14 GB of VRAM: run locally or call an API
The HunyuanVideo 1.5 repo lists 8.3B parameters, 480p to 1080p and a 14 GB VRAM minimum with offloading. A local-run versus API checklist.
- HunyuanVideo 1.5 SSTA and FP8: or just call an API
HunyuanVideo-1.5 has 8.3B parameters, SSTA for a 1.87x speedup at 720p, FP8 GEMM and a 14GB VRAM floor. Decide whether to run it or call a hosted video API.
- Hy Image 3.5 reference limit: 5 or 20, and Sume's caps
Hy Image 3.5's sources disagree on references: 5 in the announcement, 20 in the API guide. Sume's caps differ by model; read input_references from the catalog.
Written by Sume