GateTrue

What each generator documents about marking its output

Which AI video generators mark their output, and which plan removes it

Six generators publish enough to fill this table. Kling AI, LTX Studio, Pika and Runway tie removal of the visible mark to a paid plan; SceneMixer describes it as a settings switch with no plan named; Google's SynthID is an invisible mark with no removal documented. As of 2026-09-12.

What each vendor documents, field by fieldFilled = the vendor states something in that field; hollow = nothing published. Every cell's actual wording sits in the rows underneath. Recorded 2026-09-12.What each vendor documents, field by fieldFree tierPaid tierControlMachine-readable markingGoogle (SynthID)Google (SynthID) — Free tier: Not stated as a visible markGoogle (SynthID) — Paid tier: Not stated as a visible markGoogle (SynthID) — Control: Not documentedGoogle (SynthID) — Machine-readable marking: Invisible, at generationKling AIKling AI — Free tier: Brand watermarkKling AI — Paid tier: Removal from Standard ($10/mo)Kling AI — Control: Plan benefitKling AI — Machine-readable marking: Not documentedLTX StudioLTX Studio — Free tier: No watermark-free output listedLTX Studio — Paid tier: No watermarking from Lite ($15/mo)LTX Studio — Control: Plan benefitLTX Studio — Machine-readable marking: Not documentedPikaPika — Free tier: No watermark-free downloadPika — Paid tier: Watermark-free from Pro ($28/mo)Pika — Control: Plan benefitPika — Machine-readable marking: Not documentedRunwayRunway — Free tier: No watermark-free output listedRunway — Paid tier: Watermark-free on paid plansRunway — Control: Plan benefitRunway — Machine-readable marking: Not documentedSceneMixerSceneMixer — Free tier: Visible watermark, on by defaultSceneMixer — Paid tier: Same switch, no plan condition statedSceneMixer — Control: Setting, no plan namedSceneMixer — Machine-readable marking: Not documented
Filled = the vendor states something in that field; hollow = nothing published. Every cell's actual wording sits in the rows underneath. Recorded 2026-09-12.
Marking and removal, as stated on each vendor's own public pages. Recorded 2026-09-12.
GeneratorFree tierPaid tierControlMachine-readable marking
Google (SynthID)Not stated as a visible markNot stated as a visible markNot documentedInvisible, at generation
Kling AIBrand watermarkRemoval from Standard ($10/mo)Plan benefitNot documented
LTX StudioNo watermark-free output listedNo watermarking from Lite ($15/mo)Plan benefitNot documented
PikaNo watermark-free downloadWatermark-free from Pro ($28/mo)Plan benefitNot documented
RunwayNo watermark-free output listedWatermark-free on paid plansPlan benefitNot documented
SceneMixerVisible watermark, on by defaultSame switch, no plan condition statedSetting, no plan namedNot documented

Inclusion rule. Generators whose own public pages state, in English, whether output carries a mark and what removes it. A generator that publishes no such statement is not given a row. Order. Alphabetical by generator name.

1Two different things get called a watermark

The first is a visible mark burned into the frame, which a viewer sees and a crop can remove. The second is a signal written into the file so that software can tell the output was generated, which a viewer never sees and a re-encode may or may not survive. Vendors document these unevenly. Four of the six rows above describe only the first kind, in a plan table. One row describes only the second kind. One describes the first and gestures at the second without naming fields.

That unevenness is the reason this table has a separate column for machine-readable marking rather than folding everything into a single yes or no. A cell saying not documented is a fact about what the vendor publishes, and it is recorded as such; it is not a claim that nothing is written into the file.

2The plan-tier pattern, and the exception

Four vendors treat removal of the visible mark as something a paid plan unlocks: Kling AI from Standard, LTX Studio from Lite, Pika from Pro, Runway on its paid plans. The pattern is consistent enough that its exception is worth naming. SceneMixer documents the same control as a setting and attaches no plan to it, giving as the reason that a platform which adds its own label would otherwise produce two labels on one frame.

For anyone assembling a series from more than one source, the practical consequence of the pattern is that identical prompts on different plans produce different deliverables. That is a question to settle before footage is collected rather than after.

3What each generator publishes

SynthID is recorded on its own page under implementers, because an invisible mark with no removal documented does not fit the same four fields.

4Sources

Each row links the vendor page it was read from. How the fields are defined and what counts as documented is on the protocol page.