Luma Ray 3.2 Keyframe

The Luma Ray 3.2 Keyframe node is a building block: it takes one guide image and anchors it to a specific moment of a video you're about to generate, so that moment of the output looks like that image. Chain two or more of these together and you're telling Ray 3.2, "start here, look like this at the halfway mark, end looking like that." It's how you steer a video's look over time instead of trusting one prompt to carry the whole thing.

This node generates nothing by itself and calls no API. It just packages an image with a timeline position into a LUMA_RAY32_KEYFRAME bundle. The actual generation happens in the sibling Luma Ray 3.2 Keyframes to Video node, which takes your keyframe chain, your prompt, and a duration, and interpolates a video through all the anchored images. So the workflow is: several Keyframe nodes → one Keyframes to Video node.

The inputs that matter:

• image - the guide image to place at that moment of the output video. Connect a Load Image.
• position - a dynamic combo that decides how you place it:
  • Fraction of duration (0.0–1.0) - 0.0 is the start, 1.0 is the end. Best when you don't know the exact runtime and just want "roughly a third in."
  • Absolute time (seconds) - 0 to 10 seconds from the start. For when a moment must land at an exact time.
• keyframes - optional input of the same type, so you can chain keyframes into this one. Wire the previous Keyframe node's keyframes output in here and each node accumulates the chain.

Output is keyframes (LUMA_RAY32_KEYFRAME), which feeds the keyframes input of Keyframes to Video.

The rules that matter live downstream: the Keyframes to Video node requires at least 2 keyframes (it errors otherwise), supports up to 64, and every keyframe must resolve to a distinct frame - so two keyframes both at 0.5 are a hard error, and a seconds-position past the end of a 5s/10s video is rejected too. The chain order doesn't matter; positions are what place them, and the node sorts them for you. That's a nice touch, but it also means a confusingly-ordered chain will silently "work" - keep your positions sane and your video will too.

Partner-node house rules: Ray 3.2 is a paid API line billed to your Comfy account credits, and you must be signed in. If the family litters your search, --disable-api-nodes removes it.