Ideogram Topaz Text Refine 8x limit: 8192px math vs Sume upscale

Ideogram's Topaz Text Refine upscales 2x, 4x or 8x and is "rejected when the output would exceed 8192px on either side", so divide 8192 by the factor to get the longest source edge: 4096px at 2x, 2048px at 4x, 1024px at 8x. Sume's image upscaler takes an upscale_factor from 1 to 4, so 8x is not a single call there.

Ideogram facts are from its endpoint reference; Sume facts from the OpenAPI spec and Asset library, read 2026-10-01. The longer discussion of 8x is in the AI image upscaler 8x limit.

What are the Ideogram limits?

The endpoint is POST /v2/image/upscale/topaz-text-refine, multipart, with a source image up to 50MB. The 400 error is described as invalid input or an output over the 8K limit. It returns results directly by default; set async or a webhook_url to get a generation_id and poll.

What does the Sume upscaler accept?

POST /v1/image-upscale-1.0/upscale requires a public HTTPS image_url; upscale_factor is 1 to 4 (default 2) and output_format is png, jpg or webp. The spec states no output pixel ceiling, so test the largest size you need. In MCP the same job is image_upscale_create, a paid tool.

Which input URLs does Sume refuse?

Input URLs must be fetchable public HTTPS. The asset docs say localhost, private-network, non-HTTPS and signed or private URLs, and mismatched content types, are rejected before submission. An oversized request body returns 413 payload_too_large, and an input Sume cannot fetch surfaces image_not_fetchable or input_media_unreachable. Ideogram takes an upload instead; Sume takes a URL.

How do I reach 8x on Sume?

Chaining two calls (for example 2x then 4x) multiplies the factor, but the docs make no promise about quality after repeated passes, so inspect the result. See the image upscale API for the route and exact pixel size for hitting a target.