Paid tier: where the visible mark stops, and what it costs
Paid tier records the plan at which a generator's own pages say the visible mark is no longer applied. Ten name a plan, and seven of those print a figure beside it, from $10 to $30 a month. The other five name no plan at all. As of 2026-09-12.
| Generator | Where the mark stops |
|---|---|
| Amazon Nova Reel | Same mark, no removal documented |
| D-ID | Still marked on Lite; clean above it |
| Fliki | No watermark on the paid plans |
| HeyGen | Removal from Creator ($29/mo) |
| Kling AI | Removal from Standard ($10/mo) |
| LTX Studio | No watermarking from Lite ($15/mo) |
| Luma AI | No watermark from Plus ($30/mo) |
| Pictory | No watermark from Starter ($25/mo yearly) |
| Pika | Watermark-free from $28 Pro |
| Runway | Watermark-free on paid plans |
| SceneMixer | Same switch, no plan condition stated |
| Sora | Not documented |
| Synthesia | Remove Synthesia logo from Starter ($29/mo) |
| Veo | Same mark, no removal documented |
| Wan | API parameter, default false |
Inclusion rule. Every generator on this register. A vendor that ties removal to no plan keeps its row, with what its pages say in place of a tier name. Order. Alphabetical by generator name.
1A crossing point is a packaging decision
LTX Studio stops marking at Lite, fifteen dollars a month. Pika stops at Pro, twenty-eight, and Luma AI at Plus, thirty. Kling AI stops at its first paid membership at ten dollars, Pictory at twenty-five, HeyGen and Synthesia at twenty-nine, and Runway stops on its paid plans without naming a figure, as do D-ID above its Lite plan and Fliki at a tier whose price its page does not print. Nothing in that spread is about the mark itself: a logo costs the same to leave off everywhere. What the numbers record is where each vendor draws the line between a trial and a customer, and the marking line rides along with it.
That is why this column holds a tier name and a price rather than a verdict. Two products whose crossing points differ by a factor of about two can be identical on this field in every way that reaches a file, and a reader choosing between them on this column alone is choosing on the wrong evidence.
2How the value is read off a grid
Four stages, in the same order every time. Find the plan grid the vendor publishes. Find the line about watermarking, which sits in a different place on each of them: an additions list on LTX Studio, a repeated feature row distinguished only by its icon on Pika, a benefit list on Kling AI. Take the first plan carrying it, with the list price printed beside it. Write both down with the address and the reading date.
The procedure is mechanical and it still goes wrong in one predictable way. On a cumulative grid a feature introduced at one tier is inherited upward without being repeated, so its absence higher up means nothing at all. The value this column wants is where the line first appears, never where it last appears.
3What this column does not settle
Upgrading changes what the product makes next. Nothing published by any vendor here says what happens to files already generated, and this register records none of it, because a claim about retroactive behaviour would have to come from watching output rather than from reading a page.
A crossing point is also not a licence. On LTX Studio the two boundaries are a plan apart: watermarking stops at Lite and commercial use starts at Standard, so a subscriber can hold a clean file they are not permitted to publish. Those lines are recorded separately for that reason, and this column carries only the first of them.
- Paid tierBrand watermark removal is listed as a benefit of every paid membership, from Standard at $10 a monthremoval is a plan benefit
- Paid tierWatermark-free download is included from the $28 Pro plan upwardfrom Pro and Fancy
- Paid tierNo watermarking is listed from the Lite plan at $15 a month upwardfrom Lite
- Paid tierWatermark-free output is listed on the paid planslisted as a plan feature
4Sources
Every value above is read from the vendor page named beside its row on the support table, checked 2026-09-22. What this column is allowed to hold is defined on the protocol page, and the rest of the columns are on the fields index. Next columns along: user toggle, machine-readable marking.