Upscale after a 360p Omni draft

Draft at 360p on Google’s Omni 1.1 Flash, pick the keeper, then upscale that file to 1080p or 4K on Google — or throw the prompt at a Versely 4K row for the hero. Google’s 27 August 2026 Keyword post claims 360p drafts are up to 60% faster and one-third the cost of Omni 1.1 720p. That is Google’s claim, on Google’s surface. Versely does not publish a gemini-omni-1-1-flash slug. Do not look for 360p drafts on a Versely Omni card.

This is the after-draft upscale procedure. It is not a second essay on why 360p exists.

Draft on Google, score like a working print

Omni 1.1 Flash (gemini-omni-1.1-flash) is what Google shipped on 27 August 2026: text/image/video in, video out 3–10s, 360p / 720p / 1080p / 4K, 24 fps. Access: AI Studio, Gemini Enterprise Agent Platform, Flow Plus/Pro/Ultra, Gemini app for extend. 360p is the draft tier on that surface.

Versely Omni rows that actually exist:

• Gemini Omni Video — T2V/I2V/R2V, 9 credits, 4K listed, 4/6/8/10s. No 360p draft tier on the card.
• Gemini Omni Flash Edit — edit-video, 13 credits, audio false. Not a 360p draft button.

Procedure on Google:

1. Open the Google surface you already have (AI Studio or Flow). Do not invent a Versely Omni 1.1 row.
2. Set output to 360p. Do not set 4K “to be safe.” You are hunting the take.
3. Change one variable per draft: camera, blocking, line, still. Google’s own sketch is a “Draft Room”: three or four 360p variations side by side.
4. Generate 3–10 second clips (Omni 1.1’s output window).
5. Score at 360p for verbs, not for grain:
   • Did the subject do the verb?
   • Did the camera move you named happen?
   • Did the face hold, or melt at 0:04?
   • Did it add speech or music you did not want?
6. Bin the misses. Keep one (or two) candidates. You are not delivering 360p to a buyer.

What 360p will not tell you: whether the fabric holds at a 4K crop, whether a pack label is listing-legible, whether a 9:16 recrop after upscale still has a head. You will learn those on the upscale or on a native 4K hero.

The 60% / one-third figures are Google’s 360p vs 720p throughput claim, 27 August 2026. They are not Versely credits. Quote them as Google’s. Do not convert them into a SKU here.

Upscale the keeper on Google, or re-run a 4K row here

Two delivery doors. Pick one on purpose.

Door A — upscale the 360p file on Google. Omni 1.1 can upscale to 1080p or 4K (same Keyword post). This keeps the exact take you already liked: the same blocking, the same accident that worked.

Procedure:

1. Take only the keeper. Do not upscale the misses.
2. Run Google’s 1080p or 4K upscale on that clip.
3. QC at 100% on a phone and on a laptop:
   • Label lettering.
   • Skin and fabric.
   • Temporal mush (upscale that smears motion).
   • Aspect. If you drafted 16:9 by mistake, upscale will not invent 9:16 headroom.
4. If the upscale is soft on the SKU, stop. A 4K upsample of a 360p pack shot is still a 360p pack shot with extra pixels. You needed a still + I2V hero, not a bigger draft.
5. Export. Caption after the upscale. Burning type at 360p and then upscaling the letters is how you get crunchy captions.

Door B — re-generate the hero on a Versely 4K row. You liked the idea of the 360p draft (the blocking, the line), not the file. Prompt that idea into a card that already lists 4K.

Examples:

• Veo 3.1 — T2V, native audio, 4/6/8s, 4K, 40 credits.
• Gemini Omni Video — 9 credits, 4K listed, 4–10s, on this catalog.
• Other 4K video rows you actually have in the catalog — not an invented Omni 1.1 slug.

Procedure:

1. Write the prompt from the keeper, not from memory. Include the verb that worked at 360p.
2. Attach the same still if I2V was the job.
3. Set 4K and the ratio you will ship.
4. Generate. Do not expect pixel-identical motion. You bought a new take at delivery resolution.
5. If you needed Omni 1.1’s scene extend (10s increments to 40s cumulative), that is still Google. Versely’s Veo extend is 7s, 720p, 40 credits — a different card.

Upscale video to 4K is the Versely editing door when the file you have is the file you want bigger. Use it on a keeper from a 720p or 1080p row, or on a Google export you brought in. Do not use it as a substitute for “we never locked the take.”

Audio: Omni Flash Edit is audio false. A 360p Omni draft may have sound on Google’s 1.1 generate path; check the file. If you upscale picture-only, keep the audio sidecar aligned. If you re-run Veo as the hero, native audio is a new performance — recaption from that take.

Do not skip QC between draft and spend

The cheap loop dies when every 360p becomes a 4K invoice.

Rules:

1. One upscale or one 4K hero per idea you would actually ship. Four 360p misses stay 360p.
2. Fix composition at 360p. A head cut off at 360p is still cut off at 4K.
3. Fix the still at image prices if the SKU is wrong. Upscale will not reprint a label.
4. Crop to 9:16 before the hero if the destination is vertical. Upscaling a 16:9 draft and then cropping throws away the pixels you just bought.
5. Caption last, on the delivery file, with add captions.

If Door A’s 4K upscale looks like a soft 360p, you learned something: this shot needed native 4K, not an upsample. Use Door B. If Door B cannot match the accident you liked, you needed Door A’s file. Do not run both on every clip “to compare” unless the test is worth two bills.

Bring Google keepers into Versely when the rest of the pipeline lives here: captions, a second model, a 9:16 finish. Flow is not that studio.

If you need a studio seat to upscale a keeper or to run the 4K hero row, sign up. Bring the 360p file you already picked. Do not bring five unwatched drafts.

FAQ

Does Versely have an Omni 1.1 360p draft row?

No. Google’s model id is gemini-omni-1.1-flash (27 August 2026). Versely publishes Gemini Omni Video (9cr) and Gemini Omni Flash Edit (13cr, audio false). Draft 360p on Google.

Should I caption the 360p draft?

No. Score picture first. Upscale or re-generate the hero, then transcribe and burn. Upscaled burned type is crunchy type.

When do I upscale on Google versus re-run Veo 3.1?

Upscale on Google when the 360p file is the take. Re-run Veo 3.1 (or another 4K row) when the 360p idea is the take and you want native 4K, native audio, or a catalog row you will finish here.