DocumentationAEMUser Guide

[AEM Assets]{class="badge positive" title="Applies to AEM Assets)."}

C2PA metadata in Dynamic Media C2PA-metadata-dynamic-media

Last update: August 26, 2026
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • User

Brands are more concerned than ever about content transparency, AI disclosure, and preventing the tampering of assets. The Content Authenticity Initiative (CAI) at Adobe builds tools compliant with the Coalition for Content Provenance and Authenticity (C2PA) technical standard. User-Generated Content (UGC) consists of uploading assets to a dedicated Adobe Dynamic Media Classic storage repository and performing related operations. Dynamic Media User-Generated Content (UGC) also follows the C2PA specification. Using C2PA metadata, assets which are generated through AI are digitally signed using the C2PA specification. These signatures embed secure metadata within the asset, enabling users and systems to verify the content’s origin and history. The metadata can provide information such as:

  1. The software or service used to create the image.
  2. Whether generative AI was involved in the image creation process.
  3. Edits or modifications made to the image, such as modification in height or width after it was generated.
  4. The provenance and authenticity of the content.

Thus C2PA metadata, which is a new kind of tamper-evident metadata can help viewers understand the lineage of content and ensure the integrity of brand assets.

Prerequisites of Assets using C2PA metadata in Dynamic Media prerequisites-of-assets-using-C2PA-metadata

Ensure that you fulfil the following requirements before using C2PA metadata:

  1. Only eligible assets that have been created through GenAI such as Adobe’s Firefly are supported, non-GenAI assets are not eligible for C2PA metadata preservation. An asset is considered eligible in the following conditions:

    1. The source brand asset is identified as a content generated using GenAI.
    2. The source brand asset contains valid C2PA metadata.

  2. Dynamic Media does not preserve C2PA metadata for assets that do not already contain them.

  3. For image or document assets, C2PA metadata is supported for .jpeg, .png, .gif, .tiff, .dng, .arw, and .nef file formats. For video assets, C2PA metadata is supported for .mp4, .avi, .mov, .m4v file formats.

  4. C2PA metadata preservation is supported only for asset download or export workflows. This includes exports from Adobe Experience Manager (AEM) or Adobe Dynamic Media Classic and delivery through the attachment modifier, which forces download by setting the Content-Disposition response header.

    note
    NOTE
    If C2PA metadata cannot be validated or processed, the asset can still be uploaded, processed, delivered, or exported normally, but the output does not include C2PA metadata.

Access C2PA metadata for Dynamic Media assets access-C2PA-metadata-for-dynamic-media-assets

  1. Upload an asset in the Dynamic Media environment.

  2. Open the asset and copy the URL.

  3. Paste the copied URL in any web browser. You can generate rendition by customizing the height and width of the asset.

  4. Download the asset. You can download eligible assets or renditions from Dynamic Media using the attachment (attachment=true) as a modifier. When the source asset is eligible, Dynamic Media preserves the C2PA metadata in the downloaded output.
    For more information on downloading the asset using the attachment as a modifier (attachment=true), see the Adobe Experience Manager API.

    note
    NOTE
    When you download a generated rendition, Dynamic Media creates a new output file. As this output is newly generated, Dynamic Media signs the rendition again using the original asset as a source ingredient to preserve the C2PA metadata chain and returns the generated file with C2PA metadata when the source asset is eligible. Similarly, for video assets, Dynamic Media signs each video encode with C2PA metadata, provided the source video is eligible.

  5. You can also export an asset from Dynamic Media.

    note
    NOTE
    For original exports, the original asset is returned with its existing C2PA metadata.

  6. Upload the downloaded asset in any C2PA software, for example, Adobe’s CAILens interface.
    You can now view the list of actions performed such as opening the asset, converting the asset’s type from .png to .avif, resizing the asset, and editing the asset.
    C2PA Manifest

Limitations limitations-C2PA-metadata

To maintain the integrity and authenticity of C2PA metadata, Dynamic Media enforces the following limitations:

  1. Source assets that are above the configured maximum file size of 2 GiB and above the processing timeout of 60 seconds are not processed for C2PA metadata preservation.
  2. Composite Assets are not supported during signing and only the base image is considered for signing. If the base image is generated through any GenAI tool, the output is signed accordingly. However, the signature does not include any information about the GenAI-generated layers that are used to create the final rendition.
  3. Adaptive video streaming files and video thumbnails are not signed. Also, there is no support for C2PA metadata preservation for Dynamic Media hybrid solution.
  4. C2PA metadata processing has a configured timeout.
    If any of these safeguards are reached, the asset continues through normal Dynamic Media processing, but C2PA metadata may not be preserved in the generated output.

See also

recommendation-more-help
experience-manager-cloud-service-help-main-toc