> 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/direct-render.md).

# Direct Render

Render a single shot's 3D scene as video, no AI model, for a small flat fee. The wireframe / greybox view captured as MP4, exactly as authored.

Render the shot's 3D scene as video, no AI in between. The camera move, the animated subjects, the lighting model: captured frame-for-frame as an MP4. Useful when you need to see the blocking move, hand a director a structural cut, or sanity-check a long animated shot before spending credits on AI generation.

![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)

## What it does

Direct Render captures the shot's 3D scene as a video. Same camera move, same animation, same viewport lighting, exported as an MP4. Deterministic: run it twice, get the same file.

Distinct from the AI video paths (Seedance 2.0, Luma Ray 3.14, Veo, Kling, Runway) which interpret your scene through a diffusion model and produce a stylized result. Direct Render does no interpretation. What's in the viewport is what ships.

Direct Render is not a separate pipeline. It is a sentinel model, `Shot Animation Capture` in the code, picked inside the scene mode, so the same **Generate** button submits it.

The capture above is from an earlier build and does not match the labels on this page: it shows the mode as "Video (From Animation)" and the button as "Capture Animation". If that is what you see in front of you, you are on an older release.

## How to use it

1. **Switch to Visualize mode** on a shot whose animation is set up in Compose.
2. **Set the mode dropdown to Video (from scene).**
3. **Pick Direct Render from the model dropdown.**
4. **Click Generate.** The job runs server-side. No prompt needed.
5. The output lands as the shot's video. Download or use it as the start frame for a later AI pass.

## When to reach for it

* **Blocking review.** Walk a director or producer through the structural cut before committing renders.
* **Pre-render preview.** Confirm the sequence reads as authored before spending more on a generated render.
* **Reference handoff.** Hand a downstream artist a video of the wireframe they can match against.
* **Tight iteration.** No generation model runs, so each pass costs the same small flat fee whatever the shot's length.

When not to reach for it:

* **Final delivery.** The wireframe isn't a finished shot. For finished output, render through one of the AI video models (Veo, Kling, Seedance, Luma, Runway).
* **Stylized or photoreal look.** Direct Render is structural, not visual. For style, use an AI model.

## Direct Render vs Scene to video

Two ways to get a wireframe video out of Intangible, at different scopes:

| Path                                                                       | Scope           | Where it lives                      |
| -------------------------------------------------------------------------- | --------------- | ----------------------------------- |
| **Direct Render** (this page)                                              | One shot        | Visualize mode, model dropdown      |
| [**Scene to video**](https://help.intangible.ai/publish/scene-to-video.md) | One whole scene | Compose mode, Scene Timeline action |

Use Direct Render when you're working on a specific shot in Visualize and want a quick non-AI preview of just that shot. Use Scene to video when you want the whole scene's animatic across all its shots, in their authored order, as a single file.

## Limits and known issues

* **Wireframe / greybox output only.** No materials, no shading, no textures. That's the point: it's structural.
* **No audio.** Capture the audio separately and add it in your editing tool.
* **Per-shot only.** For multi-shot exports, see [Scene to video](https://help.intangible.ai/publish/scene-to-video.md) (full scene) or the export menus at scene / sequence level (see [Export video](https://help.intangible.ai/publish/export-video.md)).

## Related

* [Video (from scene)](https://help.intangible.ai/visualize/video-from-animation.md) – the parent mode that contains Direct Render.
* [Scene to video](https://help.intangible.ai/publish/scene-to-video.md) – the Compose-side export of the full scene animatic.
* [Animate an object](https://help.intangible.ai/learn-more/how-to/animate-an-object.md) – authoring the motion that Direct Render captures.
* [Models](https://help.intangible.ai/visualize/ai-models.md) – the AI video models you'd use for a finished render instead.


---

# 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 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/direct-render.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 `automate deployments from our CI pipeline` 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.
