GateTrue

What each generator documents about marking its output

One page per generator, four fields on every one of them

Every generator recorded here gets its own page, and every page answers the same four questions in the same order. That uniformity is the point: the fields can be read down a column as easily as across a row. As of 2026-09-12.

How a vendor sentence becomes a row on this registerA row starts at the vendor's own published page. Four fields are filled from it and nothing else: free tier, paid tier, control and machine-readable marking. Where the page says nothing about a field, the silence is recorded as the finding. The address and the reading date travel with the row, so the same check can be run again.Vendor's pageA pricing grid,a plan table ora product helppage, publishedby the companyitself.One sentenceFour fieldsFree tier, paidtier, control,machine-readable.Same four, sameorder, everygenerator.A filled field,or a blankSilence keptA field thepage does notaddress isrecorded as notdocumented,never inferredfrom the grid.A rowAddress anddateThe page it wasread from andthe day it wasread areprinted besidethe row.
Fig. 1 Four stages, and only the first one touches a page written by the vendor. Nothing after it adds information that was not on that page.

A vendor page is the only thing a row here is built from. Where a plan table says a watermark comes off at a named tier, the tier and the price go in. Where the plan table is silent, the field records that silence rather than an inference drawn from the shape of the pricing grid.

The fourth field is the one that stays empty on most rows. Machine-readable marking asks what a downloaded file carries once it leaves the product — a credential, a provenance manifest, a documented identifier of any kind. Twelve of the fifteen generators listed below publish nothing about it at all, and that is recorded as a finding rather than a gap in the reading. The three that do fill it are the three whose statements live in developer or safety documents rather than on a price list.

Pages are rewritten when the vendor page they were read from changes, not on a calendar. Each entry carries the address it was read from and the date it was read, so a reader can re-run the same check without taking this register's word for it.

1The entries

  • Kling AI — Brand watermark on the free plan, removal listed as a benefit of every paid membership from Standard upward.
  • Pika — Watermark-free download arrives at the $28 tier, not at the $8 one, which is unusual enough to be worth the row.
  • LTX Studio — The free plan is read by omission: no watermarking appears on the paid feature list and not on the free one.
  • Runway — Watermark-free output is a paid plan feature; the free tier is described only by what the paid list adds.
  • SceneMixer — A visible mark on composited episodes, off by a settings switch rather than by a plan condition.
  • Luma AI — The licensing guide says a Free or Lite watermark stays on those files even after the subscription is upgraded.
  • HeyGen — Watermark removal is a plan line from Creator upward, and the mark it removes is never described.
  • Synthesia — The word watermark never appears; the plan grid offers to remove a logo instead, from the Starter plan.
  • Sora — A system card rather than a price list: a moving watermark on downloads, and C2PA metadata on every asset.
  • Veo — Two sentences in the API documentation, under Limitations: SynthID on every video, and a platform that verifies it.
  • Wan — The console stamps AI generated and cannot be told not to; the API takes a watermark parameter that defaults to false.
  • Amazon Nova Reel — An invisible watermark on all output, Content Credentials on 1.1, and the vendor's own caveat about metadata being removed.
  • Fliki — One of the few free tiers described in a sentence: the free plan includes the Fliki watermark.
  • D-ID — A full-screen mark on the trial, a reason printed beside it, and a first paid plan that is still marked.
  • Pictory — No free plan at all, and No watermark printed as a feature of the cheapest paid one.

Each row in the support table links back to the page it came from, so a figure that looks wrong can be traced to the vendor sentence behind it in one click.

The rest of the register: Fields, Readings, Side by side, Implementers, Questions, Findings, Source documents, Terms, Learn, Data, and the field definitions on the protocol page.