C2PA Image Signer - ComfyUI Custom Node

What is This?

This is a tool that lets you digitally sign your images to prove you created them. Think of it like putting an invisible, tamper-proof seal on your artwork that says "I made this."

When you sign an image with C2PA:

✅ People can verify you created it (authenticity)
✅ People can see when it was created (timestamp)
✅ The signature breaks if someone modifies the image (integrity)
✅ You can add information about how it was made (metadata)

This is especially useful for AI-generated art, photography, and any digital content where proving authorship matters.

🚀 Quick Start

New to all this? Don't worry! Start with these guides in order:

📖 QUICK_START.md - Get it working in 5 minutes (step-by-step)
📚 SETUP_GUIDE.md - Understand what you're doing (beginner-friendly)
💡 EXAMPLES.md - See real-world examples

What This Tool Does

Simple Version

You put an image into this node in ComfyUI, and it comes out with an invisible digital signature embedded in the file. Anyone can check this signature to verify you created it.

The Features

✅ Signs images with C2PA certificates (industry standard for digital content)
✅ Works directly in your ComfyUI workflows
✅ Add custom information (who made it, what tools were used, etc.)
✅ Includes test certificates so you can start immediately
✅ Automatically saves signed images (no extra steps needed)

What's Included

When you downloaded this custom node, you got everything you need to start testing:

Test Certificates (Ready to Use!)

Think of certificates like a digital ID card. The node comes with official test certificates from the c2patool project:

📄 Private Key: keys/es256_private.key
- This is like your password - keep it secret!
- Used to create the signature
- Never share this file
📄 Certificate: keys/es256_certs.pem
- This is like your public ID - it's safe to share
- Contains your "public key" that others use to verify your signature
- Gets embedded in signed images

⚠️ Important: These test certificates are perfect for learning and testing, but if you're releasing images publicly or professionally, you'll want to get a "real" certificate from a trusted organization (more on that later).

Why Two Files?

Think of it like this:

