Sora status checked October 22, 2026

OpenAI’s discontinuation notice gives April 26, 2026 for the web and app closure and September 24, 2026 for the API shutdown. Both dates have passed. Sora is unavailable for new generation in QuestStudio. This correction preserves the original publication date and separates historical material from actions you can take now.

Sora has closed, but a saved shot brief can still be useful. Keep the subject, action, camera, lighting, and sound intent, then translate the brief for an available video model. This article preserves its original templates while correcting obsolete Sora instructions on October 22, 2026.

The examples below are planning templates for cinematic scenes, ads, dialogue, social clips, and image-to-video work. They are not executable Sora requests or proof that a different model supports the same controls.

What to preserve from a Sora 2 prompt

A reusable shot brief records:

  • subject
  • action
  • setting
  • shot type
  • camera movement
  • lighting
  • mood
  • audio or dialogue
  • any important constraints

OpenAI’s historical prompt guidance treated a prompt as production direction. Preserve that useful structure. Former Sora API documentation describes a retired service, so confirm reference and audio support in the replacement rather than copying an old request unchanged.

A weak prompt looks like this:

make a cool night city video

A stronger prompt looks like this:

A slow tracking shot through a rain-soaked neon alley in Tokyo at midnight, steam rising from vents, reflections rippling across wet pavement, cinematic realism, shallow depth of field, soft handheld motion, moody blue and magenta lighting, distant sirens, light traffic hum, and footsteps echoing in the background.

The second version makes the framing, atmosphere, action, and sound easier to check against an output. It remains a brief, not a guarantee of model behavior.

A reusable Sora 2 shot-brief formula

Start with this structure:

Subject + action + setting + camera + style + lighting + audio + constraints

You can use this template:

A [shot type] of [subject] [action] in [setting]. The camera [movement]. Style is [visual style] with [lighting details] and [color mood]. Audio includes [ambience, sound effects, or dialogue]. Keep motion [smooth, natural, dramatic, restrained]. The overall feeling should be [emotion or tone].

Use the formula to communicate a shot. Adapt the syntax and any separate controls to the model you actually select.

Saved Sora 2 prompt templates to adapt

1. Cinematic scene prompt

Use this for film-like shots with mood and realism.

Template:

A [shot type] of [subject] in [location], performing [action]. The camera [camera move]. Style is cinematic and realistic with [lighting], [atmosphere], and [color palette]. Audio includes [ambience] and [sound effects]. Keep movement natural and visually grounded.

Example:

A medium-wide shot of a lone astronaut walking across a frozen shoreline at dawn. The camera slowly pushes in as icy fog drifts across the frame. Style is cinematic realism with pale blue morning light, muted steel-gray tones, and soft atmospheric haze. Audio includes distant wind, ice cracking, and faint radio static. Keep movement natural and emotionally restrained.

2. Product ad prompt

Use this for polished commercial shots.

Template:

A [product] in [environment]. Start with [opening composition], then the camera [movement]. Show [key product details]. Style is premium commercial advertising with [lighting], [surface detail], and [background mood]. Audio includes [brand-like sound cues]. Keep the motion clean and precise.

Example:

A luxury perfume bottle on a black stone pedestal in a dark studio. Start with an extreme macro close-up on the glass edge, then the camera slowly circles to reveal the full bottle. Show glossy reflections, embossed gold lettering, and soft mist in the air. Style is premium commercial advertising with soft rim lighting, deep shadows, and warm highlights. Audio includes a delicate glass chime and a soft cinematic whoosh. Keep the motion elegant and controlled.

3. Dialogue prompt

Use this when speech matters.

Template:

A [shot type] of [character description] in [setting], speaking directly to [camera or another character]. The camera [movement or framing]. Style is [visual style]. Lighting is [lighting]. Audio includes clear spoken dialogue, natural room tone, and subtle environmental ambience. The character says: [short line of dialogue].

This template preserves dialogue intent from the former Sora workflow. Before generating with another model, verify that it supports the required speech, language, and sound controls. Keep a separate voiceover plan when it does not.

Example:

