Skip to content

Building a character cast

How to create persistent characters that stay consistent across every render.

Why characters are a first-class object in CreatorStudio

Section titled “Why characters are a first-class object in CreatorStudio”

A character you meet in scene 1 and recognize in scene 50 is the difference between a story and a slideshow. Most AI video tools can’t do this. CreatorStudio can, because characters live in Memory, not in a prompt.

  1. Describe — tell Ra who they are (“a 50-year-old bespectacled historian, warm voice, wool jacket”). Ra drafts the look; you approve.
  2. Reference — upload an image, a video clip, or a description of an existing person (real or fictional). Ra pattern-matches.
  3. Cast from Memory — reuse a character from a prior project. They carry their full profile.

After creation, a character has:

  • A locked visual profile (used across every render)
  • A voice profile (if they speak)
  • A set of approved expressions and poses
  • A set of rejected variants (shots you killed)
  • A usage log (every scene they’ve appeared in)
  • Name characters early. Naming locks them.
  • Use Character manager, not scene-level prompts. Prompts drift; Characters don’t.
  • Reuse characters across projects — this is how a creator universe gets built.
  • For multi-character stories, define relationships in the cast. Ra uses this for framing.