GEMINI OMNI PROMPTS

Field Guide

Gemini Omni Prompt Guide

A practical field guide. What works, what breaks, what to avoid. Based on DeepMind's official prompt guide + community testing from PixVerse, Atlas Cloud, Chrome Unboxed, and Medium's Gemini Omni Prompt Playbook.

What changed in the last 30 days

A dated timeline of every material change since launch. We update this whenever something shifts.

Source tier: 🟢 official Google/DeepMind · 🟡 reputable hands-on / news · 🔴 unverified.

Who can use Gemini Omni Flash (and what it costs)

Access tiers (post I/O 2026 restructure)

TierPrice / monthWhat you get for Omni
Google AI Plus$7.99Gemini app + Google Flow access to Omni Flash
Google AI Pro$19.99Higher quota; per-prompt cap (from May 28 update)
NEW Ultra (creator)$99.995× Pro usage, 20TB storage, YouTube Premium bundled
Existing Ultra$200 (was $250)20× Pro usage, 12,500 AI credits, Project Genie / Mariner
Free path$0YouTube Shorts & YouTube Create App (18+, certain limits)

Source: Google One AI Subscriptions blog 🟢.

Per-generation credit cost (open question)

Google has not published a per-generation credit cost for Omni Flash inside Google Flow. The best available signals as of 2026-05-29:

Practical takeaway: if your generation didn't produce what you wanted, re-generate, don't edit. Editing burns more credits and frequently produces output that's visually indistinguishable from the original.

Where to use it

The base formula

Most working Gemini Omni prompts follow this structure:

[Subject] + [Action] + [Setting] + [Camera] + [Lighting] + [Style]

Example: "A red panda chef tossing pizza dough, in a cozy mountain kitchen, low-angle close-up, warm tungsten light, Pixar-style 3D animation".

This is the same DNA as Sora / Veo prompts, but Omni adds two unique elements that most other models don't have:

The opening-line trick

Lock these three things in the very first sentence:

Create a [duration]-second [aspect-ratio] [genre] video in one continuous shot.

Why: Omni interprets "one continuous shot" as "no cuts" and respects the time / aspect ratio you specify upfront. Specifying these inline beats putting them in metadata.

Camera vocabulary Omni understands

From DeepMind's prompt guide, these terms are explicitly parsed:

Camera motion verbs

Style references

Duration sweet spots

GoalBest durationAspect ratio
Mood / cinematic8-10s16:9 or 2.39:1
Product hero6-8s1:1 or 16:9
Reels / TikTok / Shorts5-7s9:16
Slow-motion impact5-6s1:1 or 16:9
Timelapse10s (max)16:9
Avatar talking head10s (max)16:9 or 9:16

Gemini Omni Flash hard limit: 10 seconds per clip. Source: TechCrunch launch coverage.

The "Keep X identical" lock

When using conversational editing (Omni's flagship feature), every follow-up turn should explicitly list what to preserve. Pattern:

[Change instruction]. Keep [X, Y, Z] exactly the same.

Without this lock, Omni may re-style the entire scene when you ask it to change one element — losing the consistency that's the whole point of conversational editing. (Documented by Atlas Cloud's hands-on testing.)

The trigger pattern (for VFX)

One of Omni's strongest patterns — used in Google's own viral demos (mirror-arm-transformation, bubble sculpture, origami ships):

[Base scene]. When [specific trigger action], [specific transformation]. Keep [list] identical.

Example: "A woman reaches toward a mirror. When her fingertips touch the glass, make the mirror ripple like liquid and her arm turn to reflective mirror material. Keep the parlor and lighting identical."

"It's blocking my prompt" — the two bugs you need to keep straight

Since launch, the phrase "Gemini Omni is blocking my prompts" has been used to describe two completely different bugs. Mixing them up is the most common source of confusion in the community right now.

Bug A — The false-positive policy block (still unresolved as of 2026-05-29)

Omni rejects clearly harmless prompts (Cat walks between rabbits, Change the background to night) with a generic "I can't generate that video" / "policy violation" message — claiming a rule violation that doesn't exist. Widely reported from 2026-05-19 onward. Google VP Josh Woodward acknowledged the issue publicly and said Google was investigating and collecting affected examples. As of today, no fix has been announced; users are still posting fresh examples on the Google AI Developers Forum 🟡. For the full breakdown of what's a real policy vs. this bug, see our deep dive on Bug A.

Bug B — The quota counting bug (fixed 2026-05-28)

Unrelated to the policy block — this was a billing bug where failed generations (including ones killed by Bug A) were still being deducted from your quota. On 2026-05-28, Woodward announced:

Source: 9to5Google 🟡.

How to tell which one hit you

Known failure modes (be honest about these)

DeepMind's own model card explicitly lists these as "Known Limitations" 🟢 — so when you hit them, it's not a prompt-writing problem, it's a model boundary.

Text rendering

Any onscreen text — labels, signage, captions, brand logos — degrades. Avoid mentioning text overlays in your prompt. Verified by PixVerse hands-on.

Hand articulation

Hands holding objects, sign language, typing — fine articulation drifts. Frame to hide hands when possible, or accept some imperfection.

Multi-shot character consistency

Per Atlas Cloud's multi-turn review: Omni scores 3/5 on character consistency across 4+ shots. Use @character_name with a reference image for best results, and accept drift past shot 4.

Complex motion

Per digit.in's test: complex actions (dancing, gymnastics, instrument playing) show AI artifacts more than static shots. Simple actions (walking, standing, talking) work best.

Word count over 50

Per Seaart's analysis: prompts longer than ~50 words dilute focus and reduce output quality. Be specific but concise.

What NOT to do

Avatar feature hard rules

Source: Google Gemini Avatar help page.

Sources

Last updated 2026-05-29. We re-verify every claim and update this page whenever Google ships a change. Spot something wrong or outdated? Tell us — we read every email.