Runway names paid plans but not a figure
Runway lists watermark-free output among its paid plan features. The line is stated at plan class rather than at a named tier, so this cell carries no figure and no plan name. As of 2026-09-12.
| The reading | What it holds |
|---|---|
| The recorded value | Watermark-free on paid plans |
| The vendor's own words | Watermark-free output is listed on the paid plans. |
| How the reading was taken | Read from a feature line attached to the paid side of the grid rather than to one named plan. |
Inclusion rule. One row for the value, one for the sentence or absence behind it, one for the method. Nothing here is drawn from output, support replies or coverage by anyone else. Order. Fixed order: the value, then its evidence, then the method.
| Generator | Paid tier |
|---|---|
| Fliki | No watermark on the paid plans |
| Runway | Watermark-free on paid plans |
Inclusion rule. Generators whose pages place the end of the visible mark on the paid side of a grid without printing a figure a reader could quote for it. Order. Alphabetical by generator name.
1A class of plans is a coarser answer than a tier
Most rows in this column name a plan and a price, which lets a reader work out what clean output costs. This one names neither. The feature is attached to the paid plans collectively, so the register records that and stops, because choosing a plan to attribute it to would be inventing precision the page does not have.
The practical consequence is small and real: a reader can tell that payment removes the mark and cannot tell how much payment. On a row where the crossing point is the cheapest plan that is a difference of a few dollars. On a row where it is two plans up, as it is elsewhere in this register, it is a difference of twenty.
2Two routes to the same models, one of them silent
This vendor publishes API pricing on pages separate from its plan pricing, and those pages do not repeat the watermark line. The register records the consumer plans because that is where the statement is, and it does not extend the statement across a boundary the vendor did not extend it across.
Where a company sells the same model through two routes, the route decides what the file carries. One generator here documents that outcome explicitly, with opposite defaults on its console and its interface. Here the second route is simply undocumented, which is a weaker finding and the same practical risk.
3What the cell holds, and why it is phrased that way
The recorded value repeats the vendor's own construction: watermark-free output is listed on the paid plans. That is a claim about a feature list. Paid output is clean would be a claim about files, and the page does not describe the mark or its absence in any file.
Keeping the two apart looks fussy until one changes without the other. A grid can gain a watermark-free line for a plan whose output never carried a mark, and a mark can appear on output whose plan line never mentioned one. Recording what was read keeps either change visible on the next reading.
4Sources
- Paid tierWatermark-free output is listed on the paid planslisted as a plan feature
- Paid tierNo watermark is listed as a benefit of the paid plans in the plan comparisonread from the plan comparison
The value above is read from runway.com, the vendor's pricing page, on 2026-09-12. The whole row for this generator is on its own page, and the rule for what this column may hold is on the paid tier column page. Neighbouring readings: SceneMixer, paid tier, Luma AI, paid tier.