When two marking systems land on one file
One vendor gives a reason for turning its watermark off: the upload destination may add a label of its own, leaving the frame carrying two. No other entry here acknowledges that a second marking system exists at all. As of 2026-09-12.
| Entry | What is published | Detail |
|---|---|---|
| Generator's visible mark | Applied by the tool | On by default where described |
| Platform's own label | Applied on upload | Outside this record's scope |
| Metadata layer | Written by the tool | Removed by re-encoding, per the same vendor |
Inclusion rule. Layers described on the public pages of entries in this record. Platform labelling is listed for context and is not recorded as a fact here, because it belongs to the platform. Order. In the order a file meets them.
1Two labels is a real outcome, not a hypothetical
A file generated by a tool that marks by default and uploaded to a platform that labels AI-generated uploads carries both. Whether that matters is a judgement for whoever publishes it; that it happens is mechanical, and one vendor has written down that it happens.
The wider point is that a generator controls one layer of several. A record organised around generators can say precisely what that one layer does and has to be explicit that it is not the whole picture.
2The layers fail in opposite directions
The visible mark survives re-encoding and is removed by a setting or a plan. The metadata layer survives a setting change and is removed by re-encoding. A file can therefore end up with the logo and no metadata, or the metadata and no logo, entirely through ordinary handling.
Anyone reasoning about what a file carries from the fact that it has a logo on it is reasoning about one layer only. That is the whole reason this site keeps visible and machine-readable as separate fields rather than one marked column.
3What is deliberately out of scope here
What individual platforms do on upload is not recorded on this site. It changes faster than any of the vendor pages here, it varies by region and by account type, and a record that tried to track it would be wrong more often than right.
What is recorded is the one sentence a generator wrote about the collision, because that is the part inside this record's boundary and it is the only acknowledgement of the problem anywhere in it.
- User toggleAn AIGC watermark switch in settings turns it offno plan condition stated
- MetadataThe guide tells publishers to keep whatever content credentials or generation metadata the tool writes, and warns that re-encoding can strip themdescribed but not enumerated
4Sources
Every line is read from the vendor pages listed on the support table, checked 2026-09-12. What earns a row is set out in the protocol. Nearby: Free tiers, Getting it off, A switch instead.