Runway's two Omni Flash ids: 10-11 credits vs 3.4-30 for 1.1

Runway lists gemini_omni_flash at 10 to 11 credits a second and gemini_omni_flash_1.1 at 3.4 to 30. Which is cheaper depends on resolution.

3 min readSume
All posts

Runway sells two Omni Flash ids: gemini_omni_flash at 10 to 11 credits a second and gemini_omni_flash_1.1 at 3.4 to 30. The 1.1 id is cheaper at low resolutions and dearer at 4K. Sume lists only gemini-omni-flash-1.1.

The two ids

At $0.01 per credit, from the Runway pricing page:

Omni Flash ids on Runway (read 2026-10-07)
Runway idCredits per secondDollars per secondResolutions
gemini_omni_flash10 to 11$0.10 to $0.11See page
gemini_omni_flash_1.13.4 to 30$0.034 to $0.30360p to 4K

How to choose

  • Drafts and tests: 1.1 at 360p at 3.4 credits is about a third of the older id's rate.
  • Final renders at 4K: 1.1 costs 30 credits a second, nearly three times the older id.
  • If you do not need Omni's new features, compare the output at the resolution you will ship, not the headline price.

Sume's side

The Sume catalog carries the 1.1 model only: 3 to 10 seconds, 360p, 720p, 1080p and 4K, 16:9 or 9:16, audio always on. I found no older Omni Flash id in the video catalog. Sume bills Google's list times 1.25, so a 720p second is $0.125.

Where the break-even sits

From the Runway page I have only the two ends of the 1.1 range, 3.4 credits at 360p and 30 at 4K, and the older id's 10 to 11. So the break-even lies somewhere between those resolutions, and I cannot place it exactly. At the low end 1.1 is under a third of the older rate; at the top it is nearly three times higher.

If you use the Runway API, price a test at the resolution you ship before choosing an id, and read the pricing page again on the day you run a large batch, since credit tables change. On Sume the question does not arise, because only the 1.1 model is listed.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume