> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ozu.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Props

> Single-image assets for the objects your story depends on — swords, mugs, cars, letters.

A **Prop** is an asset for a specific object in your story. Unlike Actors, Props have no wardrobe variants — each Prop is a single canonical image. If an object matters enough to appear in your script by name, give it a Prop Node so it looks the same everywhere it shows up.

Props live on the Flow canvas alongside [Actors](/user/assets/actors-and-wardrobe/) and [Sets](/user/assets/sets/). They pass through the same approval workflow and feed the same storyboard pipeline downstream.

## Generate a Prop

1. **Open the Prop Node.** Ozu creates a Prop Node for every named object surfaced during Script Node analysis. You can also add one manually from the canvas.

2. **Describe the object.** Size, material, era, and style matter most. "A 19th-century cavalry sabre, worn leather-wrapped grip, slight rust on the blade" generates a very different image than "a sword."

3. **Pick a style and aspect ratio.** Style inherits from the project by default. Most Props look best on a neutral background so they read clearly when placed into a scene.

4. **Generate.** The hero image renders in a few seconds.

5. **Approve.** Mark the Prop approved so it can pass the [Director Review Board](/user/assets/director-review-board/) and be used by the Storyboard Node.

<Tip>
  **One image, many scenes**

  A Prop's single hero image is used as a visual reference across every storyboard frame that features it. You don't need variants — the Storyboard Node re-interprets the Prop in context (different angles, lighting, positions) using the hero as ground truth.
</Tip>

## Approve, reject, reshot

Props move through the same three states as every other asset:

* **Pending** — awaiting review.
* **Approved** — locked in, ready to propagate downstream.
* **Rejected** — blocked from use until regenerated.

To **reshot**, adjust the description and generate again from the Prop Node. A reshot rebuilds every storyboard frame that used this Prop on the next storyboard run. Use reshot when the object design is wrong; use a single-frame regenerate when a specific frame misplaces or misrenders an otherwise correct Prop.

## Tips for sharp Props

<Columns cols={2}>
  <Card title="Be specific about size">
    "A pocket-sized silver locket" and "a dinner-plate-sized medallion" are very different images. Scale is hard to infer from a description alone.
  </Card>

  <Card title="Name the material">
    Brass, oak, worn leather, brushed steel, pale ceramic. Material choices drive texture and lighting response.
  </Card>

  <Card title="Anchor it to an era">
    "Early 1970s rotary phone, avocado green." "Victorian brass pocket watch." Period language narrows the design space fast.
  </Card>

  <Card title="Describe the condition">
    A brand-new object and a beaten-up one tell different stories. "Chipped," "pristine," "sun-faded," "recently polished" are all useful words.
  </Card>
</Columns>

## Related

<Columns cols={2}>
  <Card title="Actors and Wardrobe" href="/user/assets/actors-and-wardrobe">
    Hero looks, wardrobe variants, and keeping a character consistent across scenes.
  </Card>

  <Card title="Sets" href="/user/assets/sets">
    Environments and locations — interiors, exteriors, and panoramas.
  </Card>

  <Card title="Director Review Board" href="/user/assets/director-review-board">
    The approval gate every asset passes through before the storyboard can run.
  </Card>

  <Card title="Generating Frames" href="/user/storyboard/generating-frames">
    How approved Props feed into the Storyboard Node's frame generation.
  </Card>
</Columns>

## FAQ

**Why don't Props have wardrobe variants?**
Objects don't change identity the way characters do. If you need meaningfully different versions of the same object — a pristine sword and the same sword shattered in act three — create two separate Props and reference each where appropriate.

**Do I need a Prop Node for every object in my script?**
No. Only for objects whose visual consistency matters across frames. A generic coffee cup that appears once in a wide shot doesn't need its own node. A signature weapon or a plot-critical letter does.

**Can I upload an existing reference image for a Prop?**
Yes. Drag an image onto the Prop Node and Ozu uses it as the hero reference instead of generating from scratch. Useful when you have product photography, concept art, or a real-world object you want to match.

**What happens if I reshot a Prop after building the storyboard?**
Every frame that used that Prop rebuilds on the next storyboard run. This is the whole point of the reshot workflow — fix the object once, and every appearance updates automatically.

**What if my Prop looks different in every frame?**
The Prop was probably not approved, or the storyboard ran before the new hero image was set. Confirm the Prop is approved, then regenerate the affected frames.

**Are Props reusable across projects?**
Assets live inside the project they were created in. Cross-project reuse is on the roadmap.