How do you use a Blender blocking render as a camera reference for AI video?

Use a rough Blender scene to plan framing and camera travel, render that plan as visual reference, and give it to the invideo agent with the subject and look you want. Review the generated shot against the reference before accepting it. A Blender render communicates your intention; it does not guarantee an exact camera solve or pixel-identical composition in the output.

When is this useful?

Use this approach when a shot depends on where the camera starts, how it travels past the subject, or what it reveals. Simple stand-in geometry can make those relationships easier to communicate than a text-only brief. For a broad move such as a push-in or pull-back, the camera-move preset guide is a simpler starting point.

What the demonstration shows

Invideo’s Impossible Shots example combines a rough Blender reference with filmed material and generated imagery. At 00:15–00:19, the reel shows a grey 3D camera pass around a seated figure. At 00:26, it pairs the rough reference with three filmed frames. At 00:29–00:31, it compares the rough pass with the finished shot, including a close view of the eye.

Rough reference and finished shot at 00:29 in the source reel. This illustrates the creator’s result, not a measured fidelity test.

The caption also mentions a scissor-kick composite, but this short reel does not provide its complete recipe. The steps below focus on preparing and reviewing the camera-reference shot.

Prepare and use the reference

1. Block the shot in Blender

Place enough geometry to judge the subject’s position, the surrounding space and the camera’s view. Preview the intended movement from the camera. Add detail only when it helps communicate a relationship the shot depends on, such as an object passing close to the lens.

2. Render the information you need to convey

A still can show a composition; a rendered camera pass can also show timing and travel. Choose output dimensions and framing that reflect the intended shot. Blender’s render-output documentation explains output size, frame rate and image-versus-animation output. The reel does not establish a required Blender engine, focal length, frame rate, codec or resolution.

A grey render is not automatically a technical depth pass. Describe it as a camera or composition reference unless you have actually exported a depth map and confirmed that the selected generation route accepts it.

3. Supply the render and explain each reference

Attach the rendered reference in invideo and identify its role. Add filmed frames or approved visual references when they are needed to communicate the subject, wardrobe or environment. The AI filmmaking workflow provides the broader context for working with these materials.

Try this adapted brief:

Use the rough Blender render as the camera and composition reference. Use the filmed frames for the seated character and room. Follow the intended progression from the wider view toward the face and eye. Keep the character’s appearance consistent and show me the result for review.

This is an editorial starting prompt, not the creator’s exact command. The readable generation labels at 00:27 identify Seedance 2.0 in this example; they do not establish a required model or an automatic routing rule for every Blender reference. Check that the selected route supports your reference type. If you first develop a styled still, approve its composition before animating it; a separate image-model stage is not fully demonstrated here.

4. Compare the shot with the reference

Check the start, middle and end side by side. Does the camera travel in the intended direction? Does the subject remain in the right part of the frame? Do foreground objects pass the camera in the right order? Look for changes in facial structure, room layout and scale, particularly during close passes.

The comparison at 00:31 shows the intended close approach. Inspecting a still cannot verify the whole path or its timing.

If the path is wrong, clarify that the render describes camera travel rather than subject movement. If the composition is wrong, revise the blockout or reference package before asking for another take. Keep the accepted version with its references so later shots can be compared against it.

Use the accepted footage in an edit

After shot approval, arrange and trim the clip in invideo Editor, checking continuity with the shots on either side. This is an editorial handoff recommendation; the supplied Blender reel does not demonstrate timeline assembly. Generated motion remains part of the video, rather than editable Blender camera keyframes.

For the surrounding production process, see AI previz workflows and AI VFX.

Supporting questions

Do I need a detailed Blender scene?

Use enough detail to communicate the shot’s framing and spatial relationships. A rough scene is sufficient for the demonstrated reference approach; the reel does not prove that simpler geometry always generates better results.

Is a grey Blender render a depth map?

Not necessarily. A normal grey render shows surfaces and shading. A depth map represents distance. Do not treat the two as interchangeable or assume a depth-input requirement without checking the selected model workflow.

Which AI model should I use?

The reel shows Seedance 2.0 generation labels, but it does not establish one required model. Choose a route that supports your supplied reference and check its current input requirements. No universal image-model-to-video-model chain was verified.

Will the generated shot match my Blender camera exactly?

Exact matching has not been established. Compare the output’s framing, direction, spatial relationships and timing with the Blender reference and revise or reject takes that miss the intended shot.

Can I extend a long move by joining generated clips?

Joining clips is possible in an edit, but a seamless continuous camera move is not assured. Inspect the join for changes in subject position, lighting, perspective and speed before treating it as one shot.