Which pages document a watermark, and which question this register cannot answer

Whether a law requires a watermark is not something this register has standing on: it records vendor pages, not statutes, and nothing here is a legal opinion. What it does hold is which tools document a mark. Kling AI prints one on the free plan and prices its removal; Veo's documentation names SynthID on every video. As of 2026-10-13.

1Lines this register already holds

The register's lines on marks and the absence of them: what the free tier carries, what lifts a mark, and what each of these pages does and does not say about the inside of a file.

• Visible mark
  Output carries a brand watermark on the free Basic planfree planKling AI, membership plans / 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
• Machine-readable marking
  Not documented on the vendor's public pages (as of 2026-09-12)not mentioned in the plan tableKling AI, membership plans / recorded 2026-09-12
• Machine-readable marking
  Videos created by Veo are watermarked using SynthID, described as the vendor's tool for watermarking and identifying AI-generated contentstated under LimitationsGemini API, Veo documentation / recorded 2026-09-22
• Detection
  Videos can be verified using the SynthID verification platforma named platformGemini API, Veo documentation / recorded 2026-09-22
• Visible mark
  Not documented on the vendor's public pages (as of 2026-09-22)nothing published about a mark on the frameGemini API, Veo documentation / recorded 2026-09-22
• Control
  Not documented on the vendor's public pages (as of 2026-09-22)no plan and no request parameter publishedGemini API, Veo documentation / recorded 2026-09-22
• Machine-readable marking
  An invisible watermark is embedded across Google's generative AI consumer productsproduct-wideGoogle DeepMind, SynthID / recorded 2026-09-12

2The search names a law; the record names pages

The question this page is reached by asks whether a state requires watermarks on AI video. That is a legal question, and this register states nothing about compliance: it records what vendors publish, cells are read from vendor pages, and no line on it is a legal opinion. What can be answered from those pages is narrower, and checkable in a sitting — which tools say they put a mark on output, and which of them say anything about the inside of the file.

The collection counted sixty-eight near-identical threads carrying the question, filed under copyright and legal matters. That count is the reason this page exists rather than being left to the register: people arrive with a law in mind, and the honest thing a record can do is mark where its evidence stops and hand over what it does hold.

3Where a visible mark is documented, and at which tier

Across this register the visible mark is most often documented in one place: the plan table, where it appears as a line on the free column and as removal among the paid benefits. Kling AI is the clearest case of that shape. Its membership page states that output carries a brand watermark on the free Basic plan, and lists brand watermark removal as a benefit of every paid membership from Standard at $10 a month at list price. What the page does not do is describe the mark: no position, no size, no behaviour on export. The field is filled and the object stays unexamined, which is how it is recorded.

Google Flow's own page comes at the same window from the other side. It names the engines the suite is built around — Veo 3.1 with native audio, Nano Banana and Gemini Omni — and states a free entry on a Google account with fifty daily credits. The marking sentence for that model line is filed on this register with the developer documentation rather than with the product page: videos created with Veo are watermarked using SynthID, and the same page names a platform where one can be verified.

4A mark on the picture and a mark in the file

Two layers are kept apart on this register by design. A visible mark is drawn into the frame: a viewer sees it, a crop can take it away, and it is usually tied to a plan. A machine-readable mark is written into the file for software to find, and most entries here do not document one at all. Veo's documentation names SynthID and says nothing about a mark on the frame or a setting that changes either layer; Kling's membership page says nothing about the inside of a file. Both silences are recorded as silence.

Where the second layer is documented, the mechanism is worth reading exactly. Sora's system card lists C2PA metadata on all assets beside a visible moving watermark on downloads, with no plan attached to either. Wan's API reference is the contrast: a request field for the visible stamp, defaulting to false, and no provenance field anywhere among its parameters or its response. Two shapes of one question, printed side by side rather than averaged into a column of yes and no.

5What the counts around one name add up to

The collection counted 8,089 posts and 1,318 comment mentions around Kling, and the question it quotes below is one this register cannot act on: whether a viewer could tell the clip was made with a given tool. That is a question about output, and nothing here is produced by looking at output. What the register can do is record what the pages state, which is where the tier, the plan and the parameter lines above come from.

The count is still worth printing beside those lines, because it shows the question is asked at scale rather than in passing. A reader who wants the other half, what the marks actually do inside files, has to run material through something; this page says plainly that it does not, instead of letting a filled table imply an answer.

6What each named tool's own pages state

Inclusion rule. Tools this page is about, each read on its own public pages and dated in the last column. A maker's cell carries the wording of the page read; the pipeline's cell is one sentence quoted from its own guides. A point a page does not carry is printed as not stated rather than paraphrased from somewhere else. Order. Alphabetical by named tool.

7What the collected threads counted

The lines below belong to the name the collection counted around this question, and the counts are what a record of conversation can honestly contribute here.

Inclusion rule. Names carried in the collected material and read on this page. A post arguing with itself can be counted in the positive and the negative column both. Order. Descending by posts.

Inclusion rule. Questions the collection counted around the names on this page, quoted as written. Order. Descending by the thread count.

8When the named tool is the safer arrangement

• The mark is announced before anyone pays — A free plan whose output carries a stated brand watermark is a mark a buyer knows about in advance, rather than one discovered on delivery.
• Removal is a line in a table, not a policy question — On this entry removal is listed plan by plan, so the crossing point can be read off the sellers' own page and checked against an invoice.
• The engines behind the suite are named — Naming Veo 3.1 and the rest lets a reader trace a marking statement to the documentation it belongs to instead of taking a product page's word for it.

This page is reached by asking "Does California require watermarks on AI videos?" — a question a record of vendor pages can only half answer. Read beside it: Higgsfield's own record and Sora's export window.