Skip to content
Docs
Docs

Scripts and storyboards

Importing a production script, laying it out as a storyboard on a Canvas, and making consistent shots from its scenes with the Space's styles, characters and palettes.

Markdown

A script becomes part of what a Space knows: its scenes and shots are references you can name with @, lay out on a Canvas and make images for, consistently. See Intelligence for references and @, and A storyboard from a script for a walk-through.

From a script to a storyboard

  1. Upload a Word production script into the Space. It should have a table with columns such as Scene, Voice-over, Captions and Visual cues, and pictures if you have them.

    A script written in Markdown works too: a document (or an uploaded .md or .txt file) with the same kind of table. Use <br> for a new line inside a cell. Its page has Extract script. Pictures linked in Markdown aren’t imported: add them to the Space and link them to their scenes.

  2. Ask the Assistant: “Extract this script, create scene and shot references, and link the images.” It makes:

    • a script document, with the voice-over and captions word for word;
    • a shot list. A scene with several actions is split into several shots, marked as proposals for you to correct;
    • references for the script (@script-01), each scene (@scene-01…) and each shot (@shot-01…);
    • the script’s pictures, imported into a folder beside it and linked to their scenes and shots.

    It tells you anything it couldn’t place. The Word file itself is never changed.

  3. On a Canvas, ask: “Lay out @script-01 as a storyboard on a new Canvas page.” Each scene becomes a frame, in order, with its voice-over, captions, visual cues, shot labels and pictures. They’re ordinary Canvas items that you can move and edit; they stay linked to their scenes and shots. Ask “Where is @shot-05?” and the Assistant selects it.

Consistent shots

Ask “Generate a 1:1 image for @shot-01”. The Assistant reads the shot’s description and pictures, then applies:

  • the style: the one assigned to the shot or script, or the one you choose. If there are several and none is assigned, it asks which, and remembers your choice for the rest of the script;
  • characters the shot mentions;
  • the colour palette: its exact colours are given to the model, though a model may not match them perfectly;
  • the prompt template.

The image is made as any image is (priced as usual), lands in the shot’s place on the storyboard, and stays linked to the shot. Ask for the next shot and it uses the same choices without asking again. How each image was made (the shot, style, characters, palette, template and their versions, and the prompt) is recorded with it, and later edits to those never change that record.

How this was made appears in such an image’s Metadata on a Canvas, and in its details in the library. It lists what the image was made from, each with the revision it was read at, and marks anything edited since. Each name opens what it names. On a Canvas, Run again puts the same request back in the Composer (“Generate a 1:1 image for @shot-01 in @style-isometric…”). It’s read with the references as they are now, and nothing is made until you send it and confirm the price.

In the Space’s Intelligence tab, each shot says whether it has been generated, and how many images it has.