Adobe Firefly Image 5 API: native 4 MP vs Sume resolution tiers

Adobe's Firefly API overview describes the Image5 model as its latest, with native 4 MP resolution and a new Instruct Edit capability. Sume's image docs do not name a Firefly model, so you cannot call Image5 through Sume. What Sume offers is a normalized resolution tier of 512, 1K, 2K or 4K on the models that list it.

Adobe facts are from its overview page; Sume facts from the Image API docs, read 2026-10-01.

What does Adobe say Image5 does?

The page calls Image5 "a leap forward in realism, lighting, and composition" with native 4 MP resolution across photography, text and illustration. Instruct Edit lets you generate and refine in one workflow using natural language edits. It also points existing Firefly API users to a migration guide.

What are Sume's resolution tiers?

The docs define resolution as a "Normalized tier (512, 1K, 2K, 4K)" and say a model only accepts the values its catalog descriptors list. Read supported_parameters before pinning a tier. Slow configurations such as 4K, high quality and large n are the most likely to return a 202 job envelope.

Can I compare pixel counts directly?

Not from these pages. Adobe gives megapixels; Sume gives tiers, and the docs do not map each tier to a pixel count in the sections cited here. Check the catalog entry for the model you plan to use and measure the file you get back.

What happens if I send sume/auto?

Sume picks the family for you and never discloses which one ran. It is not listed in GET /v1/images/models, and job.model stays sume/auto. If you need a known family, pass a catalog id; see picking a model for product photos.