Microsoft Designer on credentials for images from its editing features
The claim is tied to a named part of the product: images created with the editing features. A scope that narrow is more useful than a broad one, because a reader can tell which of their files it covers. As of 2026-09-22.
| Point | What the record holds |
|---|---|
| Article 50(2), machine-readable marking | C2PA content credentials on all images created with the editing features |
| Read from | A support FAQ, written to answer a customer's question |
| What it does not settle | What anything outside those features produces |
Inclusion rule. One cell of this generator's entry, quoted from the page the entry names. Coverage, commentary and third-hand summaries are not admitted, in either direction. Order. Fixed order: the cell, the page it came off, then the limit on reading it.
1A narrow claim beats a broad one for anybody keeping records
Broad wording is comfortable to write and hard to use. Told that a service applies provenance, a reader still has to guess whether that covers the template they started from, the stock element they dropped in, or the export they took away.
Naming the editing features removes the guess for those features and makes the boundary visible for everything else. That is the shape a register can record faithfully, and it is why this cell quotes the scope rather than summarising it.
2A support article is an odd place for a provenance commitment
The page was written because customers asked a question, not because a transparency obligation existed. That gives the sentence a particular character: it explains what a user will find in a file, in the register of a help desk, with no reference to any duty.
Read against a clause, help-desk prose has one advantage over marketing prose. It is written by people who will be held to it by the next ticket, which tends to make the scope clauses accurate.
3Images are the easy medium and the one most often re-encoded
Still images pass through more automatic rewriting than any other asset type. Messaging apps recompress them, content systems generate derivatives, and each of those steps rebuilds a container. A manifest that arrives with the original often does not arrive with the copy the audience sees.
That is a property of the route rather than of this product, and it is the reason the record keeps a separate row for who can read the mark. A credential nobody downstream preserves is a credential nobody downstream reads.
- Microsoft Designer (microsoft.com)Content credentials, provenance based on the C2PA standard, are applied to all images created with the editing featuresan image generation and editing tool
- Article 50(2)Providers must mark synthetic audio, image, video and text in a machine-readable formatincluding general-purpose AI systems
4Sources
Wording taken from the support FAQ at support.microsoft.com, consulted 2026-09-22. All four rows for this generator sit on Microsoft Designer; the same column across every entry is read down on What it asks for. Filed beside it: Wan on marking and open weights, SceneMixer on a mark at compositing.