Luma releases Ray3.2 with 16 keyframes, 20s V2V, and EXR HDR

• LumaLabsAI's launch post opened Ray3.2 with three concrete upgrades for creators: up to 16 keyframes in one clip, Modify Video V2 for footage transformations, and Reframe for aspect-ratio changes while preserving motion and facial performance.
• According to LumaLabsAI's API post, the same control surface now ships through Luma's API, including multi-keyframe control, HDR generation, and 16-bit EXR export.
• The product page says Ray3.2 outputs 1080p across modes, while LumaLabsAI's Modify Video V2 post caps video-to-video runs at 20 seconds.
• Luma's announcement and Luma's learning-center guide frame the big workflow shift the same way: Ray is moving from prompt-only clip generation toward shot direction, grading, and VFX handoff.
• Creator demos from DreamLabLA's trailer breakdown, DreamLabLA's short film post, and mrjonfinger's motion-transfer demo all lean on the same pitch, control is finally getting specific enough to storyboard beats instead of rolling dice.

You can browse the launch page, dig through Luma's feature and pricing page, and skim the output-controls guide. Ray3.2 is also already exposed outside Luma's own surface on fal and Replicate, which makes this feel less like a model refresh and more like a production rollout.

Luma's headline feature is Multi-Keyframe, which lets a single clip carry up to 16 keyframes. That matters because most AI video tools still treat shot progression as a single prompt plus vibes.

Between LumaLabsAI's product demo and the official announcement, the promise is very literal:

• up to 16 keyframes inside one clip
• control over what changes and what stays locked
• beat-by-beat direction for pacing and story turns
• the same sequence-level control exposed through the API

That lands closest to storyboarding, not prompting. mrjonfinger's demo thread pushed the point further, saying control now depends more on how well you drive motion and edit images than on writing a longer prompt.

Ray3.2's second big move is treating existing footage as source material, not just inspiration. LumaLabsAI's Modify Video V2 post says users can swap walls, worlds, and wardrobe while holding lighting and performance, up to 20 seconds at 1080p.

Luma's Ray3.2 page expands that into a fuller production list:

• character transformation while preserving performance
• environment change
• relighting
• product swap
• visual-effects style transformations

That is a pretty direct pitch at ad and branded-content teams. LumaLabsAI's API brand-system post frames the workflow as one brand system, multiple markets and formats, with Reframe handling the backdrop and V2V handling the SKU.

The sleeper feature here is not another motion claim. It is the finishing pipeline. LumaLabsAI's HDR and EXR post says Ray3.2 supports native HDR generation and 16-bit EXR export so outputs can composite into Resolve or Nuke.

On the product page, Luma gets more specific: EXR export is ACES2065-1 (AP0), and HDR output uses native 16-bit color. In Luma's controls guide, EXR is described as a ZIP variant for downstream finishing in Nuke, Resolve, Flame, or Baselight.

Two useful constraints show up once you leave the marketing thread. Replicate's Ray 3.2 readme says HDR is only available at 720p and 1080p, only on 5-second clips, and EXR requires HDR to be turned on.

Luma is pitching Ray3.2 as a model you can build with, not just use in a web app. LumaLabsAI's API post calls this the first time the full Ray control surface is available through the API.

The most concrete numbers live on Luma's pricing page for Ray3.2:

• 1080p text-to-video or image-to-video, 5 seconds: 400 credits
• 1080p text-to-video or image-to-video, 10 seconds: 1200 credits
• 1080p video-to-video, 5 seconds: 720 credits
• 1080p video-to-video, 10 seconds: 1440 credits
• Reframe at 1080p: 120 credits per second
• HDR output: 2x SDR credits
• HDR plus EXR: 3x SDR credits

Distribution is already broader than Luma's own site. fal's Ray 3.2 page presents it as available now, while Replicate's readme exposes a simpler public checklist of supported durations, resolutions, and HDR constraints.

The early creator material is all about control surfaces, not one-shot magic. DreamLabLA's trailer breakdown is a full promo built around cinematic motion and shot continuity, while DreamLabLA's comedy short uses multi-keyframe control, facial performance, HDR and EXR, reframe, and motion transfer in a short character piece.

Three patterns recur across the examples:

• trailer-style sequencing with locked framing and moving beats
• product and environment swaps that keep performance intact
• motion-transfer experiments where the source movement does most of the storytelling work

Luma's own controls guide sketches the workflow behind that material. It recommends exploration in Speed mode at 360p or 540p, polished review at 720p, then final delivery at 1080p, with HDR and EXR reserved for premium finishing. mrjonfinger's tutorial teaser suggests a longer creator tutorial pass was already in the works within a day of launch, which is usually a good sign that the tool has enough knobs to need teaching.