Ideogram ad resizer API safe zones vs Sume aspect_ratio 4:5
Ideogram's ad resizer returns an exact WIDTHxHEIGHT inside a platform safe zone. Sume's image route picks an aspect_ratio and resolution tier instead.

Ideogram's ad resizer reframes an ad to an exact WIDTHxHEIGHT and, with platform, keeps it inside that platform's safe zone. Sume's image docs describe no safe-zone parameter: you choose an aspect_ratio and a resolution tier (512, 1K, 2K, 4K), and exact pixels are not guaranteed.
Ideogram facts are from its ad resizer page; Sume facts are from Image models, read 2026-10-01.
What does the Ideogram ad resizer guarantee?
Per the page, each output image has exactly the requested pixel dimensions, with or without a platform. With platform, the ad is generated inside the largest rectangle that fits that platform's safe zone for the requested ratio, and the surrounding space is filled in. A resolution outside the platform's accepted list is rejected with a 400.
| `platform` | Accepted resolutions |
|---|---|
google, tiktok | 1920x1080, 3840x2160, 1080x1080, 2400x2400, 2880x2880, 1080x1920, 2160x3840 |
meta_stories, meta_reels, meta (legacy), snapchat | 1080x1920, 2160x3840 |
What does Sume offer for ad-shaped images?
Normalized fields: resolution is a tier of 512, 1K, 2K or 4K, and aspect_ratio includes 1:1, 16:9, 9:16, 4:5 and others. The docs note that 4:5 is Instagram portrait (1080x1350), not 4:3, and that a model only accepts the values its catalog lists. They also say not to put custom pixels on size.
Can Sume hit 1080x1350 exactly?
The docs say one model sends aspect_ratio: "4:5" at a native size of about 928x1152 at 1K, and that exact 1080x1350 is a documented post-step via job target_pixels. See the 1080x1350 post before relying on exact pixels; there is no per-platform safe-zone control to lean on, so keep key text away from the edges yourself.
How do I resize an existing ad on Sume?
For edit and image-to-image calls, prefer aspect_ratio: "auto" to match the reference; omitting the field is not the same as auto. A parameter the model does not list is rejected with 400 unsupported_parameter, so there is no silent platform fallback. Check the output dimensions before you upload to an ad platform.
Sources
Related posts
More in Use cases
- Ideogram ad variations API: one axis per call vs Sume n
Ideogram's ad-variations tool varies people, setting, group_size or scene. Sume has no axis field: describe the change in the prompt and set n up to 10.
- Ideogram ghost mannequin API views vs Sume input references
Ideogram's ghost-mannequin tool takes front, back, left, right, top and bottom photos and a required view. Sume takes a flat input_references list.
- Ideogram model pose variants API vs a Sume edit prompt
Ideogram's pose tool takes an `instruction` field. Sume has no pose endpoint: you edit with a prompt, references and n up to 10 per call.
- Ideogram Sketch to Render API vs a Sume image reference edit
Ideogram's Sketch to Render turns a fashion sketch into garment imagery. On Sume, send the sketch URL in image_urls with a prompt describing materials.
Written by Sume