Two generations included, none marked as first
A single membership reaches the current pair and a previous generation. The newer models are promoted as current, which is a marketing position rather than a stated default, and nothing on the plan page says which engine a project runs on when nobody selects one. From 1 source page, read 2026-09-12; no maker pays to be listed.
| What the page is asked | What Kling AI publishes | What that leaves open |
|---|---|---|
| Is a starting tier stated | Not stated on the plan page | Both generations appear as benefits |
| Which is presented first | The newer pair, promoted as current | Promotion is not a lifecycle statement |
| Is the older generation included | Yes, listed as a plan benefit | So staying on it needs no extra purchase |
| What a default would settle | Which engine untouched work came from | Which decides how far a change reaches |
Inclusion rule. Filled when the entry's own public page says which model a new project starts on, or when a single-model menu makes the answer follow from the list having one line. Order. The absence first, then what the plan bundles instead.
1Bundling both removes the pressure and keeps the ambiguity
Including two generations means nobody is pushed forward when a new one ships, which is the useful half. The unhelpful half is that a customer cannot tell which of the two produced their existing work unless they recorded it themselves.
A stated default would have answered that for free. Without one, the question falls back on the customer's own bookkeeping, which is where this register keeps sending readers for a reason.
2Current is the closest thing to a default here
Promoting a pair as current is a strong hint about what a new user gets and it is not a statement. Promotion order can change with a campaign, and nothing about it describes what the product does in the absence of a choice.
The register records hints as hints. Filling this cell with the promoted pair would make the column look complete while resting on a page layout.
3Why the answer matters more here than on a single-line menu
With two generations live, a version change can reach one set of projects and not another, so the size of the affected group depends entirely on which line was the default.
On a one-model entry that question is trivial because everybody is on the same line. Here it is the difference between a change affecting most delivered work and almost none of it.
4Production that outlasts a model
Model end dates touch “Kling AI”; SceneMixer's guides describe how its pipeline treats the models it runs:
A script is read once per project; switching affects new tasks, such as regenerating a storyboard.
SceneMixer, Which text tier for reading and storyboards — “Do I need to re-read the script when I switch?” (read 2026-10-13)
Recommended is the badge on the tier the site suggests for most character sheets; the default for new accounts stays the cheaper tier.
SceneMixer, Qwen-Image 3.0 Pro: the recommended tier — “Is Recommended the same as default?” (read 2026-10-13)
5Sources
Read from the membership plans on kling.ai, 2026-09-22. The whole entry is on Kling AI, and the column it sits in is on Default tier. Same column, other entries: Luma, Runway.