One cell of the register at a time
Each page here takes one generator and one column and says how that cell was arrived at: what the vendor's page actually prints, what kind of evidence that is, and which questions the cell does not answer. As of 2026-09-22.
Inclusion rule. One row per generator on the register. A cell carries a page where the vendor's own wording, or the shape of its silence, supports more than the table row can hold; a dash marks a cell whose value repeats nine other rows word for word. Order. Alphabetical by generator name.
The support table holds a value per cell and nothing else, which is the right shape for comparison and the wrong shape for argument. Two cells can both read watermark while one rests on a sentence a vendor wrote and the other rests on a feature line missing from one column of a grid. Those readings age differently, are wrong in different ways, and deserve to be argued with separately.
Not every cell has a page. Where the control column says the same nine words on nine rows, a page per row would be nine copies of one paragraph with the names swapped, so those rows are left to the support table and to the column's own page. What earns a reading here is a vendor that writes something specific, or a silence that is odd beside the rest of its column.
The evidence class is printed beside every value in the tables below and in the rail of each page. Four classes cover the register: a sentence the vendor wrote, a line carried by the layout of a grid rather than by its words, a default with no tier attached, and a plan whose absence means the question has no subject.
1The readings
- Amazon Nova Reel, all output — Everything it generates is marked, and none of the marking is something a viewer sees.
- D-ID, trial — Full-screen on the trial, with a stated reason: transparency about synthetic video.
- Fliki, free tier — A grid that lists the vendor's own watermark as something the free plan includes.
- HeyGen, free tier — A free plan bounded by video count, so the clean file and the allowance run out together.
- Kling AI, free tier — The free answer written out as a sentence, which is the rarest evidence class in this column.
- LTX Studio, free tier — A cumulative grid, where the free plan is whatever the additions lists have not yet added.
- Luma AI, free tier — Stated outright, and stated to be permanent: a later upgrade does not lift it from those files.
- Pictory, no free plan — An empty free cell for a third reason: the pricing page publishes no free plan to read.
- Pika, free tier — Every plan appears to include watermark-free download; only the icon beside the line says otherwise.
- Runway, free tier — A one-time credit allocation rather than a recurring tier, which changes who the cell describes.
- SceneMixer, free tier — A default rather than a tier: the same sentence answers the free and the paid question.
- Sora, free tier — A moving watermark scoped to downloads from the vendor's own surfaces, with no plan in sight.
- Synthesia, free tier — A grid that never prints the word watermark, so searching it for one finds nothing.
- Veo, free tier — This column holds a machine-readable answer here: a signal on every video, nothing on the frame.
- Wan, console default — The console stamps every video and the page says the stamp cannot be switched off there.
- Amazon Nova Reel, paid tier — Metered usage with no tiers, and an invisible mark that is not offered as removable.
- D-ID, paid tier — The one row where the first paid plan is still marked, with the mark named on both plans.
- Fliki, paid tier — Clean output on the paid plans, at a price the page does not print as text.
- HeyGen, paid tier — Twenty-nine dollars, where the removal line and the first real credit allowance start together.
- Kling AI, paid tier — The lowest crossing point recorded here: removal listed as a benefit of the first paid membership.
- LTX Studio, paid tier — Marking stops a plan below the commercial licence, which leaves a clean file nobody may publish.
- Luma AI, paid tier — Thirty dollars, and the crossing point applies only to files generated after it is paid.
- Pictory, paid tier — The cheapest published plan is also the crossing point, because nothing is published below it.
- Pika, paid tier — One of two rows where a paid plan is still marked: the $8 tier changes nothing about the file.
- Runway, paid tier — A crossing point named by plan class rather than by a figure, and an API route that repeats nothing.
- SceneMixer, paid tier — An empty crossing point for a reason no other row has: the vendor attaches no plan condition at all.
- Sora, paid tier — A mark described in detail with no plan anywhere near it, so there is no crossing point to record.
- Synthesia, paid tier — A crossing point that removes a logo, at two prices for one tier and none of them called a watermark.
- Veo, paid tier — Every video carries the signal and no page publishes a route off it, at any price.
- Wan, API parameter — The crossing point is a boolean in the request, published as defaulting to off.
- Amazon Nova Reel, control — Two marking mechanisms on all output, and no configuration published for either of them.
- D-ID, control — A plan benefit whose boundary sits one tier above the first payment, with the exception written out.
- Luma AI, control — A plan benefit whose window closes at generation: after that, nothing changes the file.
- SceneMixer, control — A switch in settings with an operational reason attached, and no plan condition anywhere near it.
- Sora, control — A mark described in more detail than most, and no published way to stop it being applied.
- Veo, control — Nothing in the documentation is offered as a way to change what the output carries.
- Wan, control — The caller decides, through a documented field; on the console nobody does.
- Amazon Nova Reel, file contents — Two mechanisms, a public inspection route and the only durability caveat any vendor here publishes.
- D-ID, file contents — A published rationale about disclosure, and no mechanism a receiving party could check.
- Luma AI, file contents — Unusually exact about the standing of files, and silent about what is written inside them.
- SceneMixer, file contents — The one page here that raises file contents without naming a scheme or a field, so the cell stays empty.
- Sora, file contents — C2PA named on all assets, with the detection route described as held inside the vendor.
- Synthesia, file contents — No word for the mark and no field for the file: two silences on one page, recorded apart.
- Veo, file contents — A scheme named, and a platform named that anybody holding the file can use to check it.
- Wan, file contents — Silence in the one document on this site written to enumerate everything a caller sends and receives.
Grouped by column, then alphabetically by generator inside each column, which is the order the columns appear in on every generator page.
Elsewhere in the register: Generators, Fields, Side by side, Implementers, Questions, Findings, Source documents, Terms, Learn, Data. Field definitions live on the protocol page.