Ideogram resolution options and what they cost
·
Ideogram v3 does not expose a top-level resolution selector through the current
Genace image endpoint. Earlier wording on this page incorrectly described a
fixed 480p tier and validation errors for other resolutions. That did not match
the request mapper or provider schema and has been corrected.
Follow the actual request contract
The public image route builds a selected parameter object. It maps
aspect_ratio, image references, count, seed and negative prompt, but it does
not map resolution. Adding "resolution": "1080p" at the top level therefore
does not request a documented 1080p image and does not establish an
unsupported-resolution validation error.
The provider’s standard image schema likewise has no resolution field. Do not infer support from a generic schema parse succeeding: an object schema may silently discard unknown keys. Review the normalized output rather than only checking whether parsing threw an exception.
Inspect the actual output
Download a completed image and inspect its decoded pixel dimensions. Record those dimensions alongside the job ID and original output before producing website derivatives. An aspect ratio describes shape, not an exact pixel size. A successful generation alone does not prove that a delivery specification has been met.
If your placement needs a precise width and height, create a reviewed crop or resize in your own media-processing stage. Keep the original unchanged and avoid claiming that upscaling restores details that were never present.
Budget using supported fields
The local standard price is 6 credits per requested image, multiplied by
n. A top-level resolution value is not a documented lower-price switch.
Do not use video-model resolution tiers to estimate this image model’s cost.
The provider also forwards an extra object after standard mapping; arbitrary
upstream overrides are not a validated resolution contract and can invalidate
your request assumptions.
Review Ideogram v3 aspect ratios, image request validation, and delivery derivatives for distinct request and post-processing responsibilities.
Continue with models and parameters
Models covered on this page
Where these facts come from
- codebase: src/app/api/v1/images/generations/route.ts
- codebase: src/ai/providers/ideogram.ts — paramsSchema and pricing()