Private key = Your pen (only you can sign with it)
Certificate = Your signature sample (others compare to verify it's really yours)

Someone can have your signature sample (certificate) and verify your autograph, but they can't forge your signature without your actual pen (private key).

What You Need First

Installing c2patool

This is a helper program that does the actual signing. Think of it like installing a printer driver before you can print.

For Windows (Easiest Way):

Download the tool:
- Go to: https://github.com/contentauth/c2pa-rs/releases
- Find the latest version
- Download the file that says "windows" in the name (like c2patool-v0.23.4-x86_64-pc-windows-msvc.zip)
Extract it:
- Right-click the downloaded ZIP → Extract All
- Put it somewhere you'll remember (like C:\Tools\c2patool)
Make it accessible:
- This part lets Windows find the tool from anywhere
- See the SETUP_GUIDE.md for detailed instructions
- Basically: Add the folder to your "PATH" (Windows settings)
Test it worked:
- Open Command Prompt (search for "cmd" in Windows)
- Type: c2patool --version
- If you see a version number, you're good! ✅

📖 Need more help? Check SETUP_GUIDE.md for step-by-step instructions with screenshots.

How to Use It

This custom node package includes two nodes:

C2PA Image Signer - Signs images with C2PA manifests
C2PA Verifier - Reads and displays C2PA manifests from signed images

Signing Images: The Simple Workflow

In ComfyUI, your workflow looks like this:

[Load Image] → [C2PA Image Signer]

That's it! The C2PA Image Signer automatically saves the signed image for you.

Important: Don't add a "Save Image" node after the C2PA Signer. If you do, the signature will be stripped out because ComfyUI re-processes the image. The signer already saves the file for you.

What to Put in the Node

The node needs these settings:

image (connect to it)
- This is your image from Load Image or any other node
private_key_path (type it in)
- The full path to your private key
- Example: <ComfyUI_path>/custom_nodes/c2pa_signer/keys/es256_private.key
- ⚠️ Use forward slashes / not backslashes \
cert_path (type it in)
- The full path to your certificate
- Example: <ComfyUI_path>/custom_nodes/c2pa_signer/keys/es256_certs.pem
- ⚠️ Use forward slashes / not backslashes \
filename_prefix (optional)
- What to name your signed images
- Default: "C2PA_signed"
- Result: C2PA_signed_20251006_094628.png
manifest_json (optional, advanced)
- Extra information to embed in the signature
- Start with just {} (empty)
- See examples below for what you can add

Where Do Signed Images Go?

After you run the workflow, check:

<ComfyUI_path>/output/

Look for files named like: C2PA_signed_20251006_094628.png

The signature is invisible - the image looks the same, but the file is slightly larger because it contains the signature data.

Signing Multiple Images at Once (Batch Signing)

Good news! The C2PA Image Signer automatically handles multiple images. If you connect multiple images to it, it will sign each one individually.

How It Works

When you sign multiple images at once:

Each image gets signed separately with its own C2PA manifest
Each signed image is saved as a separate file
The console shows progress as each image is signed

Setting Up a Batch Workflow

Option 1: Using the Batch Images Node

This is the easiest way to sign multiple images:

[Load Image] ──┐
               ├─→ [Batch Images] → [C2PA Image Signer]
[Load Image] ──┘

Steps:

Add 2 or more Load Image nodes
Load different images in each one
Add a Batch Images node
Connect all the Load Image nodes to the Batch Images node
Connect Batch Images to your C2PA Image Signer
Run the workflow!

Option 2: For More Than 2 Images

The standard Batch Images node in ComfyUI usually supports 2 images. To batch more:

[Load Image] ──┐
               ├─→ [Batch Images] ──┐
[Load Image] ──┘                    ├─→ [Batch Images] → [C2PA Image Signer]
                                    │
[Load Image] ───────────────────────┘

Connect the first Batch Images node to a second one, and add another image to the second node. This way you can combine 3+ images.

What You'll See

When signing multiple images, the console output shows progress:

For 3 images:

🔏 C2PA Batch Signing: Processing 3 image(s)...
✅ C2PA signing successful [1/3]
💾 Saved: C:/Users/.../output/C2PA_signed_20251006_123456_batch000.png
✅ C2PA signing successful [2/3]
💾 Saved: C:/Users/.../output/C2PA_signed_20251006_123456_batch001.png
✅ C2PA signing successful [3/3]
💾 Saved: C:/Users/.../output/C2PA_signed_20251006_123456_batch002.png
🎉 Batch signing complete! Signed 3 image(s)

File Naming

Single image:

C2PA_signed_20251006_123456.png

Multiple images:

C2PA_signed_20251006_123456_batch000.png
C2PA_signed_20251006_123456_batch001.png
C2PA_signed_20251006_123456_batch002.png

The batch000, batch001, etc. helps you keep track of which signed file came from which input image.

Why batch signing is useful:

Save time when signing lots of images
All images get the same signature settings
Perfect for signing a collection or series of images at once

Embedding Your Workflow in Signatures (Optional)

What is this? You can include your entire ComfyUI workflow inside the signature. This means anyone who verifies the signed image can see exactly how you created it - which nodes you used, what settings you applied, everything!

Why would you want this?

Full transparency - Prove exactly how the image was made
Reproducibility - Others can recreate your work
AI art attribution - Show which AI models and prompts you used
Learning - Share your workflow with others

How to Embed Workflow Metadata

The C2PA Image Signer has two new optional fields for this:

workflow_json - Paste your exported workflow here
include_workflow_metadata - Set to "enable" to turn this feature on

Step-by-Step Guide

Step 1: Export Your Workflow

In ComfyUI, create your workflow as normal
Click the gear icon (⚙️) or settings menu
Click "Save (API Format)" or "Export"
This saves a JSON file with your complete workflow

Step 2: Copy the Workflow JSON

Open the saved JSON file in Notepad or any text editor
Select all the text (Ctrl+A)
Copy it (Ctrl+C)

Step 3: Paste into C2PA Signer Node

In your ComfyUI workflow, find the C2PA Image Signer node
Find the workflow_json field (it's a big text box)
Paste your copied workflow JSON (Ctrl+V)
Set include_workflow_metadata dropdown to "enable"
Run your workflow!

What You'll See

When workflow metadata embedding is enabled, the console will show:

✨ ComfyUI workflow metadata will be embedded in signature
✅ C2PA signing successful
💾 Saved: C:/Users/.../output/C2PA_signed_20251006_123456.png

That ✨ tells you the workflow was successfully embedded!

Verifying Workflow Metadata

When you use the C2PA Verifier on a signed image with workflow metadata, you'll see:

✅ C2PA Manifest Found
🔒 Signature: Valid
📋 Assertions: 2
  • stds.schema-org.CreativeWork
  • com.comfyui.workflow

The com.comfyui.workflow assertion contains your full workflow! You can view it in the full manifest JSON output.

Important Notes

Privacy Warning: Your workflow JSON may contain:

File paths from your computer
Model names and locations
Node settings and parameters
Prompt text (including any sensitive info you typed)

If you're signing images publicly, review your workflow JSON first and remove any private information you don't want to share.

When to Use This:

✅ Sharing AI art with full attribution
✅ Professional work requiring provenance
✅ Educational content showing your process
✅ Open-source creative projects

When NOT to Use This:

❌ Private work with sensitive paths/prompts
❌ Commercial work with proprietary techniques
❌ When you want to keep your process secret

If you don't need it: Just leave include_workflow_metadata set to "disable" (the default). Your images will still be signed normally, just without the workflow data embedded.

Verifying Signed Images: Using the C2PA Verifier

The C2PA Verifier node lets you read and display C2PA manifests from signed images directly in ComfyUI.

Important: C2PA signatures are stored in the file's metadata, not in the image pixels. When images flow through ComfyUI as tensors, they lose this metadata. Therefore, to verify a signed image, you need to provide the file path to the actual signed file on disk.

How to Use the C2PA Verifier

Your verification workflow looks like this:

[Load Image] → [C2PA Verifier] → [Preview Any or Show Text]

The Node Inputs:

image (required, connect from Load Image)
- This is for ComfyUI workflow compatibility
- The verifier needs a tensor input, but won't use it for verification
file_path (optional, but required for actual verification)
- The full path to a signed image file on disk
- Example: C:/Users/YourName/Documents/ComfyUI/output/C2PA_signed_20251006_094628.png
- ⚠️ Use forward slashes / not backslashes \

The Node Outputs:

manifest_json - Full C2PA manifest as JSON (technical details)
summary - Human-readable summary showing:
- ✅ Whether a manifest was found
- 🔒 Signature validation status
- 👤 Issuer/creator information
- 📋 List of assertions (metadata)
image - Passthrough of input image for workflow chaining

Example Workflow: Sign and Verify

Sign an image:
```
[Load Image] → [C2PA Image Signer]
```
Run this workflow and note the output path shown in the console
Verify the signed image:
```
[Load Image] → [C2PA Verifier] → [Preview Any]
```
- In the C2PA Verifier node, paste the full file path to your signed image
- Connect the output to Preview Any or Show Text to see the verification results
- You should see "✅ C2PA Manifest Found" with signature details

What You'll See

If verification succeeds:

✅ C2PA Manifest Found
🔒 Signature: Valid
👤 Issuer: C2PA Test Signing Cert
🔐 Algorithm: es256
📋 Assertions: 1
  • stds.schema-org.CreativeWork

If you forget to enter the file_path:

❌ No C2PA manifest found

This is expected! Image tensors don't include file metadata.

📝 To verify a signed image:
1. Sign an image (check the output folder for the saved file)
2. Enter the full path to that file in the 'file_path' field above

Example: C:/Users/YourName/Documents/ComfyUI/output/C2PA_signed_20251006_094628.png

Why can't the verifier read from the tensor?

C2PA signatures are stored in the image file's metadata, not in the pixel data. When an image flows through ComfyUI, only the pixel values (the tensor) are passed along - the file metadata is left behind. This is why you need to provide the file path to the actual signed file on disk.

Adding Information to Your Signatures (Optional)

You can embed extra information in your signatures using the manifest_json field. This is optional but powerful!

Example 1: Add Your Name

Paste this into the manifest_json field:

{
  "assertions": [
    {
      "label": "stds.schema-org.CreativeWork",
      "data": {
        "@context": "https://schema.org",
        "@type": "CreativeWork",
        "author": [
          {
            "@type": "Person",
            "name": "Your Name Here"
          }
        ]
      }
    }
  ]
}

This embeds your name as the creator. Anyone who verifies the signature will see this.

Example 2: Add AI Generation Info

If you're making AI art, add this info:

{
  "assertions": [
    {
      "label": "com.example.ai-art",
      "data": {
        "model": "Stable Diffusion",
        "prompt": "A beautiful sunset over mountains",
        "workflow": "ComfyUI",
        "created_date": "2025-10-06"
      }
    }
  ]
}

What Are "Assertions"?

Assertions are just pieces of information you're "asserting" (claiming) about the image. Think of them like adding tags or notes that get sealed with your signature.

Common things to include:

Who created it (your name)
When it was created
What tools/software were used
If it's AI-generated or photographed
Copyright information
Licensing details

Checking If It Worked

After signing an image, you can verify it contains a signature in two ways:

Option 1: Using the C2PA Verifier Node (Easiest!)

Use the C2PA Verifier node in ComfyUI:

Add the C2PA Verifier node to your workflow
Paste the full path to your signed image in the file_path field
Connect to Preview Any or Show Text
Run the workflow
You should see "✅ C2PA Manifest Found" with signature details

See the Verifying Signed Images section above for detailed instructions.

Option 2: Using Command Line

Open Command Prompt

Type:

c2patool "<ComfyUI_path>/output/C2PA_signed_20251006_094628.png"

(Use your actual filename)

You should see a bunch of information about the signature, including:
- ✅ "validation_state": "Valid" (the signature is good!)
- Your certificate information
- Any assertions you added

If you see "validation_state": "Valid", congratulations! Your image is signed and verified! 🎉

Common Questions & Problems

"c2patool not found"

What it means: Windows can't find the c2patool program.

How to fix:

Make sure you extracted c2patool to a folder
Make sure you added that folder to your Windows PATH
Restart ComfyUI after changing PATH
Test by typing c2patool --version in Command Prompt

"Invalid manifest JSON"

What it means: There's a typo in your manifest_json field.

How to fix:

Check for missing commas or brackets
Use a JSON checker: https://jsonlint.com/
Start simple with just {} and add things one at a time

"Failed to read private key" or "Failed to read certificate"

What it means: The file paths are wrong.

How to fix:

Make sure you use forward slashes: C:/Users/...
Don't use backslashes: C:\Users\... (this won't work)
Copy-paste the full path to avoid typos
Make sure the files actually exist in that location

Why can't I use SaveImage after the C2PA Signer?

The Problem: When you run an image through SaveImage, ComfyUI re-processes it and strips out the C2PA signature.

Why: SaveImage converts the image back to pixels and re-saves it, which loses all the extra signature data.

The Solution: The C2PA Signer already saves the file for you! You don't need SaveImage.

The image looks the same - did it work?

Yes! The signature is invisible. The image looks identical to humans.

The signature is stored in the file's metadata (invisible data), not in the pixels you see. The file will be slightly larger (a few KB) because of this extra data.

To verify it worked, use: c2patool your-image.png

What "Test Certificates" Mean

The certificates included with this node are official test certificates from the c2patool project. Here's what that means:

For Testing/Learning:

✅ Perfect for experimenting
✅ Works completely
✅ Signatures verify as valid
✅ Free to use

Limitations:

⚠️ Everyone has these same certificates
⚠️ Not unique to you
⚠️ Won't prove YOU specifically made something
⚠️ Not accepted for professional/commercial use

Think of it like using a practice signature vs. your real signature on legal documents.

When Do I Need "Real" Certificates?

You need real certificates if:

You're releasing images publicly
You want to prove YOU made them (not just "someone")
You're doing commercial or professional work
You need legal authenticity

How to get them: You'd get a certificate from a "Certificate Authority" (an organization that verifies identities). This is beyond the scope of testing, but when you're ready, look into:

Professional certificate providers
Industry-specific certificate authorities
Enterprise solutions from C2PA members

For now, the test certificates are perfect for learning!

Learn More

Want to understand C2PA better? Check out:

C2PA Official Site: https://c2pa.org/
c2patool Documentation: https://github.com/contentauth/c2pa-rs/tree/main/cli
Technical Specification: https://c2pa.org/specifications/ (if you're curious!)

Need Help?

Read SETUP_GUIDE.md for detailed explanations
Check EXAMPLES.md for workflow examples
Review the troubleshooting section above

License

This custom node is free to use. The c2patool program is created by the Content Authenticity Initiative and is licensed under Apache License 2.0 / MIT.

Name		Name	Last commit message	Last commit date
Latest commit History 11 Commits
.gitignore		.gitignore
EXAMPLES.md		EXAMPLES.md
LICENSE		LICENSE
QUICK_START.md		QUICK_START.md
README.md		README.md
SETUP_GUIDE.md		SETUP_GUIDE.md
__init__.py		__init__.py
c2pa_node.py		c2pa_node.py
c2pa_verifier.py		c2pa_verifier.py

License

mikecaronna/comfyui_c2pa_signer

Folders and files

Latest commit

History

Repository files navigation

C2PA Image Signer - ComfyUI Custom Node

What is This?

🚀 Quick Start

What This Tool Does

Simple Version

The Features

What's Included

Test Certificates (Ready to Use!)

Why Two Files?

What You Need First

Installing c2patool

How to Use It

Signing Images: The Simple Workflow

What to Put in the Node

Where Do Signed Images Go?

Signing Multiple Images at Once (Batch Signing)

How It Works

Setting Up a Batch Workflow

What You'll See

File Naming

Embedding Your Workflow in Signatures (Optional)

How to Embed Workflow Metadata

Step-by-Step Guide

What You'll See

Verifying Workflow Metadata

Important Notes

Verifying Signed Images: Using the C2PA Verifier

How to Use the C2PA Verifier

Example Workflow: Sign and Verify

What You'll See

Adding Information to Your Signatures (Optional)

Example 1: Add Your Name

Example 2: Add AI Generation Info

What Are "Assertions"?

Checking If It Worked

Option 1: Using the C2PA Verifier Node (Easiest!)

Option 2: Using Command Line

Common Questions & Problems

"c2patool not found"

"Invalid manifest JSON"

"Failed to read private key" or "Failed to read certificate"

Why can't I use SaveImage after the C2PA Signer?

The image looks the same - did it work?

What "Test Certificates" Mean

When Do I Need "Real" Certificates?

Learn More

Need Help?

License

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Contributors 2

Uh oh!

Languages

Packages