What Image Platform Terms Let You Do With Output

What you may do with a generated image is decided by six questions, and the answers live in predictable places in almost every platform’s terms. Learning where to look is durable; learning what one platform said in one particular month is not, because these documents are revised often and quietly.

Why this page names no platform

Two reasons, both practical. Terms of service for these products change frequently — commercial-use rules, ownership language and indemnity offers have all moved more than once across the industry — so a page that quoted current wording would be a page that became confidently wrong without changing a character.

And the cost of being wrong is asymmetric. A reader who acts on a stale latency figure loses an afternoon. A reader who ships a campaign on the strength of a stale licensing claim has a commercial exposure. So this page gives you the questions, which stay true, and sends you to the document, which does not.

The six questions

Question six carries the sting people miss. A prohibited-use breach is usually framed as terminating your rights under the agreement, which is a much larger event than the one image being disallowed — every asset you have shipped may sit on a licence that no longer exists.

Where each is answered

These agreements are structured similarly enough that you can navigate one you have never seen in about fifteen minutes.

• A definitions section distinguishes your inputs from the outputs, and often introduces a term such as “content” that covers both. Read it first: the rest of the document turns on which term is used in which clause, and a grant covering “content” is quite different from one covering “output”.
• A rights or ownership clause answers question one, usually in two sentences that need to be read together — one about what you get, one about what the provider retains.
• A licence-back grant, often in the same clause, gives the provider rights over what you generate. Check whether it is limited to operating the service or extends to promotion and training.
• An acceptable-use policy, almost always a separate document incorporated by reference, answers question six. It is revised more often than the main terms and typically without notice.
• A plans or billing page answers question two, and this is the one that most often contradicts a summary elsewhere on the site.
• A privacy or data policy answers question four.
• A separate commitment, often not in the terms at all, answers question five. If you cannot find one, the answer is that there is none.

Marketing pages are not terms. Where a summary on a product page and a clause in the agreement disagree, assume the agreement governs and ask the provider in writing.

One question sits outside all seven documents and is worth separating off now: whether the material a model was trained on was lawfully used is a dispute between rightsholders and providers rather than a term of your licence, and it is being litigated on its own track. An indemnity is the only place it usually touches you.

Rights granted and copyright are different questions

This is the most consequential confusion in the whole area. A platform can grant you every right it has. That does not create a copyright in the image, because whether the output attracts copyright at all is a question of law rather than of contract.

The practical consequence: even with the most generous possible terms, you may hold a strong contractual position against the platform and a weak position against a third party who copies the image, because preventing copying requires a right that exists in law. Jurisdictions differ sharply here, and the general shape is covered in the ownership half of the plagiarism page.

Three things follow. If exclusivity matters — a logo, a character, a brand asset you must be able to stop others using — generated output is a weak foundation, and the more human modification sits on top of it the better. If you are commissioning, say in the contract what the deliverable may contain and who warrants it. And if a client asks you to assign copyright in the work, know before you sign whether you have one to assign.

Indemnities and what voids them

Some providers offer to defend customers against certain third-party intellectual property claims arising from output. Where such an offer exists it is a genuine allocation of risk and worth having. It is also conditional, and the conditions are where the offer lives or dies.

The questions to put to any indemnity, whatever it covers:

1. Which tiers and which products does it apply to? Free and trial tiers are commonly excluded.
2. Does it survive if you modified the output? Many creative workflows modify by default.
3. Is it void if you disabled a safety feature, prompted for a named artist or living person, or supplied a copyrighted input image? Each of those is a common carve-out and each is a thing designers do routinely.
4. Does it cover defence costs, settlements and damages, or only defence? These are very different numbers.
5. Is there a cap, and how does it relate to what you spend?
6. What must you do to claim it — notice period, control of the defence, cooperation obligations? A missed notice deadline forfeits the whole thing.

The problem arrives downstream

Most people who get into difficulty here do not get there through the platform. They get there through their own client contract, which was signed first and says something the platform terms cannot support.

Standard agency and freelance contracts routinely include a warranty that the work is original and does not infringe, an assignment of all intellectual property in the deliverable, and an indemnity running from you to the client. Deliver generated material under that contract and you have personally warranted something you have not verified and assigned something you may not own.

The fix is a conversation before the work, not after: disclose that generated assets may be used, agree in writing what that means for the warranty and the assignment, and if the client needs exclusive ownership of a mark or a character, do not use generated output for it.

What to record, per image

None of the above is answerable later without records, and records cost nothing at the time.

asset:            hero-warehouse-03.png
generated:        2026-08-04
platform:         <name>
model / version:  <as shown in the interface>
plan tier:        <the tier active on the generation date>
prompt:           <the full prompt, verbatim>
input images:     <any image supplied, and its source and licence>
terms version:    <date of the terms in force, or a saved copy>
modifications:    <what a human changed afterwards, and who>
used in:          <where it was published>
disclosure:       <caption text used>

• The tier on the generation date is the field people wish they had. Rights usually attach at generation time, and a downgrade six months later makes the question unanswerable from memory.
• Input images and their licences. If you supplied a reference, the rights in that reference travel with the output and are a separate problem from the platform terms.
• A saved copy of the terms in force. A PDF costs nothing and is the only way to establish what you agreed to, since the live page will have moved on.
• Modifications and who made them. The human contribution is what strengthens your position, and it has to be evidenced rather than asserted.

The prompt field is the one people leave out and regret. It is the evidence of what was asked for, it is what makes the second image in a series match the first, and it is the artefact the brief was written to produce in the first place.