Veo 3.1 Fast: Runway $0.15/s vs Google's $0.10-$0.12

Runway's API lists Veo 3.1 Fast at 15 credits a second ($0.15); Google's Gemini API page lists it at $0.10 (720p) and $0.12 (1080p). An 8 second clip each way.

5 min readSume
All posts

An 8 second Veo 3.1 Fast clip is $1.20 through Runway's API and $0.80 to $0.96 on Google's Gemini API by their own pages, because Runway lists veo3.1_fast at 15 credits per second ($0.15 at $0.01 a credit) and Google lists Fast at $0.10 per second for 720p and $0.12 for 1080p. Sume does not list a Veo id, so the closest Sume rows are given at the end for scale only.

One thing the pages do not settle: Runway tags its Veo rows as audio versions, and the part of Google's page read does not say what is included in each per-second figure. Confirm audio on the vendor you choose before treating the gap as pure reseller margin.

Veo 3.1 per second, three sellers

Standard tier first, since it is the one where the two prices agree.

Veo 3.1 per output second, USD (read 2026-10-03)
TierRunway APIGoogle Gemini API
Standard$0.40 (40 credits)$0.40 (720p, 1080p); $0.60 (4k)
Fast$0.15 (15 credits)$0.10 (720p); $0.12 (1080p); $0.30 (4k)
Litenot listed on the page read$0.05 (720p); $0.08 (1080p)

An 8 second clip

Standard is 8 x $0.40 = $3.20 on both. Fast is 8 x $0.15 = $1.20 on Runway, 8 x $0.10 = $0.80 at 720p on Google, and 8 x $0.12 = $0.96 at 1080p on Google. The Runway premium on Fast is therefore $0.40 per clip at 720p, or 50%, and $0.24, or 25%, against Google's 1080p price.

Across 50 Fast clips that is $60.00 on Runway against $40.00 (720p) or $48.00 (1080p) on Google. If your reason for Runway is its tooling, the premium is the price of that; if it is only the model, the direct page is cheaper.

What Sume offers for the same 8 seconds

Sume's catalog today includes gemini-omni-flash-1.1, which bills the provider list times 1.25 per output second by resolution with native synced audio always on. For 8 seconds that is $1.00 at 720p, $1.50 at 1080p and $3.00 at 4K, per the estimator. That is a different Google model, not Veo, so it answers a budget question and not a like-for-like quality one; the Video Router docs have the full request shapes.

To keep a Veo workflow priced exactly as the vendor states it, call the vendor. To keep reserves, refunds on failure and one USD balance across models, use the Sume ids and budget from the table.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume