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.

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:
| Runway id | Credits per second | Dollars per second | Resolutions |
|---|---|---|---|
| gemini_omni_flash | 10 to 11 | $0.10 to $0.11 | See page |
| gemini_omni_flash_1.1 | 3.4 to 30 | $0.034 to $0.30 | 360p 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
- Seedance 2.5 reference counts: Together's 30/10/10 vs Sume docs
Together lists Seedance 2.5 at 30 images, 10 videos and 10 audio clips per pass. Sume's docs name reference types for it but give no such counts.
- Seedance 2.5 targeted editing: vendor claim vs what Sume accepts
Together says Seedance 2.5 edits specific moments after generation. Sume lists no video_url edit for it; only gemini-omni-flash-1.1 does. The reroll workaround.
- Seedream 5.0 Lite or Nano Banana 2.1 for product shots on Sume
Seedream 5.0 Lite bills $0.04375 per image on Sume against $0.10 for Nano Banana 2.1 at 1K. Ratios, tiers, references and when the extra cost is worth paying.
- Pilot STT in 3 languages: language_code hint vs auto-detect, 30 clips
MAI-Transcribe-2-Streaming advertises 60 languages; here is a 30-clip pilot on Sume STT that compares a language_code hint with auto-detect for about 60 cents.
Written by Sume