Luma Ray 3.2 Video Edit

The Luma Ray 3.2 Video Edit node is the "change everything, move nothing" tool. You feed it an existing video and a new prompt, and Ray 3.2 re-renders that footage - restyle it, relight it, swap elements in or out - while keeping the original motion and timing. Think of it as a video-native img2img: the choreography stays, the look changes. It's the node you reach for when a shot is blocked well but the art direction is wrong.

Mechanically it's the Ray 3.2 API flow: your video is uploaded through your Comfy account, a video_edit generation runs on Luma's servers, and the result comes back as a VIDEO plus a generation_id you can feed into extend later. The edited output keeps the source's length, and it's billed per generation to Comfy account credits.

The inputs that matter:

• video - the source footage. Up to 18 seconds. That's a hard cap enforced by the node, so plan your clips accordingly.
• prompt - describes the desired edit, up to 6,000 characters. "Golden-hour lighting, replace the car with a bicycle" type instructions.
• strength - the interesting control. A dynamic combo with a ladder from adhere_1 to adhere_3 (preserve the source most), through flex_1–flex_3 (balanced), to reimagine_1–reimagine_3 (change the most), plus auto (default), which lets Ray 3.2 pick. The higher the number in each band, the stronger that direction.
• resolution - 360p through 1080p, 720p default.
• seed - the Luma stub: controls whether the node re-runs; results are nondeterministic regardless.

Outputs are VIDEO and generation_id.

Where people get tripped up: the strength semantics are easy to misread. reimagine isn't "better," it's "further from the source" - if you want your subject to stay recognizable, start with adhere and only loosen up when the look isn't changing enough. And keep the 18-second source limit in mind before you wire in a long clip; the node rejects oversize footage rather than trimming it. Also note the edit preserves the source's length, so a 5-second source gives a 5-second result - the duration field is derived from the input, not something you pick.

Usual partner-node rules: sign into your Comfy account or it won't run, Ray 3.2 is a paid line, and --disable-api-nodes hides the whole family if it clogs your search.