> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/visualize/video-from-animation.md).

# Video (from scene)

Use the keyframes you set in Compose to drive an AI video model's motion, or render the scene as video without AI via Direct Render.

You authored keyframes on the shot in Compose. Video (from scene) takes those keyframes as the motion source for the video. The model follows the camera move, the subject motion, and the pose changes you set, rather than inventing motion of its own. Or pick Direct Render and skip the AI entirely.

![The Generate menu with Video expanded; From scene animation is the entry for this mode](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-800a43492178ef9d256b870e1e0de21ec9f9c089%2Fvisualizer-modes-01.png?alt=media)

## What it does

Most video models start from a still image and a prompt and invent the motion. Video (from scene) is different: it takes the animated 3D scene as the input. The keyframes you set in Compose drive what the model renders. The output follows the camera path, the character pose changes, and the object motion you authored, within whatever the chosen model can interpret.

This is the mode to reach for when the motion matters more than the look. If you've spent time animating a precise camera move or character action, this is how you preserve it through video generation.

## How to use it

1. **Author the animation in Compose.** Set keyframes on the camera, subjects, and any animated objects in the shot. See [Animate an object](/overview/how-to/animate-an-object.md) for the full flow.
2. **Switch to Visualize.** The shot's animation is preserved across modes.
3. **Set the mode dropdown to Video (from scene).** The panel updates to show the model picker for this mode.
4. **Pick a model.** Three options, each does something different (see below).
5. **Write a prompt** (skip this for Direct Render; the scene drives everything).
6. **Click Generate.** The job runs server-side. The output lands as the shot's video.

![Direct Render selected as the model with the mode set to Video (from scene): the panel explains that it captures your scene animation directly, and the Generate button runs it](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-90a4da22958e3f9f9051bcf1ee2fb9feb6b51d59%2Fdirect-render-panel-01.png?alt=media)

## The three model options

![The model dropdown for Video (from scene), grouped by vendor: ByteDance, Kling, Alibaba, Fal with H3 Max, Luma, and Intangible with Direct Render ticked and described as rendering the 3D scene as video](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-81a17215e29806750fa559a7ac53f62b91c3eea0%2Fvideo-from-animation-models-01.png?alt=media)

* **Seedance 2.0** (ByteDance). Generative video that follows the scene's motion. Use it when you want a stylized AI output that respects your authored blocking.
* **Luma Ray 3.14** (Luma). Video-to-video model with first-and-last frame anchoring. Tightest motion fidelity of the AI options.
* **Direct Render** (Intangible). Non-AI. Renders the 3D scene as video, frame-for-frame, no diffusion model involved. See [Direct Render](/visualize/direct-render.md) for the full picture.

## Motion versus appearance

When you use Video (from scene) with an AI model, the *motion* is driven by your keyframes but the *appearance* still comes from the prompt and any reference images. A dolly through an empty 3D scene produces a dolly through whatever the prompt describes. A subject animating across frame stays animated, but its visual identity is decided by the prompt.

If you want the appearance locked to your scene too, that's [Direct Render](/visualize/direct-render.md).

## When to reach for each option

| If you want                                              | Use                                                                                              |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Stylized AI video that follows your authored motion      | Seedance 2.0                                                                                     |
| Tighter motion fidelity with start / end anchoring       | Luma Ray 3.14                                                                                    |
| Wireframe preview of the authored shot, no AI, no credit | [Direct Render](/visualize/direct-render.md)                                                     |
| A still-image generation with no motion                  | Switch the mode dropdown back to Image                                                           |
| Video from a single start image, no scene animation      | Switch to Video (from keyframes), see [Generate video](/visualize/generate-video.md)             |
| Video from two anchor images                             | Switch to Video (from keyframes), see [First and last frame](/visualize/first-and-last-frame.md) |

## Limits and known issues

* **The model interprets your motion; it does not replay it.** Seedance 2.0 and Luma Ray 3.14 honor authored motion, but they still resample through their own video generation. Sharp keyframe changes can soften; fast camera moves can drift. If a move has to land exactly, use Direct Render.
* **Direct Render output is wireframe / greybox**, not photoreal. It captures the 3D scene as it appears in the viewport. For a finished look, render through one of the AI models.
* **No audio.** The audio toggle that appears on other video modes is not present here. Add audio later in your editing tool, or use Video (from keyframes) with a model that generates audio.

## Related

* [Direct Render](/visualize/direct-render.md) – the non-AI option inside this mode.
* [Animate an object](/overview/how-to/animate-an-object.md) – how to author the motion that drives this.
* [Animation and shot time](/overview/concepts/animation-and-shot-time.md) – the concept.
* [Generate video](/visualize/generate-video.md) – the mode menu and the keyframe-driven video path.
* [Models](/visualize/ai-models.md) – the full model reference.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/visualize/video-from-animation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.