A paid switch over a kept watermark, and no route at all
One entry gives paid members a switch for its visible badge and says in its terms that the invisible layer under it is never removed. The other names SynthID under Limitations and publishes no plan, parameter or setting that changes it. From 2 source pages, read 2026-09-22 to 2026-10-13; no maker pays to be listed.
| On this question | SceneMixer | Veo |
|---|---|---|
| The control | A switch for paid members | Nothing published |
| The visible layer | A corner badge at delivery | Nothing visible described |
| The invisible layer | Kept on, per the terms | SynthID, on every video |
| What a recipient can check | Nothing published yet | A named verification platform |
| Document read | Terms and product pages | Developer documentation |
Inclusion rule. One row per question on which these two entries can be compared from their own published pages. Questions neither vendor addresses are left out rather than filled with a dash. Order. Fixed order: the mechanism first, then who holds it, then what it leaves behind.
| Generator | User toggle | Document read |
|---|---|---|
| SceneMixer | Plan benefit, a switch for paid members | terms of service |
| Veo | Not documented | Veo API documentation |
Inclusion rule. The two entries on this page, with the value each one's own pages support in the column they diverge on. Order. Alphabetical by generator name.
1Both keep an invisible layer on
On the question that matters most to a platform's software the two rows agree: each describes an invisible signal that no plan, parameter or setting removes. One calls it SynthID; the other's terms call it a compression-resistant watermark or content credential.
2Only one describes what a viewer sees, and who can change it
One entry also applies a corner badge at delivery and lets paid members switch it off for later renders. The other describes no visible mark at all, so there is nothing on its side of the control column to switch.
For a production that publishes to platforms with their own labels, that difference is the practical one: a visible badge can collide with a platform's label, and only one of these entries gives a way to avoid the collision.
3Where Veo is ahead: a reader
Veo's documentation names a verification platform, so a recipient can check a file. The other entry publishes no reader for its invisible layer yet, so its commitment is in a contract rather than in a check anyone can run.
4Sources
- User togglePaid members can switch the badge off for later renders; the terms make removing the visible label an optional paid feature where the law permitstied to a paid membership
- Machine-readable markingAn invisible, compression-resistant watermark or content credential is applied to output and never removedstated in the terms
- ControlNot documented on the vendor's public pages (as of 2026-09-22)no plan and no request parameter published
Both values above are read from the vendor pages linked in the rows: scenemixer.com and ai.google.dev, on 2026-10-13. Each entry has its own page, SceneMixer and Veo, and the rule for the column they diverge on is on the control column page. Other pairs: ten dollars, or twenty-eight, the described marks.