Nano Banana Pro vs GPT Image 2.5 for 9:16 covers: 18.8 vs 3.6 cents
A 9:16 cover bills $0.1875 on Nano Banana Pro and about $0.036 on GPT Image 2.5 high at 720x1280 on Sume. Twenty covers: $3.75 vs $0.71.

For a 9:16 cover, Nano Banana Pro bills $0.1875 per image on Sume and ChatGPT Image 2.5 at high quality bills about $0.0356 at 720x1280. Twenty covers are $3.75 against $0.71. Both list 9:16, so the ratio is not the deciding factor; price, resolution control and your own eyes on the output are. The Image API docs define both request shapes.
This is a cost comparison, not a quality ranking. Vendor claims about how each model looks belong on each vendor's own page, and the only honest test is the same prompt on both.
How do I ask each model for 9:16?
Nano Banana Pro takes a ratio and a resolution tier. GPT Image 2.5 takes either a ratio or explicit pixels, and explicit pixels are what the price below assumes. When both image_size and aspect_ratio are sent, image_size has priority.
| Field | Nano Banana Pro | GPT Image 2.5 |
|---|---|---|
| model | google/nano-banana-pro | openai/gpt-image-2.5 |
| Shape | aspect_ratio: "9:16" | image_size: {width: 720, height: 1280} |
| Size control | resolution: 0.5K, 1K, 2K or 4K | Multiples of 16, max edge 3840 |
| Quality | Not offered | auto, low, medium, high, xhigh, max |
What do twenty covers cost?
Nano Banana Pro's row is the 1K default; its 4K tier is listed higher and Sume scales the reservation for it. GPT Image 2.5 moves with quality.
| Model and tier | Per cover | Twenty covers |
|---|---|---|
| GPT Image 2.5, low, 720x1280 | $0.0040 | $0.08 |
| GPT Image 2.5, medium, 720x1280 | $0.00925 | $0.185 |
| GPT Image 2.5, high, 720x1280 | $0.0356 | $0.71 |
| Nano Banana Pro, default tier | $0.1875 | $3.75 |
How do I decide?
Generate three covers per model for the same prompt, put them side by side, and look for text errors and edge artifacts at phone size. If GPT Image 2.5 is good enough, it is 5 times cheaper at high. If you need Nano Banana Pro's resolution tiers or 21:9 and 4:5 ratios, that is what you pay for. Prices here are list x 1.25 in dollars per image before whole-cent rounding; the catalog's billable formula reads "list x 1.25, ceil usd cents", so confirm the first charge in usage.cost and budget from the invoice, not from the sum.
Sources
Related posts
More in Comparisons
- Notion Agent SDK beta vs Sume Agent Completions: run agents from code
Notion's SDK continues agent chats and streams results. Sume's Agent Completions are one-shot 202 runs you poll or get by webhook. See which fits your backend.
- Nova Canvas 4,194,304 pixel cap and 16 px rule vs Sume image_size
Nova Canvas output sides must divide by 16 and total under 4,194,304 pixels. GPT Image 2.5 on Sume has its own custom-size rules. A side-by-side check.
- Nova Canvas IMAGE_VARIATION similarityStrength vs Sume n and reference
Nova Canvas IMAGE_VARIATION takes 1 to 5 images and a similarityStrength of 0.2 to 1.0. Sume has no strength field; here is how to get variations.
- Nova Canvas inpainting mask rules vs a Sume reference edit
Nova Canvas inpainting wants a pure black and white mask, same size as the input. What to build, and how Sume's edit call differs.
Written by Sume