Sora 2 prompt guide: describe a shot you can evaluate
Turn an idea into a visible action, then decide how the camera should observe it. This Pix Verse guide shows you how to write a clear shot, spot conflicting instructions and revise one variable at a time.
Build a shot promptExplore visual possibilities
Style and composition inspiration. These images are separate from this guide's worked examples.
Worked example: a florist's quiet morning
First draft: “A cinematic flower shop, beautiful light, a florist making an arrangement.” The mood is present, but the main event is vague. There is no clear test for whether the action finished or the viewer saw it.
Review question: can you follow the flower from the hand into the vase? If the hand hides the placement, revise only the viewpoint: “View the vase from slightly above the table so its opening stays visible.” If the scene adds extra actions, keep the composition and shorten the event description. Save each revision so you can tell what changed.
Medium side view of a florist at a wooden worktable beside a shop window. A clear vase sits in the center. The florist lowers one yellow tulip into the vase, releases the stem, then moves their hand away. The camera stays still. Soft daylight enters from the left; shelves in the background remain secondary. End with the tulip resting in the vase.
Illustrative writing, not a generated result.
Give each sentence a job
Start with the part of the scene the viewer needs to understand. A description such as “beautiful cinematic moment” leaves the subject, action and composition undecided. Replace abstract approval words with things someone could point to in a frame.
Subject and setting
Name the focal subject and its surroundings. Add only the identifying details that matter to this shot.
Action and order
Describe one main action with a visible beginning and end. State which event happens first when order matters.
Frame and light
Choose a view, one camera behavior and a lighting direction. Keep these compatible with the action you want to see.
A prompt is a request, not a set of enforceable controls. Duration, aspect ratio, reference inputs and audio depend on the actual interface and model you use. Select supported settings there instead of assuming that writing them into prose will enable them.
Write, test and revise in four passes
Write the observable event
Use a concrete sentence: a florist places one yellow tulip into a clear vase. Keep extra people, props and simultaneous actions out of the first draft.
Choose the viewer's position
Specify a medium side view so the hand, flower and vase can share the frame. Choose a stationary camera first; add movement only if it serves the event.
Check the prompt for conflicts
Remove instructions that compete: a locked camera and an orbit, a close detail and a full-room view, or several events with no room to finish. For multiple shots, draft each shot separately.
Review one variable at a time
If you test the prompt in a supported tool, record the text and settings. Compare the action, framing and continuity with your brief, then change the instruction tied to the most important failure.
Plan for uncertainty
Detailed wording cannot guarantee exact physics, persistent identities or readable text. Adding more instructions may make a prompt harder to assess. If a sequence needs several events, prepare a shot list and check each event separately before assembling a larger story.
If your selected tool supports audio or dialogue, keep sound notes separate from visual action and verify them in the result. A written line alone does not establish that a model will speak it verbatim, synchronize lips or produce an approved voice.
Use the shot plan for different scenes
A product detail
Name the feature the viewer should notice and keep the action simple enough that the feature stays visible.
A human gesture
Describe the start and end of one gesture. Review hands and object contact before adding another action.
An establishing view
Choose the place and the element that orients the viewer. Leave closer details for a separate shot instead of demanding both views at once.
Sora 2 prompting questions
Is a longer prompt always better?
No. Begin with a subject, an event and a viewpoint. Add detail when it resolves a specific ambiguity rather than increasing length for its own sake.
Should I include exact camera equipment?
Only if it helps communicate the intended look. A clear framing or motion description is easier to evaluate than a list of equipment names with no visible purpose.
Does this page generate or export a Sora 2 video?
This is a writing guide. It does not submit prompts, set up a model or export video. Check the capabilities and settings of the tool you actually use before production.
Start with one readable shot
Write the event, choose the view and keep a record of each revision. Return to the four passes whenever an instruction stops being observable.