Veo 3.1 Standard charges the same at 720p and 1080p; Omni does not

Google bills Veo 3.1 Standard at $0.40 per second for 720p and 1080p. Omni 1.1 Flash on Sume goes from $0.125 at 720p to $0.1875 at 1080p. Read 2026-10-04.

5 min readSume
All posts

On Google's own pricing page, Veo 3.1 Standard is $0.40 per second at both 720p and 1080p and $0.60 at 4K (read 2026-10-04). Gemini Omni 1.1 Flash is priced per token, about $0.10 per second at 720p. Sume ships the Omni model, not Veo, and bills it at $0.125 per second at 720p and $0.1875 at 1080p.

So on Veo you pay no premium to step up to 1080p, and on Omni you do: 50 percent more per second.

What do the two price lists say?

Google's pricing page lists Veo 3.1 Fast at $0.10, $0.12 and $0.30 per second and Lite at $0.05 and $0.08 for the tiers it offers. The Veo 3.1 previews are scheduled to shut down on October 22, 2026, with Google pointing developers at gemini-omni-1.1-flash.

Sume's Omni rows are the provider list times 1.25, rounded up to the cent per job.

Veo 3.1 Standard (Google list) vs Omni Flash 1.1 on Sume, per second, read 2026-10-04
TierVeo 3.1 Standard (Google)Omni 1.1 Flash (Sume billed)
360pnot listed$0.0375
720p$0.40$0.125
1080p$0.40$0.1875
4K$0.60$0.375

Does the Omni premium matter?

At 8 seconds, 1080p Omni is $1.50 on Sume against $1.00 at 720p. The extra $0.50 buys the sharper tier. If the final goes to a phone feed, 720p is usually enough and the premium is wasted; if it goes to a large display, pay it for the keepers only.

The Veo comparison is not like for like. Veo 3.1 is a different model with its own look, and Sume does not route it. The point of the table is how each list charges for resolution.

What happens to Veo 3.1 workloads?

Google's documentation lists the Veo 3.1 previews (Lite, Standard and Fast) as shutting down on October 22, 2026, so the question is where those requests go next. On Sume, sume/auto defaults to Omni Flash 1.1 and accepts 3 to 10 seconds at 720p, in 16:9 or 9:16, with audio always on.

  • Pin gemini-omni-flash-1.1 for 360p, 1080p or 4K.
  • Use sume/auto for 3 to 10 second 720p clips when the family does not matter.
  • Expect a 400 unsupported_capability from Auto for 2 seconds, 11 seconds, 480p, 768p or generate_audio: false.

How do you compare on your own prompts?

Run the same prompt at 720p and 1080p and compare usage.cost on the two polls.

import os, requests

H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}
for res in ("720p", "1080p"):
    r = requests.post(
        "https://api.sume.com/v1/videos",
        headers=H,
        json={
            "model": "gemini-omni-flash-1.1",
            "prompt": "A chef plates a dish, close-up",
            "duration": 8,
            "resolution": res,
            "aspect_ratio": "16:9",
        },
    )
    print(res, r.status_code, r.json()["id"])

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume