Who is this for?

This is an introductory topic for developers who want to add and validate Coalition for Content Provenance and Authenticity (C2PA) Content Credentials on Arm devices.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Understand what C2PA is, the content provenance problem it addresses, and why provenance matters.
  • Add Content Credentials to a sample image on an Arm device.
  • Inspect the manifest and interpret content-binding, signature, and trust results.
  • Validate Content Credentials with an external validator.
  • Identify a content-binding failure after a controlled change to the image.

Prerequisites

Before starting, you'll need the following prerequisites:

  • The current stable release of C2PA Tool installed on your Arm device
  • An installation of ExifTool on your Arm device
  • An installation of libjpeg-turbo on your Arm device
  • Familiarity with running command-line tools

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll create and verify C2PA Content Credentials for a sample image on an Arm device. First, you’ll prepare an unsigned image and sign a separate copy with the C2PA Tool development credential. Then, you’ll inspect the manifest and distinguish signature, content-binding, and signer-trust results. You’ll compare the provenance of the image in the Content Authenticity Initiative (CAI) web validator. Finally, you’ll modify a copy and identify the resulting content-binding failure.
Next