A medium close-up of a tired detective in a dim apartment kitchen, speaking directly to camera. The camera is locked off with a subtle documentary feel. Style is gritty cinematic realism. Lighting is low-key with a flickering fluorescent overhead and cool dawn light from the window. Audio includes soft room tone, distant traffic, and quiet refrigerator hum. The character says: I should have left this case alone.

4. Social media hook prompt

Use this for short, fast attention-grabbing clips.

Template:

An attention-grabbing [shot type] of [subject] doing [action] in [setting]. The first second should show [visual hook]. The camera [movement]. Style is bold, crisp, and optimized for short-form video. Lighting is [lighting]. Audio includes [sound cue]. Keep pacing fast and visually clear.

Example:

An attention-grabbing close-up of a bright red sneaker landing in a shallow puddle on a city street. The first second should show water splashing toward the lens in slow motion. The camera tracks low and fast across the ground. Style is bold and crisp for short-form ad content. Lighting is bright overcast daylight with sharp texture on the shoe. Audio includes a hard bass hit, splash sound, and fast urban ambience. Keep pacing energetic and clean.

5. Image-to-video prompt

Use this when starting from a reference image.

Template:

Animate this image with subtle realistic motion. [Primary movement] happens first, then [secondary movement]. The camera [camera move]. Preserve [important visual details]. Style remains [style]. Audio includes [ambience]. Keep the scene stable, natural, and consistent.

The image reference is a production input, not just text in the prompt. Upload an authorized image through a supported image-to-video control; do not assume a text-only model can see a filename or link in your notes.

Example:

Animate this image with subtle realistic motion. The woman’s hair moves gently in the wind first, then the fabric of her coat and the tree branches behind her. The camera performs a slow push-in toward her face. Preserve the soft golden-hour lighting, shallow depth of field, and natural skin texture. Style remains cinematic realism. Audio includes birds, soft wind, and distant city ambience. Keep the scene stable, natural, and consistent.

6. Character consistency prompt

Use this when you want a recurring subject across videos.

Template:

Use the same [character or object] as the reference. Keep the same [appearance details]. Place them in [new setting] performing [action]. The camera [movement]. Style is [style]. Lighting is [lighting]. Preserve facial structure, clothing signature, and overall silhouette. Audio includes [ambience or effects].

Keep an authorized reference pack and stable identity notes. The former Sora reference workflow cannot be reused as an active service; another model’s reference count, accepted subjects, and controls may differ. Review every output for identity drift.

Example:

Use the same orange tabby cat as the reference. Keep the same green eyes, white paws, and red collar. Place the cat on a rainy apartment windowsill at night, watching traffic outside. The camera slowly dollies in from a medium shot to a close-up. Style is cinematic realism with soft city reflections and moody blue lighting. Preserve the cat’s facial proportions and collar details. Audio includes rain on glass, distant traffic, and a soft room hum.

7. Storyboard or multi-shot prompt approach

Use this when your idea is too big for one generation.

Plan one beat per clip, then choose a duration the replacement actually supports. Old Sora duration values are not current options, and writing a number in the prompt does not override the interface or API limits.

Instead of this:

a full detective story where he enters the room, finds the clue, runs outside, and gets into a chase scene

Use this:

Shot 1: A close-up of a detective’s hand opening a dusty apartment door, warm light spilling into a dark hallway, subtle handheld movement, faint floor creaks and distant traffic.
Shot 2: A slow push-in on a photograph lying on a kitchen table, cigarette smoke drifting across the frame, cold morning light through dirty blinds, quiet refrigerator hum.
Shot 3: A fast handheld shot of the detective running down wet city steps into the street at dawn, flashing police lights reflected in puddles, heavy breathing and sirens in the background.

Separate beats make it easier to identify which action failed and revise that part of the sequence.

Prompt habits worth keeping

Think like a cinematographer

Describe what a cinematographer would need to stage the shot: subject, action, framing, light, and what must remain unchanged. The historical Sora guide used this framing; it is useful planning language, not a performance promise for a replacement.

Be specific about camera language

