> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mediamonster.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Credentials

> What the Vault reads from a file's C2PA manifest, how AI skills label what they make, and which steps keep a file's history.

Content Credentials are the C2PA standard's signed history of a file. The history says who made the file, with what tool, what was done to it, and what it was made from. Cameras, Adobe apps and several AI image services write them. Mediamonster reads them when a file enters the Vault, and writes a label on what its own AI skills make.

## What the Vault shows

When you upload a picture, video or recording, the Vault checks it for a C2PA manifest and for an IPTC `DigitalSourceType` in its XMP. If it finds either, the file's page shows a **Content Credentials** row under **File**:

| Row | What it tells you |
| - | - |
| **Says** | One line: **Made with AI**, **Edited with AI**, **Content Credentials**, or **Content Credentials don't match** |
| **AI** | Whether a model made the whole file or parts of it |
| **Read from** | Where that came from: the signed manifest, the file's XMP, or the skill that made it |
| **Signature** | **Signature intact**, **Changed since it was signed**, or **Present, not checked** |
| **Signed by** / **Issued by** | The signing certificate and who issued it |
| **Made with** | The app that wrote the manifest |
| **Steps** | What the manifest says was done, in order |
| **History** | How many signed steps the file's history holds |
| **Problems** | What the check found wrong, when the signature doesn't hold |

**Signature intact** means the signature and every hash in the manifest match the file. The Vault doesn't check the signer against the C2PA trust list. A verifier that does, such as [contentcredentials.org/verify](https://contentcredentials.org/verify), can show the same signer as unknown.

The Vault checks files up to 40 MB in full. For a larger file it records that a manifest is there and shows **Present, not checked**.

## Deliveries and share links

A file with Content Credentials shows a small **CR** mark on its [delivery](https://docs.mediamonster.app/galleries.md) tile and its share page. Hover it to read the one-line summary.

The mark describes the original file. Tiles and previews are resized copies, and a resized copy has no manifest. People who download the original from a share link, or from a delivery set to full-size downloads, get the manifest with it. A delivery set to web-size downloads hands out a resized copy, which has no manifest.

## AI labels on skill results

A skill that makes or redraws media with a model labels what it makes. That covers the generators, and skills such as **Swap background**, **Monster restyle**, **Object remove**, **Sky replacement**, **Animate a photo** and **Lip-sync**. There are two labels:

* **Made by an AI model** (`trainedAlgorithmicMedia`): the model made the whole file, even when it worked from your photo.
* **Includes parts made by an AI model** (`compositeWithTrainedAlgorithmicMedia`): your file, with part of it redrawn by a model.

Skills that run a model without adding anything new to the picture aren't labelled. Examples are cut-outs, upscales and noise removal.

What goes into the file depends on its type:

| Result | What is written |
| - | - |
| JPEG or PNG picture | IPTC `DigitalSourceType` in the file's XMP. With a signing certificate set up, also a signed C2PA manifest |
| Other pictures (WebP and others) | A signed C2PA manifest when a certificate is set up. Otherwise the label is on the Vault record only |
| Video and audio | The Vault record only. The file isn't changed |

The XMP label is what stock libraries, content management systems and search engines read. Anyone can remove or edit it. A signed C2PA manifest is tamper-evident: if the file changes, the signature no longer matches.

When a later skill has no model, such as **Add watermark**, it keeps the AI label from the step above.

> [!NOTE]
>
> Signing needs Mediamonster's C2PA signing certificate. Where it isn't in place, AI pictures carry the unsigned XMP label only, and the Vault record says **XMP label (unsigned)**.

## Which steps keep a file's history

Most processing drops Content Credentials. Converting, resizing and every provider we send a file to write a new file without the manifest. This is what happens to a credentialed file:

| Path | Keeps the manifest |
| - | - |
| Stored in the Vault, share link, full-size delivery download | Yes. The bytes aren't changed |
| CDN links and delivery previews | No. They are resized copies |
| A picture skill, with a signing certificate set up | Yes, for originals up to 40 MB. The new file's manifest includes the original's history |
| A picture skill without a signing certificate | No. The Vault record's **Made from** row says the history wasn't carried over |
| Video and audio skills | No. The Vault record's **Made from** row says the history wasn't carried over |
| Convert and resize steps on the Workbench | No. They also drop an AI label that a step above wrote into the file |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.