VideoGenReview

What each AI video model's release notes say changed

Terse logs and wordy posts

Makers write notes for different readers. PixVerse's API changelog is a table of one-liners, V5.5 released or Upscale feature released, and says nothing about behaviour. Luma writes a post per change, with a stated purpose and examples. Kling's API log sits between, one heading with a few lines of parameters. As of 2026-09-25.

Where this note's examples come fromThe examples in this note come from 4 entries across 3 model lines.ExamplesKling AI1 entryLuma Ray1 entryPixVerse2 entries
Fig. 1 Each example links to its line page.

A terse log is easy to date and hard to interpret; a wordy post is the reverse. The register keeps each entry's value to what the note states, so a one-line note gives a one-line entry.

The style also shapes the counts. A maker that logs every parameter change, as Kling does in its API updates, collects many entries for small steps; a maker that posts once per model, as MiniMax does, collects few entries for large ones. Neither count is a measure of how much the model improved.

The entries this note draws on, read 2026-09-25.
DateLineVersionWhat changed
2 June 2025Luma RayNot named in the noteModify Video keeps a performance and changes the world around it
2 December 2025PixVersePixVerse V5.5V5.5 is released
15 December 2025Kling AIKling 2.6Kling 2.6 launches with a switch for generating sound
16 June 2026PixVerseNot named in the noteUpscale is released

Inclusion rule. Entries used as examples in this note. Order. By date, oldest first; undated rows last.

1In the notes

With Modify Video, you can keep what matters and evolve everything else.

Luma, Modify Video post

V5.5 released

PixVerse, API changelogs

Control whether to include audio when generating videos through the sound parameter.

Kling AI, API updates

Upscale feature released!

PixVerse, API changelogs

2Other reading notes

3Notes read