Words like close-up, overhead shot, dolly-in, locked-off shot, handheld, macro, and slow pan help a lot because they define the visual grammar of the scene.

Add sound intentionally

Write the intended ambience, effects, or spoken line separately from the visual action. Generate audio only through controls that the selected model supports, or produce a separate audio asset and assemble it in your editor.

Keep each clip focused

Keep each request centered on one visible action. Longer supported durations do not remove the need to review intermediate frames and continuity.

Use real visual details instead of vague hype words

Better:

  • wet asphalt reflections
  • soft rim lighting
  • shallow depth of field
  • flickering fluorescent light
  • low documentary handheld movement

Worse:

  • amazing
  • epic
  • cool
  • beautiful

Add constraints when needed

If you want realism, stable motion, or no extra objects, say so.

Example:

Keep movement realistic and restrained. Do not add extra people. Keep the camera smooth and avoid fast chaotic motion.

Replace obsolete Sora parameters with verified controls

There are no current Sora generation lengths to select after the service shutdown. Treat old model IDs, duration values, size settings, and reference fields as migration notes. Inspect the replacement’s input schema or visible controls before submitting a new job.

For each adapted template:

  • write for one strong moment, not a whole storyline
  • assume short-form pacing unless your workflow clearly supports extended generation
  • choose an available model and supported duration in its actual controls
  • record the model version, settings, source reference, and every attempt

Common Sora 2 prompt mistakes

  • Writing a concept instead of a shot — A concept is too broad. A shot is actionable.
  • Leaving out camera direction — Without visual grammar, the result often feels generic.
  • Cramming too much into one clip — Too many actions, scene changes, or emotional beats usually reduce quality.
  • Ignoring the audio handoff: name whether sound will be generated with the clip or assembled separately, then check synchronization.
  • Using long, messy dialogue — Short, clear lines are easier to render cleanly than dense speeches.

How QuestStudio helps

The practical migration task is to compare adapted briefs, retain the useful versions, and keep the resulting assets organized. Sora itself is unavailable.

Open Video Lab to inspect available models and supported inputs. Sora 2 and Sora 2 Pro are retired. Reference uploads, native audio, video-to-video, and durations vary by the model and mode; use only controls actually exposed. Prompt Lab can hold reusable shot templates for subsequent work.

That makes it useful for:

  • testing a saved brief with available replacement models
  • keeping cinematic, product, and social prompt templates organized
  • building multi-scene video ideas in storyboard mode
  • moving from prompt experiments into a broader AI video generator, image-to-video AI, or prompt library workflow

Frequently asked questions

What is the best Sora 2 prompt format?

Use subject, action, setting, camera, lighting, sound intent, and constraints as a starting brief. The service is retired, so adapt those notes to an available model and review the resulting shot instead of treating the template as a working Sora command.

Can I still generate Sora audio or dialogue?

No new Sora generation is available after the shutdown. Saved audio notes can guide a replacement with supported audio controls or a separate voiceover workflow.

How long should Sora 2 prompts be?

Use enough detail to make the shot and its pass criteria unambiguous. Remove contradictory directions and unrelated actions. Prompt length alone does not prove that a replacement will follow the brief.

How do I reuse an old Sora image reference?

Use a source image you still hold and are authorized to use. Upload it through the replacement’s supported reference control, verify crop and resolution requirements, and check whether the result preserves the required identity or product details.

What are the current Sora 2 clip lengths?

There are no current Sora generation options after closure. Choose duration in the replacement’s supported controls; a duration written into the prompt is only a target unless that model explicitly supports it.

How should I diagnose an adapted prompt that looks generic?

Compare the output with a specific shot brief. Identify one visible mismatch, such as framing, lighting, action, or identity, and revise that variable before spending on more attempts. The problem may be the model or input constraints rather than wording alone.

Conclusion

Retain useful production direction from your old Sora prompts. Replace retired service instructions with a verified model, supported inputs, and explicit approval checks. Keep the original assets so you can compare the new result with the intended shot.

Use the available-model selector and your saved prompt library to organize the migration. A brief that copied successfully has not yet passed a video or audio quality check.

Related guides