One line in · A shot-by-shot brief out · Render it here or take it with you
Describe the clip you want in one sentence and get back a full brief: the shot list, what the camera is doing in each beat, the lens and grade, and how the seconds are spent. Vague prompts are why generated video comes back looking like nothing in particular — this builds the specific version for you, and you can render it here without leaving the page.
Both clips below were generated on Kavel from prompts written in this structure — they are our runs, not stock footage. Every output is AI-generated, so the same brief will not return the same frames twice; read them as evidence that structure survives the trip, not as a template that reproduces exactly.
The brief named the camera package (65mm anamorphic), the aspect ratio, the grade — teal in the shadows, warm amber in the highlights — and then split fifteen seconds into a handful of shots with a stated move for each. What came back holds the grade across cuts and keeps the chef readable through the fastest beat. Naming the optics and the colour is what stops a model from averaging toward generic footage.
Open the video studioThe second brief pushed on timing rather than optics: 2.35:1, twenty-four frames a second, and a multi-scene action sequence with each scene given its own slice of the fifteen seconds. The clip keeps the frame rate feel and the widescreen framing, and the scene changes land where the brief put them. Where it strains is continuity between scenes — the further apart two beats look, the more the model treats them as separate ideas.
Try your own briefA Sora 2 prompt generator takes the sentence you would normally type — "a chef running through a kitchen" — and expands it into the kind of brief a director would hand a crew: how many shots, what each one frames, where the camera moves, which lens and colour treatment, and how the running time is divided between the beats. The generation model itself has not changed.
What changes is how much of the decision-making you have made before generation starts, and that is most of the difference between a clip you keep and a clip you regenerate five times. The habit transfers: a brief written this way reads the same to any modern video model, which is why the output here is text you can carry rather than a setting buried in an interface.
What it will not do is pin the frames — video models are sampled, so two runs of identical text differ in framing and timing. Structure narrows the range rather than fixing the result.
Creative engine
Describe the clip in a sentence and the brief comes back filled in — shots, camera moves, lens and grade. Render it here on Veo 3.1 or Seedance 2.0, or copy it out.
A brief written this way survives the trip between engines, because it names things every video model understands: how many shots, what each one frames, where the camera moves, and how the running time divides between the beats.
Because framing varies between runs, the winning habit is generating a few and choosing, rather than rewriting the prompt after every miss. Structure gets you a narrow range of good takes; it cannot get you the same take twice.
The generator makes these three calls for you from one sentence, and each one is yours to override. Settled either way, the brief stops being a wish list and starts reading like a director's instruction.
"A woman walks through a market" leaves the camera unassigned, so the model invents one, differently each run. Give it a job — locked off, tracking behind her shoulder, craning up as she passes — and the shot stops drifting between attempts.

A clip is short. Decide out loud how many beats fit and what each one is for: three seconds establishing, six on the action, three to land it. Models follow an explicit division of time far more reliably than they infer one from a description.
"Cinematic" means nothing in particular. A lens, an aspect ratio, a grade — 65mm anamorphic, 2.35:1, teal shadows and amber highlights — are instructions. Swap one of them and you can see exactly what moved, which is what makes the next revision fast.
Three people who stop regenerating and start revising once the prompt has a shape.

Ten runs of the same vague sentence produce ten unrelated clips, and none of them can be improved because there is nothing specific to change. A brief makes the next run a revision instead of another roll of the dice.

A campaign needs six clips that belong together. Fixing the lens, the ratio and the grade in writing is what makes them siblings — the subject changes between briefs, the treatment does not.
Judging two models on two different prompts tells you nothing. Hold the brief still and swap the engine and the comparison finally means something — run it here on Seedance 2.0, or take the same text elsewhere.
What this tool does, what it does not, and what to expect from the text it hands you.
No, and it does not claim to. OpenAI discontinued the Sora web and app experience on April 26, 2026, and removes the Sora API on September 24, 2026 — after that date no third party can run it at all. What this page produces is a written brief. Kavel renders it on the video engines wired into this site — Veo 3.1 and Seedance 2.0 — and the same text can be pasted into whichever generator you use elsewhere. If a page ever tells you it is running a model it is not, treat everything else on it as unverified too.
Yes, because the structure was never Sora-specific. A shot list, a camera move per beat, a lens and a grade are what any modern video model reads well — the brief this page builds transfers to Veo 3.1, Seedance 2.0, or anything else you feed it. What changed is only where you render it. If you are wondering what happens to clips you already made, we covered the dates, the export deadline and the watermark question when the API shutdown was announced in Sora alternatives.
No. Video models are sampled, so two runs of identical text differ in framing, timing and detail. Structure narrows the range — the shot count, the camera moves and the grade hold up across runs — but it does not pin the frames. Plan on picking from a few takes rather than expecting one exact result.
Long enough to answer the questions the model would otherwise answer for you: how many shots, what each frames, how the camera moves, how the seconds divide, what the look is. Past that, extra sentences mostly add contradictions, and a contradiction is the one thing a model resolves at random.
Yes, with one change of emphasis. When you start from a photo, the frame and the subject are already decided, so the brief should spend its words on motion and timing rather than on composition — what moves, in what order, over how many seconds.
Writing and copying a brief costs nothing. Rendering it spends credits, and the estimate for the exact model, resolution and duration you picked is shown in the generator before you start; a failed run is refunded automatically (unless it broke the content policy). Free credits come with the account, which is enough to see a brief become footage before you decide anything.
Credits are shared across everything Kavel runs. You see the cost before each run, and a failed job is never charged.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
Pay safely and securely with
Payments are processed by Stripe over an encrypted checkout. Your card details are handled by Stripe and are never stored by Kavel.
Charges appear as “KAVEL AI” on your card statement. You can cancel any time from Settings → Billing; cancellation takes effect at the end of the period you already paid for. Operator details, the full model list, and the refund window are on the about page.
Start from one line about the clip you want. The structure comes back filled in, and the studio is on the same page.