LLMSwaps

Which model each app runs today, and when it last changed

A meter per output, and no library behind it

Each video model here meters its own unit: some charge for a second of footage, others for a finished clip. That shapes what the page needs to say about material. Delivery is the whole relationship, so retention is not addressed, and a line leaving the price list removes a purchasable engine rather than a collection. As of 2026-09-22.

What per-output billing settles about material and about a line leaving. Recorded 2026-09-22.
What the page is askedWhat fal publishesWhat that leaves open
Is disposal of material addressedNot addressed on the pricing pageThe relationship ends at delivery of the unit
How the meter worksOne unit per model, second or clipQuoted from the page rather than inferred
What a removed line takes awayA purchasable model, priced individuallyOther lines keep their own prices
Is there a plan to loseModels are priced individually, not bundledSo no tier moves when one line goes

Inclusion rule. Read from the public pricing page, restricted to video models. Storage products offered separately by the same company are out of scope for this column. Order. The absence first, then what the meter implies.

1Per-model pricing changes what a retirement costs

Where models are bundled into a plan, losing one changes what a subscription is worth. Where each model carries its own price, losing one removes a line and leaves every other price untouched.

That makes this entry unusually legible. A reader can see exactly which capability disappeared and what it used to cost, which is the arithmetic every bundled entry hides.

2Two units on one page

Some engines meter a second of footage and others a whole clip, which the page states rather than leaving to be worked out. For a production that is a budgeting fact; for this column it is a clue about the shape of the product, where units are delivered rather than accumulated.

It also means there is no place for material to sit. The register records that as an absence with a structural explanation, the same as the platform entries in this column.

A meter that records what a library would have hiddenWhere models are bundled into a plan, losing one changes what a subscription is worth and the arithmetic is invisible. Where each model is priced individually, the invoice already says which engine produced what and at what rate.Bundled planPer-model meterA line leavesThe plan is worth less, somehowOne price disappearsWhich model made thisReconstruct it, or guessOn the invoice alreadyUnitA subscriptionA second, or a videoMaterial heldOften a library insideDelivered, then yoursWhy this column is blank here for a structural reason
Fig. 1 The bookkeeping this register keeps recommending falls out of the billing model rather than being an extra habit.

3What still has to be kept somewhere

Per-output delivery means the files are the customer's from the first second, and so is the obligation to keep them. Nobody is holding a copy to fall back on.

Combined with per-model prices, that makes the bookkeeping unusually easy to do properly: the invoice already says which model produced what. Most entries in this register make that connection impossible to reconstruct.

  • How the meter works
    Video models are billed by output unit, per second or per video depending on the modelquoted from the pagefal, pricing page / recorded 2026-09-22
  • Models carried
    Wan 2.5, Kling 2.5 Turbo Pro, Veo 3 and Ovi, each priced individuallypriced per model rather than per planfal, pricing page / recorded 2026-09-22

4Sources

Read from the pricing page on fal.ai, 2026-09-22. The whole entry is on fal, and the column it sits in is on Stored work. Same column, other entries: LTX Studio, SceneMixer.