Microsoft Designer on the site where the metadata is read
The page does not describe a detector; it names a place to go. For a reader that is the same thing as a public route, and it is the shortest possible answer to who can check this. As of 2026-09-22.
| Point | What the record holds |
|---|---|
| Reading route | The Content Credentials site, named on the support page |
| Read from | A support FAQ, answering a customer's own question |
| What it does not settle | What a messaging app's recompression leaves behind |
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.
1Naming a destination is a small act with a large effect
Most provenance claims leave the reader to work out how to verify them. A named site turns the claim into something a person can attempt in a minute, which is the difference between a stated property and a usable one.
It also fixes the standard by implication. Only a specification with public readers has a site like that, so the sentence carries interoperability without arguing for it.
2Still images are the worst-treated assets on the internet
Pictures pass through more automatic rewriting than any other file type. Messaging apps recompress, content systems build derivatives, and every one of those steps rebuilds a container without any obligation to copy what was in it.
A manifest that arrives with an original often does not arrive with the copy an audience sees. That is a fact about routes rather than about this product, and it makes the reading route worth checking on the route rather than on the export.
3A help page is an unusual place for an interoperability claim
The sentence exists because customers asked where the metadata went, not because a duty required an answer. Support prose has the useful habit of describing what a user will actually find.
Read against the clause, that habit is worth more than a policy statement. A reader can follow the instruction and see for themselves, which no marketing sentence in this record permits.
- Microsoft DesignerProvenance metadata can be viewed on the Content Credentials sitethe route a viewer uses to read it
- Article 50(2)Technical solutions must be effective, interoperable, robust and reliable as far as technically feasiblequalifier on the marking duty
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 Reading route. Filed beside it: Firefly on a coalition of readers, AudioSeal on detection granularity.