# Content Credentials on your files

> In short: Zymcos copies every generated file into your storage byte for byte, so any C2PA record (Content Credentials) the provider embedded stays intact, and it reads the copy to note what it carries. Nothing is added, altered or refused because of what it finds.

Applies to: v0.9 · Last reviewed: 2026-09-30 · Canonical: https://docs.zymcos.com/product/content-credentials/

Some image and video generators attach a record to the file they make, saying how it was made.
The standard for that record is **C2PA**, and the mark people see is often called **Content
Credentials**. Zymcos keeps such a record intact on every file it copies into your workspace, and
reads it when the copy is made, so that we know what the file carried. This page says what
happens, and what it does not mean.

## What happens to each copied file

When a take finishes, Zymcos copies the file from the model provider into its own storage. Two
separate things then happen, and the second can never harm the first.

1. **The file is copied exactly.** Byte for byte, with nothing in between that could remove or
   change a record the file carries. Whatever the provider embedded is still in your copy.
2. **The copy is checked for a record.** Zymcos reads the file to see whether it carries a C2PA
   manifest, and notes what it found on the file's record. This only reads. It never changes the
   file.

If the check finds nothing, cannot read the file, or fails outright, the copy is kept exactly the
same. A file is never refused, held back or altered because of what the check found.

## What the check can find

Each copied file ends up with one of these, and each says something different:

- **Verified.** The file carries a manifest, and it checks out.
- **No manifest.** Nothing was embedded. Many files from model providers carry none, so this is
  ordinary.
- **A manifest that did not validate.** One is there, but it failed its checks. The manifest is
  kept exactly as it came, and the reasons are noted.
- **Cannot carry one.** The kind of file has no place for a manifest, such as a text file
  or a JSON document.
- **Not checked.** The check could not run, or failed. This is different from *no manifest*: it
  means we did not look properly, not that there was nothing there.

## Where you see it

Today the result is recorded on the file but **not shown in the app**: there is no badge in the
Viewport or Files. What you can rely on is the copy itself. **Download**, in the bar under a
picture, saves the original with its manifest intact; see
[Your files](https://docs.zymcos.com/product/your-files/#downloading-the-original).

## What Zymcos does not do

- **It does not add a manifest to your files, sign them, or edit them.** Nothing is written into
  a take.
- **It does not vouch for a provider's claim.** A verified manifest says the record is intact and
  valid, not that Zymcos endorses what it says.
- **It does not treat a missing manifest as a warning.** Absence is common and says nothing about
  the file.

## The record filed when you circle a take

When you circle a take with a ★, Zymcos files a small text record (a JSON file) beside it in
Files. It lists the take's recipe, the files it was made from with what the check found for each, and the
steps that led to the ★. It is a separate file: it does not go inside the take, and it is not a
C2PA manifest itself.
