What the ownership column is mostly made of
Nine of the seventeen vendors publish nothing about ownership on the pages read. The eight that do split into four shapes: a flat disclaimer, a conditional one, a grant of ownership, and a narrower statement about publishing. As of 2026-09-12.
| Shape of the statement | What it does | Example wording read here |
|---|---|---|
| A flat disclaimer | Removes the vendor as a claimant | No ownership claimed of inputs or outputs |
| A disclaimer inside a licence | The same, in the binding document | No rights claimed in the Outputs you generate |
| A grant of ownership | A stronger form of words, hedged by law | You own any outputs, to the extent the law permits |
| A narrower statement | Answers whether a file may go out | Publishing rights are owned by the user |
Inclusion rule. Shapes taken by published ownership statements in this register. A vendor silent on ownership is counted in the total and not given a row here. Order. From the broadest form of words to the narrowest.
1Silence is this column's normal state
More rows are empty than filled, which means a blank here is not a finding about a particular vendor. It is a description of an industry that answers licence questions on plan pages and leaves title to somebody else.
That is why no page in this register argues that a given vendor is unusual for saying nothing about ownership. The unusual rows are the ones that say something, and there are eight of them.
2A disclaimer and a grant reach the same place
If a vendor is not claiming the work, the practical position is the same whether the document phrases that as declining a claim or as granting ownership. Both leave the underlying question to copyright law.
The difference shows up in a negotiation. A grant is easier to quote to a client; a disclaimer is easier to defend, because it promises only something the vendor actually controls.
3Why one vendor uses a narrower word
A product that bundles licensed stock cannot honestly promise title to a finished export, because some of what is in it was never the customer's. Publishing rights describes what travels with the file.
Read that way the narrow wording is a signal about the product rather than a weakness in the drafting, and it is the shape a client contract asking for assignment will collide with first.
- What is ownedHiggsfield does not claim ownership of your inputs or outputsstated plainly
- What is ownedTencent claims no rights in Outputs you generate, and you and your users are solely responsible for Outputs and their subsequent usesstated in the licence itself
- What is ownedThe repository claims no rights over your generated contents, granting you the freedom to use them provided your usage complies with the licencestated in the same sentence as the licence
- What is ownedYou own any outputs generated from the Models or Derivative Works to the extent permitted by applicable lawstated in the licence
- What is ownedPublishing rights are owned by the user of the content, and Fliki does not own any contentstated as publishing rights
4A generator's account of it
Alongside the terms behind “Ownership silence”, SceneMixer's guides describe the work itself this way:
The terms grant you the output to the extent the law allows, and that includes commercial use.
SceneMixer, What You Get to Keep — “Do I own the copyright in what I generate?” (read 2026-10-13)
You can recomposite with different end-card text, and in step-by-step mode you can reshoot individual segments. The finished file can also be downloaded and shared with a link.
SceneMixer, How to Make an Ad from One Photo — “Can I change the ad after it is finished?” (read 2026-10-13)
5Sources
Each row quotes a plan card or a terms page, gathered on commercial use and read 2026-09-12. The test a sentence has to pass before it counts as a licence statement is set out on the reading page. Nothing here is legal advice. Nearby: Marks, not licences, Where the grid stops, Named platforms.