GPT Image 2.5 widest banner: 3072x1024 at 3:1, with output cost
GPT Image 2.5 stops at 3:1. 3072x1024 passes the multiples-of-16 and pixel rules; 4:1 and 8:1 banners need another model. Output estimates by quality.

GPT Image 2.5's widest legal shape is 3:1, and 3072x1024 fits every rule: both edges are multiples of 16, neither edge exceeds 3840, and the area is 3,145,728 pixels, inside the 655,360 to 8,294,400 range. At that size the output estimate is $0.00741 on medium and $0.02964 on high. A 4:1 or 8:1 banner is outside the model's limits, so use a model that lists those ratios.
The rules, applied
OpenAI's image generation guide gives the custom size limits, and Sume's Image API page repeats them: multiples of 16 on both edges, maximum edge 3840, aspect ratio at most 3:1, 655,360 to 8,294,400 pixels. 3072 is 192 x 16 and 1024 is 64 x 16. A 4096x1024 banner fails twice: the edge exceeds 3840 and the ratio is 4:1.
| Size | Ratio | Passes? | Reason |
|---|---|---|---|
| 3072x1024 | 3:1 | Yes | Multiples of 16, ratio at the limit |
| 3840x1280 | 3:1 | Yes | Edge at the 3840 cap |
| 4096x1024 | 4:1 | No | Edge above 3840, ratio above 3:1 |
| 1500x500 | 3:1 | No | 1500 is not a multiple of 16 |
| 1536x512 | 3:1 | Yes | Both edges multiples of 16, area 786,432 |
Output estimate at 3072x1024
Computed from the output token formula in Sume's pricing code for GPT Image 2.5 at $30 per million output tokens, before input tokens and Sume pricing. The docs themselves publish only the 1024x1024 xhigh and max figures. The values below are lower per pixel than the 1024x1024 figures because the short edge sets the token grid.
| Quality | Estimate per image |
|---|---|
| low | $0.00309 |
| medium | $0.00741 |
| high | $0.02964 |
| xhigh | $0.05187 |
| max | $0.11856 |
A request
Pass the size as image_size in WIDTHxHEIGHT form; image_size wins over aspect_ratio, and the docs say sizes without a verified GPT pixel mapping reserve the output upper bound, so an explicit size gives the tighter estimate. The normalized aspect_ratio list in the docs has no 3:1 value, so do not use it for this banner. OpenAI also notes that resolutions above 2560x1440 are experimental, so test 3072x1024 before you commit to it.
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",
"prompt": "A wide coastal panorama at dusk, empty sky on the left for headline text",
"image_size": "3072x1024",
"quality": "medium"
}'When you need wider
Taller ratios than 3:1 need another family: the Sume docs list 4:1, 1:4, 8:1 and 1:8 among the normalized aspect_ratio values, but a model only accepts the values its catalog descriptors list. Read supported_parameters first. A banner that is a multiple of 16 on one family may not be on another.
Sources
Related posts
More in Developers
- GPT Image 2.5 returns base64; Sume returns a URL: port the code
OpenAI's image API returns base64 data for GPT Image models, and Sume's returns hosted URLs. The three lines that change when you move a decoder over.
- GPT Image 2.5 can take two minutes: handle the 202 job on Sume
OpenAI says complex GPT Image 2.5 prompts can take up to two minutes. Sume blocks 30 seconds, then returns a 202 job. Submit async, poll, and fetch the result.
- One config file for gpt-image ids before December 1
OpenAI retires gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest on 2026-12-01. Keep image ids in one map, and test Flare and Sunburst on Sume now.
- Grok Imagine video API: 15 s, 5 references, request-ID polling
xAI's video guide for grok-imagine-video-1.5 lists up to 15 seconds, up to 5 reference images and async polling by request ID. The same loop on Sume jobs.
Written by Sume