Runway image credits: Muse 1, Gen-4 Image 5-8, Gemini Flash 5-16

Runway's developer pricing guide (read 2026-10-02) lists muse_image at 1 credit per image, gen4_image at 5 to 8 credits and gemini_image3.1_flash at 5 to 16 credits by resolution. At $0.01 per credit that is $0.01, $0.05 to $0.08 and $0.05 to $0.16 per image, so 100 images cost $1, $5 to $8 or $5 to $16.

The three image rows

The page labels these as sample models, so it is not a full list. The 100-image column is the per-image range times 100.

Ranges are a planning problem

Two of the three rows are ranges. For gen4_image the page gives 5 to 8 credits without telling me, in the text I read, which setting moves it; for the Gemini row it says resolution does. When you budget, take the top of the range for a batch you have not specified yet, and the bottom only once you have fixed the settings and seen one real charge.

The Muse row is the outlier: at $0.01, a thousand images is $10. That is cheap enough that review time, not generation cost, becomes the real expense.

How Sume bills images

Sume bills images per request, and the image docs say the endpoint pricing lines are the amount charged to your wallet with Sume's margin already applied, so cost_usd times n is what you pay. Billing is all-or-nothing: a completed generation is billed in full, and a failed or cancelled one is not billed.

Sume lists image models in its own catalog, and the ids Runway uses are Runway's names, not Sume ids. For what Sume carries for Meta's image model, see the Muse catalog post. Do not look for muse_image in a Sume request.

A budgeting habit

Before a large image batch, generate one image per model you are considering, read the actual charge from the ledger or the response, and multiply. Credits on one platform and dollars on another only become comparable once you have a real number from each.