Luma Scenes: approve keyframes, then render, on Sume

Luma Scenes turns a brief into a storyboard of editable keyframes, lets you approve each scene, and renders only after that. You can copy the order on Sume by hand: generate a still for each scene, approve it, and submit the approved still as a first_frame image-to-video job. The docs I read describe no storyboard editor, so the approval step is yours.

Luma's flow is from its launch post. Sume details are from Video generation and Generation admission, read 2026-10-01.

What does Luma say about paying?

The post names the problem: ten or more generations for one usable spot, and paying full price for a render before you know it is usable. Its answer is that nothing renders before approval, and fixing one scene costs one scene.

How do I send an approved frame?

frame_images specifies first or last frame images for image-to-video; each entry needs a frame_type of first_frame or last_frame. If you also send input_references, frame_images takes precedence and the request is treated as image-to-video.

When does the cost land?

At submit. Sume reserves the estimated amount when the request is accepted, captures it on completion, and releases or refunds it for failed jobs. Stills are cheap to redo before that point, which is why approving them first matters. See first-frame previews for avatar videos for a similar pattern.

How do I keep the look consistent?

Reuse the same style words in every still prompt, and send the previous approved still as a reference when generating the next one. Luma generates its scenes together in one context; Sume jobs are separate, so consistency comes from your prompts and references. More in storyboard to video.