‘This Project Already Has a Character, Scene or Item With That Name’: Why Names Are Unique and How Renaming Works

Quick answer: Storyboards refer to cast, scenes and props by name: the tags you insert from the @ menu, the props line, the in-frame list. If two cards shared a name, a shot could not say which one it meant, so a project refuses a second card with a name already in use, and a card refuses a second state with the same name. When a script itself has two characters with one name, the parse gives the second a suffix like ‘(2)’; rename either to something clearer. Renaming a card rewrites every reference to it in this project’s storyboards, so a rename is safe; it does not touch other projects, and it does not change what the clips already made look like.
Still from “The Glass Floor”, an AI short drama generated end-to-end by SceneMixer (5 characters, 1 episode)
Sample: “The Glass Floor” — Realistic HD, 1 episode, produced end-to-end by SceneMixer from the script · watch the episodes

In Step 2, try to add a character with the name of an existing one: the message appears before anything is created.

Why names are unique inside a project

Every reference in a storyboard — a character tag in a shot, a location in the header, an item on the props line — is looked up by name to find the card whose sheet becomes a reference image for the clip. A name that matched two cards would attach two sheets, or the wrong one. Uniqueness is per project: two projects can each have a ‘Mei’. The @ Menu in the Storyboard.

The episode asset library showing generated character sheets, location images and prop images
A name in the storyboard points at one card; two cards with one name would leave the shot pointing at both.

Where the message appears

Adding a character, scene or prop in Step 2 with a name already on another card; renaming a card to a name in use; adding a state to a card that already has a state of that name. (Copying a picture from the asset library is different: it goes onto a card you choose and replaces its image, so there is no name to clash.) In each case nothing is created and nothing is charged; choose another name.

Duplicates in the script itself

Two characters called ‘Guard’, or a scene and a prop both called ‘The Letter’: the parse keeps both and gives the later one a suffix, so no card is lost. Rename them to what the story calls them (‘Guard at the gate’, ‘Guard on the wall’) before generating sheets; the sheets and the storyboards then read cleanly. Re-parsing matches cards by name, so keep the names you settle on.

What a rename changes

The card’s name and every reference to it in this project’s storyboards, including voice tags; done together so nothing is left pointing at the old name. Not changed: clips already generated (they are pictures), other projects, library copies. Projects created before names were made unique may contain old duplicates; renaming there changes only the card, and the storyboard should be checked by hand.

Choosing names that work

Short, distinct, as the story says them. Avoid names that are also common words (‘Door’, ‘Night’) for props and scenes; they read ambiguously in shot text. Nicknames can be added in the description; the name is the key.

You doResult
Add a card with a name in useRefused; choose another name
Rename a cardCard and all references in this project updated
Script has two 'Guard' charactersSecond becomes 'Guard (2)'; rename both
Add a state with a name in use on that cardRefused

FAQ

Can two projects share a name?

Yes. Uniqueness is within one project.

Does renaming break my storyboards?

No. References are rewritten with the card.

Do clips change after a rename?

No. They are already generated; only text changes.

Why did the parse create 'Mei (2)'?

The script has two characters the parse read as 'Mei'; rename one.

Can a scene and a prop share a name?

No; names are unique across cast, scenes and props in a project.

One name, one card

Rename freely; the storyboards follow.

Open Step 2

Updated September 27, 2026

Pricing·Novel to Video·Guides·Samples·Support·Privacy·Terms·Legal·Contact·© 2026 SceneMixer