GateTrue

What each generator documents about marking its output

User toggle: whether a person or an invoice decides

User toggle records how the mark comes off, which is a different question from whether it can. Ten times the answer is a plan benefit. SceneMixer documents a switch in settings, Wan a watermark parameter in the request, and three publish no route at all. As of 2026-09-12.

A plan benefit and a setting, compared on four questionsBoth mechanisms can produce the same delivered file. They differ on who is able to change the state, on when it can change, on whether anyone can reconstruct the state months later, and on which generators this register finds documenting each of them.Plan benefitSetting in the productWho changes the stateWhoever pays the invoiceWhoever opens the settings pageWhen it can changeWhen the subscription doesBetween one clip and the nextRecoverable laterFrom the billing recordOnly if somebody wrote it downDocumented byKling AI, LTX Studio, Pika, RunwaySceneMixerSame output, different bookkeeping
Fig. 1 The delivered file can be identical either way. Everything that separates the two columns is about accounting rather than about pixels.
Field by field, what each vendor statesFilled where the vendor publishes something in that field, hollow where its pages say nothing.Field by field, what each vendor statesHow the mark comes offHow the mark comesoffAmazon Nova ReelAmazon Nova Reel — How the mark comes off: Not documentedD-IDD-ID — How the mark comes off: Plan benefit, not a settingFlikiFliki — How the mark comes off: Plan benefit, not a settingHeyGenHeyGen — How the mark comes off: Plan benefit, not a settingKling AIKling AI — How the mark comes off: Plan benefit, not a settingLTX StudioLTX Studio — How the mark comes off: Plan benefit, not a settingLuma AILuma AI — How the mark comes off: Plan benefit, fixed at generationPictoryPictory — How the mark comes off: Plan benefit, not a settingPikaPika — How the mark comes off: Plan benefit, not a settingRunwayRunway — How the mark comes off: Plan benefit, not a settingSceneMixerSceneMixer — How the mark comes off: Yes, in settingsSoraSora — How the mark comes off: Not documentedSynthesiaSynthesia — How the mark comes off: Plan benefit, not a settingVeoVeo — How the mark comes off: Not documentedWanWan — How the mark comes off: A request parameter, not a plan
Fig. 2 Filled where the vendor publishes something in that field, hollow where its pages say nothing.
The control each vendor documents, and whether a plan is named beside it. Rows read on their own dates, the most recent 2026-09-22.
GeneratorHow the mark comes off
Amazon Nova ReelNot documented
D-IDPlan benefit, not a setting
FlikiPlan benefit, not a setting
HeyGenPlan benefit, not a setting
Kling AIPlan benefit, not a setting
LTX StudioPlan benefit, not a setting
Luma AIPlan benefit, fixed at generation
PictoryPlan benefit, not a setting
PikaPlan benefit, not a setting
RunwayPlan benefit, not a setting
SceneMixerYes, in settings
SoraNot documented
SynthesiaPlan benefit, not a setting
VeoNot documented
WanA request parameter, not a plan

Inclusion rule. Every generator on this register. The value is the mechanism the vendor's own pages describe, not a judgement about whether the mark can be removed at all. Order. Alphabetical by generator name.

1Two mechanisms, one file

Ten generators answer this column the same way: removal is something a plan includes. SceneMixer answers it with a switch in settings and names no plan beside it, giving as its reason that a publishing platform which adds a label of its own would otherwise put two labels on one frame. Wan answers it with a field in the API request, documented with a default of false, while the same models called through the console are stamped and cannot be told otherwise. The delivered file can end up identical. What differs is who is able to change it, and when.

Whether the mark can come off is a question the paid tier column already answers. This one asks what has to happen for it to come off, which is the part a production organises around rather than budgets for.

2Which of the two can be reconstructed later

When the mark is tied to a subscription, every file made under that subscription is in one state, and the state can be recovered months afterwards from the invoice. Nobody changes it mid-shoot by clicking the wrong thing, and a contributor cannot hand over something different from what they handed over last week without the billing record showing it.

A switch is the opposite trade. It can be set per delivery, which is the thing a plan benefit cannot do at all: marked files for a client review and clean files for the master, from one account. It also leaves no trace, so a team that wants to know which of the two states a given episode came out of has to have written it down at the time.

3What this column does not settle

It does not say the mark can be removed on a given plan, only what the mechanism is where removal is documented at all. It does not say a switch is offered to everyone, because a vendor may attach conditions on a page this register has not read. And it says nothing about defaults beyond the wording: SceneMixer's switch is documented as on until somebody turns it off.

The distinction is worth carrying into any project that collects footage from more than one contributor. On ten of these generators the deliverable depends on whose account it came from, and on one it depends on which surface the caller used, which is a question to settle before material is gathered rather than in the edit.

  • User toggle
    An AIGC watermark switch in settings turns it offno plan condition statedSceneMixer, compliance guide / recorded 2026-09-12
  • Visible mark
    A visible watermark is applied to composited episodes and is on by defaultstated in the vendor's own guideSceneMixer, compliance guide / recorded 2026-09-12
  • Paid tier
    Brand watermark removal is listed as a benefit of every paid membership, from Standard at $10 a monthremoval is a plan benefitKling AI, membership plans / recorded 2026-09-12

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: machine-readable marking, free tier.