Tall 1:3 strip on GPT Image 2.5: 1280x3840 passes, 1280x3856 fails
A tall scroll strip on Sume's GPT Image 2.5 can be 1:3 at most. 1280x3840 is exact and legal; one more row of 16 pixels breaks the 3:1 rule.

For a tall strip on GPT Image 2.5, the biggest legal 1:3 size with a 1280 edge is 1280x3840. It is 4,915,200 pixels and exactly 3:1, which is the documented limit. 1280x3856 is only 16 pixels taller, but its ratio is 3.01:1 and Sume rejects it. Use the same logic in reverse for a wide strip.
Rules that apply
The documented custom-size rules (as of 2026-10-08) are: 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 655,360 to 8,294,400 pixels. A tall strip is limited by the 3:1 rule first and by the 3840 edge second. At a 3840 height the widest strip you can ask for is 1280 pixels.
If you want less height, scale in multiples of 16 on both edges. 1024x3072 and 1152x3456 are both exact 1:3 sizes and legal.
| Size | Pixels | Legal | Note |
|---|---|---|---|
| 1280x3840 | 4,915,200 | yes | exactly 1:3, 4,915,200 px |
| 1280x3856 | 4,935,680 | no | ratio 3.01:1, over 3:1 |
| 1024x3072 | 3,145,728 | yes | 1:3, 3,145,728 px |
| 720x2160 | 1,555,200 | yes | 2,160 px edge is fine but 720 is not a multiple of 16 |
Other rows for tall ratios
Not every row needs custom pixels. Nano Banana 2.1 lists 1:4 and 1:8 as aspect_ratio values, and Ideogram V3 and 4.5 list 1:3. If your layout needs a ratio taller than 1:3, those rows are the way to get it, because the GPT rows stop at 3:1.
Read the aspect_ratio descriptor of the row on GET /v1/images/models before you pin a ratio. A model accepts only the values its catalog lists.
curl https://api.sume.com/v1/images/models \
-H "Authorization: Bearer $SUME_API_KEY"Validate
Run this before submitting.
def legal(w, h):
px = w * h
return (w % 16 == 0 and h % 16 == 0 and max(w, h) <= 3840
and max(w, h) / min(w, h) <= 3 and 655_360 <= px <= 8_294_400)
for w, h in [(1280, 3840), (1280, 3856), (1024, 3072)]:
print(w, h, w * h, legal(w, h))Tall and wide ratios side by side
The 3:1 limit is symmetric, so everything here holds for a wide strip with the edges swapped. The table lists the largest legal size for tall ratios, plus the smallest at 1:3.
| Ratio | Largest size | Pixels |
|---|---|---|
| 1:2 | 1920x3840 | 7,372,800 |
| 1:3 | 1280x3840 | 4,915,200 |
| 2:3 | 2336x3504 | 8,185,344 |
| 9:16 | 2160x3840 | 8,294,400 |
A note on 1080-wide layouts
Designs often start from a 1080 px width, but 1080 is not a multiple of 16 (67.5 x 16). Round to 1088 and crop two 4 px edges in your own tooling, or ask for 1024 and scale up. 1088x3264 is a legal exact 1:3 size at 3,551,232 pixels, so a 1080-wide scroll panel fits with a small trim.
Validate the size before you send. Both edges must be multiples of 16, the longest edge is at most 3840, the ratio is at most 3:1, and the total is 655,360 to 8,294,400 pixels. A check of those four rules in your own code turns a 400 into a message you control, and it costs nothing. Run it on user-entered sizes in particular, since a person typing a height will often overshoot by a few pixels, as 3856 does here. If the number fails, snap the long edge down to the nearest multiple of 16 that keeps the ratio at 3:1 or flatter, and show the user the result.
Sources
Related posts
More in Developers
- rate_limited or queue_full? One Python submit handler for both 429s
Two different 429s need two different waits. A Python handler reads error.code, sleeps on retry-after for rate_limited, and waits for capacity on queue_full.
- Ten Sume job error categories and which ones are worth a retry
Sume failed jobs carry a category such as validation, quota or worker_timeout. Map all ten to retry, fix, top up or support in one small Python table.
- Self-test a Python Sume verifier: rotation, stale time, empty secret
Six asserts for a stdlib hmac verifier: new and old secret both pass, tampered body fails, 301 seconds old fails, empty secret raises. One file, no framework.
- Test an Omni edit prompt at 360p first: 23 cents vs 113 at 1080p
Edit mode on Gemini Omni Flash 1.1 takes resolution as an option. Try the edit at 360p, then render the winner at 1080p. Arithmetic for a 6 s clip.
Written by Sume