How SceneMixer marks its output
SceneMixer (scenemixer.com), an AI short-drama generator, documents its marking in a compliance guide rather than in a plan table. That makes it the exception here: the switch is described as a setting, not as something a plan unlocks. As of 2026-09-12.
| Field | What the vendor's pages state |
|---|---|
| Free tier | Visible watermark, on by default |
| Paid tier | Same switch, no plan condition stated |
| User toggle | Yes, in settings |
| Machine-readable marking | Not documented |
Inclusion rule. Fields are the same four for every generator on this site; a field the vendor does not publish is recorded as not documented rather than inferred from how the product behaves. Order. Fixed field order, identical on every generator page.
1What the guide states
The statement sits inside a checklist written for people publishing AI drama, and it is short: the visible watermark on composited episodes is controlled by a setting, and it is on by default. Two things follow from the wording. The mark is applied at compositing, the stage where separate generated segments become an episode, so it lands on the deliverable rather than on each intermediate clip. And the control is described as a switch in settings, with no plan named beside it.
The guide gives a reason for switching it off that has nothing to do with price: if the publishing platform adds its own label, two labels end up on the same frame. That is a practical argument rather than a feature gate, and it is the only condition the page attaches to the switch.
2What is not documented
Nothing on the public pages enumerates what is written into the file itself. The guide tells publishers to keep whatever content credentials or generation metadata the tool writes, and warns that re-encoding through an editor can strip that layer, which implies something is written; but the fields are not listed and no standard is named. Until that is published, the machine-readable field here says so rather than guessing.
The same guide is where the publisher-side duty is set out, and it treats the visible notice as the evidence that survives when metadata does not. That distinction is worth carrying into the rest of this site, because most vendors document only one of the two layers.
3The same field, across every generator
| Generator | Free tier |
|---|---|
| Kling AI | Brand watermark on output |
| LTX Studio | No watermark-free output listed |
| Pika | No watermark-free download |
| Runway | No watermark-free output listed |
| SceneMixer | Visible watermark, on by default |
Inclusion rule. Generators whose public pages state whether output carries a mark. A generator silent on this particular field keeps its row, marked hollow. Order. Alphabetical by generator name.
| Generator | Paid tier |
|---|---|
| Kling AI | Removal from Standard ($10/mo) |
| LTX Studio | No watermarking from Lite ($15/mo) |
| Pika | Watermark-free from $28 Pro |
| Runway | Watermark-free on paid plans |
| SceneMixer | Same switch, no plan condition stated |
Inclusion rule. Generators whose public pages state whether output carries a mark. A generator silent on this particular field keeps its row, marked hollow. Order. Alphabetical by generator name.
| Generator | User toggle |
|---|---|
| Kling AI | Plan benefit, not a setting |
| LTX Studio | Plan benefit, not a setting |
| Pika | Plan benefit, not a setting |
| Runway | Plan benefit, not a setting |
| SceneMixer | Yes, in settings |
Inclusion rule. Generators whose public pages state whether output carries a mark. A generator silent on this particular field keeps its row, marked hollow. Order. Alphabetical by generator name.
| Generator | Machine-readable marking |
|---|---|
| Kling AI | Not documented |
| LTX Studio | Not documented |
| Pika | Not documented |
| Runway | Not documented |
| SceneMixer | Not documented |
Inclusion rule. Generators whose public pages state whether output carries a mark. A generator silent on this particular field keeps its row, marked hollow. Order. Alphabetical by generator name.
4Sources
Every line above is read from the compliance guide published at scenemixer.com, checked 2026-09-12. The same four fields for every generator are on the support table.
- Visible markA visible watermark is applied to composited episodes and is on by defaultstated in the vendor's own guide
- 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
- Machine-readable markingNot documented on the vendor's public pages (as of 2026-09-12)no field list published