Luma's 2026 timeline: Ray3.14, Ray3.2, Scenes and Variants

Luma released four notable things in 2026: Ray3.14 in January, Ray3.2 in June, Scenes in August, and Variants on Oct 1. The Luma news page describes each in a line, and the dates show a release every two to five months. That pace is why you should pin model ids in code and log which one produced each clip.

What shipped, in order

The table lists what the news page states for each release, nothing more.

Which ones change your workflow

Three of the four are model or workflow releases, and one, Variants, is aimed at static ads. Scenes is a process change: it adds an approval step before the expensive render. That pattern is worth copying whichever model you use.

Pin the id

When a vendor ships this often, the same prompt can produce a different look in the next version. Pin the model id in your request, store it with the job id, and upgrade on purpose. On Sume, the video docs say a pinned catalog id runs that model, while sume/auto echoes sume/auto and never discloses which family served the request, so do not use Auto where you need to reproduce a look.

{
  "model": "seedance-2.5",
  "prompt": "Product on a desk, slow push-in",
  "duration": 6,
  "resolution": "720p"
}

A change log for your own prompts

Keep a small change log of the prompts that matter and the model id that produced the approved clip. When a vendor ships a new version, rerun the log's prompts and compare. This is how you find out whether an upgrade helps your content before you switch a production path.

Treat the vendor's own claims, such as faster or cheaper, as hypotheses to test. The Ray3.14 line on the news page says 4x faster and 3x cheaper, and the only way to know what that means for your clips is to time and price a pilot.

• Store prompt, model id, and date for approved clips.
• Rerun on every new version.
• Compare cost, time, and look.
• Switch deliberately, not by default.

Where to look next

Read the live catalog for what Sume lists today. The video docs describe how to compare ids, ranges, and prices across models, and the stored posts on Scenes and Variants cover those two features.