Skip to content

The storyboard

The storyboard is where a campaign's video gets written. It sits on the Storyboard & Ad copy step of the builder, after the idea and before the package: a short direction block that sets the look, then a filmstrip of scenes.

Each scene carries three lines you write:

  • Visual: what is on screen, the action and the look.
  • Voiceover: the line spoken over the scene, used when an audio field plays the generated narrator track.
  • On-screen text: a headline, caption, or CTA burned into the frame.

Any of them can hold {{variables}}, which is what makes one storyboard fill the whole matrix. The prompt the model finally receives is composed from the direction block and the scenes; see Generation and render for that, and Campaigns for the ad copy written beside the storyboard.

The clip plan

A storyboard is a list of scenes, but the video it produces is not always one file. The clip plan groups neighbouring scenes into clips, and each clip is generated as its own video.

One clip fills one video placement in the template. A placement is a layer that plays the generated footage: Klyo assumes video layers do and image layers (a logo, a product shot) do not, and the template's field settings can mark it the other way when the designer built the video slot as an image layer. A template with two video placements wants a plan with two clips; the first placement plays clip 1, the second plays clip 2. A campaign that never touches the plan has one clip covering every scene, which is exactly how storyboards behaved before clips existed.

The plan is drawn on the filmstrip as one bordered group per clip, its scenes inside it. Each group's header shows the clip's number, an optional name you can give it (click the clip chip to rename), and the length that clip generates at.

Splitting and merging

The boundary between two scenes carries one control:

  • Split into a new clip here, where the two scenes currently share a clip.
  • Merge these two clips into one, where a clip ends and the next begins.

Both are icon buttons sitting in the gap they act on, and both save immediately. Clips always cover every scene in order, so there is no way to leave a scene out or to put one scene in two clips. Adding a scene to a clip that is already full splits the run for you rather than refusing the edit.

If two people edit the same plan, the second save is refused instead of silently overwriting the first. Klyo reloads the current plan so you can redo the change against what is actually stored.

Clip lengths

A clip's header carries a compact control showing the length that clip generates at. Click it and a slider opens, stepping across exactly the lengths the campaign's video model produces, one stop per achievable length. Gemini Omni 1.1 Flash generates any whole number of seconds from 3 to 10 in one call, and reaches any whole second up to 40 with extends (below). Gemini Omni Flash, the older model of the same family, stops at 10. Veo generates 4, 6, or 8 second clips, and reaches 29 with extends. Veo's lengths are a scattered set and Gemini Omni 1.1 Flash's run contiguously, but both drag the same way, and neither has a stop on a length its model cannot make.

A line under the slider rewrites while you drag, naming what the length costs to generate: 2 extend steps · 10s + 10s + 10s for a chain, or One generation covers it. for a length one call reaches on its own. Releasing the thumb saves, the same as picking a length did before; closing the popover without moving it changes nothing.

Reference images narrow what the slider offers. Klyo conditions generation on the sample items' images by default, and Veo locks a clip to an 8 second base whenever reference images are attached, so the shorter Veo lengths are only available on a campaign that binds no references. The help card beside the length control says so where the lengths are set, rather than leaving a short range with no explanation.

The slider also names the length the template wants. The video placement this clip plays has a length the designer authored, and that length sits on the track as a marker tick, with a note under the slider saying how the length you are dragging relates to it:

  • Matches the template's 8s placement. Nothing is trimmed and nothing is missing.
  • The template's placement plays 8s; the extra 22s is trimmed at render. The seconds past the placement's length never appear, and you still generate and pay for them.
  • 4s short of the template's 8s placement; the render leaves a gap. The render does not stretch a clip, so the placement sits empty after the video ends.

The placement a clip is measured against is the one bound to it on the Package step, or, where nothing is bound yet, the one it takes by order: the first placement pairs with clip 1, the second with clip 2. That is the same pairing the Package step starts from, so sizing the clips here holds once you get there.

Longer clips: extend chains

A model that can extend reaches past one call's length by continuing a finished clip. Klyo caps the chain at three extend steps on every model.

Veo extends by 7 seconds at a time. With reference images attached (the default, see above) the base is locked to 8 seconds, so the achievable Veo lengths are 8, 15, 22, and 29 seconds; a campaign that binds no references also chains from the 4 and 6 second bases, up to the same 29 second ceiling.

Gemini Omni 1.1 Flash asks for each step's length instead of using a fixed one, so Klyo splits the target into the fewest even pieces that reach it: 11 seconds is 6 plus 5, and 29 seconds is 10 plus 10 plus 9. That makes every whole second from 3 to 40 available rather than a short list of jumps.

The slider's detail line names the chain as you drag, so what a length costs is visible before you let go: 1 extend step · 8s + 7s under a 15 second Veo clip.

Every step of a chain is a separate paid generation. A 22 second clip is three calls, not one, and takes roughly three times as long to come back. Cost follows the seconds either way: the Generate step's run summary names the model, the clip count, and the seconds one run produces, and the estimate before a matrix fan-out prices those seconds per combination.

Gemini Omni Flash has no extend. Its 10 seconds is its ceiling. Pick Gemini Omni 1.1 Flash for anything longer.

Pairing clips with video placements

The pairing itself is made on the Package step. A video placement bound to the storyboard shows a Fill this placement with picker listing every clip with its length, for example Clip 2 · Product close-up · 8s. Placements pair with clips in order until you change one, so a two-clip plan and a two-placement template need no work at all.

Two things are worth a look on that step:

  • If two placements point at the same clip, both play identical footage. Klyo says so under the picker; it is allowed, in case you want it.
  • If a clip is shorter than the length the placement plays, the gap renders black. The warning names both numbers.

When something needs attention

The clip plan is validated softly. Klyo warns and lets you carry on, because either side of a mismatch can be the one you meant to change:

  • Clip count does not match the template, shown on the bound template's card. Regroup the scenes here, or bind a template with a matching number of video placements.
  • This length is not one the chosen video model produces, which is what you see after switching models on the Activation plan step. Open the length control and set a length the new model reaches; nothing is substituted for you.
  • A clip does not match the length of the placement it plays, shown on the Clips header. A clip that runs longer than its placement is a soft note: the extra seconds are trimmed at render, and they are still generated and paid for. A clip that runs shorter is a warning, because the render does not stretch footage and the placement sits empty after the video ends. Two clips are named, then "And 2 more"; slack under a second is ignored, matching what the render itself tolerates. While the clip count does not match the template, this one stays quiet, since the pairing it would judge is the thing in question.
  • One generation of this model covers three scenes, on a clip holding more. Split it, or move a scene into the neighbouring clip.
  • The voiceover is longer than the plan, shown above the filmstrip when an audio field plays the generated narrator track. The narrator is cut off where the video ends, so lengthen a clip or shorten the scene lines.

One state is not a warning but a stop: if a placement is bound to a clip that has since left the plan, the cell will not render until you pick a clip again. Klyo never falls back to another clip, because silently rendering the wrong footage is worse than waiting. The Package step marks the placement and the render readiness readout repeats it.

Ask Kai

The assistant reads the clip plan. You can ask it how the scenes are grouped, and ask it to regroup them; it proposes the new plan and you approve it before anything is written. See Assistant.

A Digitl product. This guide covers what is built today, not the full roadmap.