Sora 2 Pro Storyboard is OpenAI's multi-shot storyboard model on Versely. This page is its structured prompting reference: the 4 parameters its schema actually exposes, the storyboard technique that applies to it, copy-ready templates.
Everything here is grounded in the same sources Versely's agent reads — the model's input schema, the sora family rule its prompt enhancer applies. Where a line is general craft advice rather than a documented fact about Sora 2 Pro Storyboard, the page says so.
What Sora 2 Pro Storyboard wants
The exact input surface, from the same schema the Versely agent fetches with get_model_input_schema before every generation.
| Parameter | What it does | Values |
|---|---|---|
shotsreq | 1-10 shot objects describing a multi-shot storyboard | array (min 1, max 10) |
n_frames | Total seconds budget — adds `25` option not on other Sora 2 variants | 10 · 15 · 25default: 15 |
image_urls | Optional single reference image | array (min 1, max 1) |
aspect_ratio | Aspect orientation | portrait · landscapedefault: landscape |
- — No `remove_watermark` field on Storyboard variant
- — `Scene` field name uses CAPITAL S — exact case required
The rule Versely's enhancer applies
Versely's prompt enhancer carries a per-family rule for sora models, applied automatically whenever it rewrites a prompt for Sora 2 Pro Storyboard. Verbatim:
“OpenAI Sora responds well to cinematic descriptions with clear scene narratives, camera movements, and temporal progression.”
Technique that applies here
Multi-shot storyboard: per-shot scene descriptions (Sora 2 Pro Storyboard shots schema)
- n_frames: "25" is a Storyboard-only option — the schema note flags it as adding a '25 option not on other Sora 2 variants.' If you need a 25-second multi-shot Sora 2 Pro sequence, Storyboard is the mode that offers it.
- There's no remove_watermark field on this variant, per the schema's own constraint notes — unlike some other Sora 2 endpoints, you can't toggle it off here.
- The product's MODEL_TIPS entry for the sora family — 'responds well to cinematic descriptions with clear scene narratives, camera movements, and temporal progression' — is what the prompt enhancer applies to any Sora model name. On Storyboard, apply that per shot: write each Scene as its own camera-plus-action-plus-setting beat rather than a bare label like 'shot 2.'
- General technique: Sora 2 Pro Storyboard has no continuity mechanism between shots besides the text you write and the single optional reference image, so repeat key visual anchors — character description, setting details — across every Scene if you need the shots to read as one sequence rather than unrelated clips.
Copy-ready templates
Replace the bracketed slots; each template says when it's the right shape.
Shot 1 — Scene: "[WIDE ESTABLISHING SHOT: SETTING, TIME OF DAY, SUBJECT ENTERING FRAME]", duration: [X] · Shot 2 — Scene: "[CLOSER SHOT: SUBJECT ACTION OR REACTION, CAMERA MOVE]", duration: [Y] (X + Y ≤ n_frames)
Use when: A simple two-beat setup-and-payoff storyboard inside the default 15-second n_frames budget.
n_frames: "25" · Shot 1 — Scene: "[BEAT 1]", duration: [s] · Shot 2 — Scene: "[BEAT 2]", duration: [s] · Shot N — Scene: "[BEAT N]", duration: [s] (durations sum to 25)
Use when: Building the longest available Storyboard sequence — 25s is the extra option this variant adds over other Sora 2 modes.
How the Versely agent does this automatically
You can use this page by hand, or let the agent apply the same knowledge. Four real mechanisms — no more, no less:
get_model_input_schema— before generating, the agent looks up Sora 2 Pro Storyboard's exact input fields, required fields, allowed values, defaults, and min/max bounds. The parameter table above is that same surface.- The prompt enhancer's family rules — 12 per-family rewrite rules, including the sora rule quoted on this page, shape how a rough prompt gets rewritten.
- The per-provider speech guide — for TTS scripts, the agent follows a provider-specific tag scheme — not relevant to this model, but it's why voiceover scripts come out marked up correctly.
expand_movie_scene— in movie flows, brief scene ideas are rewritten into detailed cinematic descriptions before generation.
Mistakes that waste generations
- Sending 'scene' in lowercase instead of 'Scene' — the schema's own constraint note calls out that the capital-S field name must be sent verbatim.
- Letting shot durations add up past n_frames — four 6-second shots (24s total) will not fit the default n_frames of 15; the sum of every shot's duration has to stay within whichever seconds budget you selected.
- Expecting a remove_watermark toggle like other Sora 2 endpoints — the schema's constraint notes explicitly say that field isn't present on the Storyboard variant.
The long-form guide
This page is the structured reference. For the essay treatment — worked examples, failure modes, and narrative — read Sora 2 Pro Storyboard Mode: The Storyteller's Complete Guide for 2026.
Frequently asked questions
Does Sora 2 Pro Storyboard support negative prompts?+
No — Sora 2 Pro Storyboard's published schema has no negative_prompt parameter. Exclusions have to be phrased positively inside the main prompt, or dropped.
Which aspect ratios does Sora 2 Pro Storyboard support?+
The aspect_ratio parameter is an enum: portrait, landscape. Set the parameter — describing the frame shape in prose does nothing on its own.
How does the Versely agent know Sora 2 Pro Storyboard's parameters?+
Before generating, the agent calls its get_model_input_schema tool, which looks up the exact input fields, required fields, allowed values, defaults, and min/max bounds for the model; separately, the prompt enhancer applies the sora family rule quoted on this page to the prompt text itself. Nothing on this page is guessed — it is the same schema surface those tools read.
Related prompting guides
Generate with Sora 2 Pro Storyboard
Sora 2 Pro Storyboard is live in Versely — paste a template above, or just describe what you want and let the agent map it onto the schema for you.