GateTrue

What each generator documents about marking its output

Marking systems that are not a line on a pricing page

Some marking systems are not a plan feature at all. They are described as a property of the product, with no tier attached and nothing offered as removable, so they are kept in a separate column rather than forced into a yes-or-no cell. As of 2026-09-12.

Two shapes of marking, and why they cannot share a columnPlan-table marking is a feature: it is visible, it is attached to a tier, and a paid plan lifts it. Product-level marking is a property: nothing is visible, no tier is named, nothing is offered as removable, and the claim is about surviving ordinary handling of the file. Recorded in one column, the two would contradict each other on every line.Plan-table markingProduct-level markingCan a viewer see itYes, drawn into the frameNo, embedded in the signalWhat lifts itA named paid tierNothing is offeredWhere it is describedThe pricing gridA product page about the systemWhat is claimed about itThat it goes awayThat it stays through an exportSame questions, opposite answers
Fig. 1 The same four questions produce opposite answers, which is why these entries are kept in their own section rather than squeezed into the support table.

The register's four fields assume a familiar shape: a mark you can see, a plan that takes it away, and a file that carries nothing. An invisible watermark inverts all three. Nothing is visible, no tier lifts it, and the claim is that the signal outlives ordinary handling of the file. Recording that as no in the removal column would be false, and recording it as yes would be worse.

So these entries are kept apart and read on their own terms. What the implementer publishes about scope, about the moment the signal is written, about which transformations it is designed to survive, and about how anyone outside the company can check a file — those four things are what the page records.

The distinction matters for a publisher with a compliance question, because detection and marking are separate capabilities. A generator can write a signal that nobody outside the vendor can read, and a platform can read a signal that most generators never write. One entry here covers the first case; the support table covers the second.

A system earns an entry when the company that builds it publishes the four things above on its own pages. Descriptions written by anyone else, talks and press coverage do not qualify, for the same reason a marketing claim about a competitor does not qualify anywhere else on this site.

1The entries

  • SynthID — Google's invisible watermark: where it is embedded, when it is written, which transformations it is designed to survive, and the two published routes for checking a file.

The support table records what each generator publishes about marking; this section records what the marking systems themselves publish.

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