Synthetic-media instruments, by article and effective date
Synthesia, read against Article 50
Synthesia publishes its marking statement in a support article about removing the mark, which means the conditions are spelled out: a plan tier puts it there, and so does generating through the API with the test flag set. As of 2026-09-12.
Fig. 1 Where two unrelated conditions switch one mark on, the account tier alone does not explain why an archived file carries it.Fig. 2 Filled where the page behind the row names something in that column, hollow where that page is silent. Silence is recorded rather than filled in.
What Synthesia publishes, set against the two duties Article 50 imposes. Recorded 2026-09-12.
Point
What the vendor's pages state
Article 50(2), machine-readable marking
Not documented on the page this entry reads from
Article 50(4), deployer disclosure
A visible mark on Basic-plan videos and on test-mode output
A test-mode mark cannot be taken off a finished video
Inclusion rule. Points are the same four for every generator recorded here: the two Article 50 duties, who controls the mark, and whatever the vendor states about it. A point the vendor does not publish is recorded as not documented. Order. Fixed order, identical on every generator page.
Fig. 3 One point at a time, every generator side by side, Synthesia marked. This is a map of what the vendors publish, not a reading of the instrument. Wording in the rows below. Recorded 2026-09-12.
Every generator on one point, with Synthesia marked. Recorded 2026-09-12.
Inclusion rule. Generators whose own public pages say something about marking. A generator silent on this particular point keeps its row, marked hollow. Order. Alphabetical by generator name.
Fig. 4 One point at a time, every generator side by side, Synthesia marked. This is a map of what the vendors publish, not a reading of the instrument. Wording in the rows below. Recorded 2026-09-12.
Every generator on one point, with Synthesia marked. Recorded 2026-09-12.
A visible mark on Basic-plan videos and on test-mode output
Inclusion rule. Generators whose own public pages say something about marking. A generator silent on this particular point keeps its row, marked hollow. Order. Alphabetical by generator name.
Fig. 5 One point at a time, every generator side by side, Synthesia marked. This is a map of what the vendors publish, not a reading of the instrument. Wording in the rows below. Recorded 2026-09-12.
Every generator on one point, with Synthesia marked. Recorded 2026-09-12.
Inclusion rule. Generators whose own public pages say something about marking. A generator silent on this particular point keeps its row, marked hollow. Order. Alphabetical by generator name.
2Two unrelated conditions put the same mark on a file
One condition is commercial and the other is technical. A Basic-plan account gets the mark because of what it pays; an API request gets the mark because of a flag that says the call is a trial rather than a production run. Both routes end with the same pixels on the same video, and a reader reconstructing why a given file is marked has to know which route produced it.
That is a documentation shape worth noticing, because most entries in this record have a single lever. Where two unconnected conditions can switch the same mark on, the answer to whether an archived file should have carried one cannot be read off the account tier alone. It depends on how the file was requested, and that is not visible in the file.
3The rare entry that says a mark is permanent once written
The article states plainly that a mark applied to a test-mode video stays on that video, and that getting an unmarked version means issuing the request again with the flag off. Nothing else recorded here describes a mark as irreversible on an existing file; every other removal statement is about future output.
Read against the disclosure duty that is a small piece of good news for whoever has to account for a delivery: a marked file from this route cannot have been quietly cleaned up afterwards, because the vendor says there is no such operation. Read against the provider duty it says nothing, because the page never mentions a signal inside the file, and this entry does not invent one.
Four words is all a row holds. Where a cell read off Synthesia's knowledge-base article needs the sentence behind it, the kind of document that sentence sits in and the limit on what it proves, it is filed on its own page below.
Synthesia on when a mark appears — The article says the watermark appears under certain conditions, naming the Basic plan and API test mode.
Read from the knowledge-base article at help.synthesia.io on 2026-09-12. The clause itself is recorded on the Article 50 page, and every generator on the same points is in the table.
Synthesia (synthesia.io)
The watermark appears on videos generated under certain conditions, such as being on the Basic plan or generating in API test modean avatar video platformSynthesia, knowledge base/ recorded 2026-09-22
Synthesia
Basic-plan users are told to upgrade the plan and re-generate the videothe route off the visible markSynthesia, knowledge base/ recorded 2026-09-22
Synthesia
A mark applied in test mode cannot be removed from an existing video; a new request with the test flag off is requiredthe API half of the same pageSynthesia, knowledge base/ recorded 2026-09-22