Skip to content

Understanding Storyboards

Before generating any video images or audio, ADD CREATE first creates a storyboard — a structured, slide-by-slide plan for the video. Think of it as the AI sketching out the script and visual ideas for each slide before any assets are produced.

Storyboards are authored in English even when the final video will be rendered in another language. This keeps review, editing, and approval on a single source version before narration is synthesised.

Each slide in the storyboard has two components:

  • A narration line — what will be spoken aloud for that slide.
  • A visual description — a description of the image to be generated for that slide, shaped by the visual style you chose.

The storyboard is generated automatically from your project’s documents and cannot be manually edited before the video is produced.

When you launch a Video job, the platform:

  1. Searches your project’s documents for the most relevant content.
  2. Uses that content to plan a structured video with a logical flow — one slide per key point or topic.
  3. For each slide, writes the narration and composes a visual description appropriate to the chosen style.
  4. Generates all slide images and narration audio simultaneously before assembling the final video.
FormatDescription
ExplainerA structured video covering the highlights of your documents in full
BriefA shorter, high-level summary video

The visual style you select shapes the look of every generated image in the video:

StyleDescription
ClassicClean, professional corporate look
DarkDark backgrounds with high contrast and a premium feel
WhiteboardHand-drawn illustration and sketch aesthetic
NeonVibrant neon colours and a tech-forward aesthetic
WatercolorSoft, painterly watercolor art style

When you finalize a storyboard into a video, the render panel now includes a Final Render Language selector.

  • The storyboard text and slide planning stay in English.
  • The final narration and caption output use the selected render language.
  • The selector exposes the full supported language list available for the render workflow.

Use these patterns to get more predictable results:

  • Keep inputs specific and scoped to one intent per generation request.
  • Save intermediate outputs often, especially before running major edits or regenerations.
  • Use review and assignment workflows early to reduce rework late in the lifecycle.

If results are not what you expected:

  • Verify source quality first (missing context, inconsistent structure, or conflicting inputs reduce output quality).
  • Re-check selected options and audience/profile settings before re-running.
  • If a job fails repeatedly, wait briefly and retry once; then escalate with the artifact or job context.

Different input context, settings, and model/runtime conditions can produce different outputs.

Regenerate when the core structure is wrong; manually edit when only wording, ordering, or style needs adjustment.

What is the best way to reduce iteration cycles?

Section titled “What is the best way to reduce iteration cycles?”

Start with clear scope, run smaller batches, and use review checkpoints after each major step.