How AI video gets marked, one generator at a time

GateTrue records what each AI video generator publishes about marking its output: what the free tier carries, what a paid plan changes, how the mark is removed, and what the vendor says is written into the file. Four fields, the same four for everyone. As of 2026-09-12.

Inclusion rule. Generators whose public pages state whether output carries a mark. Silence on the point means no row. Order. Alphabetical by generator.

1What is recorded here

Each generator gets one page, and every page answers the same four questions in the same order. That uniformity is the point: a table where one product is described by its marketing and another by its plan table is not a comparison, it is two advertisements side by side. Fields come from the vendor's own public pages, and where a vendor does not publish an answer the field says so.

Two layers get conflated constantly in this subject and are kept apart here. A visible watermark is something a viewer sees and a crop removes. A machine-readable mark is a signal written into the file for software to find. Most vendors document one and say nothing about the other.

The four fields are fixed before any vendor is read, which is what keeps the table honest when a vendor publishes a great deal about one of them and nothing about the rest. A generator with a detailed plan table and no word about file contents ends up with three filled fields and one marked not documented, and that shape is itself informative: it says the vendor treats marking as a pricing question rather than a provenance one.

2Start here

• Support table — six generators, four fields, one row each.
• SceneMixer — a settings switch rather than a plan gate.
• Kling AI — removal listed as a paid-membership benefit.
• LTX Studio — no watermarking from the Lite plan up.
• Pika — watermark-free download from the $28 plan up.
• Runway — watermark-free output on the paid plans.
• SynthID — an invisible mark with no removal documented.
• Protocol — how a field gets filled in, and what not documented means.
• What earns a row — vendor pages only; output and support replies do not count.
• How a row changes — two dates per field, and what each of them means.

3Questions the table can answer

4Explainers

How marking actually works under the hood, written for somebody who has to make a decision about it. These pages describe mechanisms; what any particular generator does about them is kept in the support table with a date on every field.

• Metadata vs watermark — two layers that live in different places and fail in opposite ways.
• Reading a plan table — how to tell an exclusion from a summary on a pricing grid.

Each of these takes one question, answers it in a sentence, then shows the rows it rests on. They read the same six entries as the table; what differs is what is being asked of them.

• What the free tiers put on your file — three of four rows are omissions, not sentences.
• What it takes to get the mark off — $15 to $28, and nobody is pricing the mark.
• The generator that uses a switch — applied at compositing, with a stated reason.
• The column that is empty on five of six — and why it stays in the table.
• What survives being re-encoded — two layers that fail in opposite directions.
• Who can check whether a file is marked — one published route out of six.
• At which step the mark gets written — generation, compositing, or unstated.
• When two marking systems land on one file — the collision one vendor names.

5How entries are kept

Both dates on a field mean different things: one records when the value was written down, the other when the vendor page was last opened to confirm it. Only the second moves on a confirmation. If the vendor page and a field here diverge, the vendor page settles it.

GateTrue is a record of what vendors have written about marking. Nothing here judges a product against a rule, and nothing here is a legal opinion.