← All posts

The Archibal Team

ComfyUI has provenance gaps. Here is what the Archibal node records.

ComfyUI embeds its workflow JSON in every PNG so you can re-create the graph that made the image. That is useful for creative iteration. It is not the record clients and platforms now ask for. Here is what a single node at the end of your graph sends to Archibal, and what it does not do.

The Archibal Callback node wired into a ComfyUI workflow.

ComfyUI is one of the most powerful creative tools ever built. Four million users, 150,000 daily downloads, a $30 million round at a $500 million valuation, bringing its total funding to $47 million - what started as a single developer's Stable Diffusion experiment has become what its founders call "the OS of creative AI." Professional studios, freelance artists, and agency production teams use it to run Flux, SDXL, video generation, LoRA stacks, ControlNet, upscalers, and audio - all in a single graph.

If you use it for commercial output, the way it handles provenance is a gap your clients and the platforms you publish to will ask about - especially for work going into the EU market, where the AI Act's transparency rules have applied since August 2, 2026.

This post explains what the gap is, why it exists, and what a single Archibal node at the end of your ComfyUI graph records - without changing how you work.

What ComfyUI already does with metadata

ComfyUI does something genuinely useful out of the box: it embeds the full workflow JSON in the metadata of every PNG it saves. Drag any ComfyUI-generated image back into the canvas and it reconstructs the exact graph that made it - checkpoint, sampler, prompts, seeds, LoRAs, everything. That is excellent for creative iteration and for sharing workflows with the community.

It is a different thing from the documentation clients, platforms and regulators now ask for.

ComfyUI's embedded workflow JSON is designed for creative reproduction: "how do I regenerate this?" A client or a platform asks a different question: "what model made this, which version, on what terms, who reviewed it, and when?"

The gap between those two questions is what 2026 is exposing.

Why ComfyUI's built-in metadata falls short

There are three specific ways the default ComfyUI metadata falls short of what the EU AI Act's Article 50 and broader AI content transparency expectations point toward.

It is not machine-readable in any standardised format. ComfyUI's workflow data sits in a proprietary JSON blob inside the PNG's tEXt chunk. It is not in IPTC Photo Metadata 2025.1 format. It is not a C2PA manifest. Platforms and downstream systems that know how to read IPTC or C2PA fields cannot parse it. The EU AI Act's marking duty in Article 50(2) sits with the providers of AI systems, and the Code of Practice the European Commission is finalising points them toward multi-layer marking: embedded machine-readable metadata, watermarks, and fingerprints. A default ComfyUI install produces none of those.

It can be stripped accidentally or deliberately. Any image editor, social media upload, file format conversion, or CMS pipeline will silently strip the ComfyUI PNG metadata. Someone on Reddit noted this is a known enough problem that there is a --disable-metadata launch flag for creators who want to ship images without leaking their workflow. What protects a creator's IP in that context is exactly the opposite of what a production record needs. Embedded metadata of any kind - C2PA included - can be stripped, which is why a record kept outside the file matters.

It has no human review layer. ComfyUI captures what the machine did: checkpoint name, sampler steps, CFG scale, seed, prompt text, LoRA weights. It has no mechanism for recording what a human decided: who reviewed this output, when, whether they approved it for a specific market, and whether they hold editorial responsibility for its publication. The EU AI Act's Article 50(4) editorial exemption for AI-generated text specifically requires that a person hold editorial responsibility and that the review process is documentable. ComfyUI cannot help you with that. A spreadsheet probably cannot either, at production scale.

As a Numonic analysis of this exact problem put it: "The problem isn't discipline. It's architecture."

The C2PA landscape in 2026

Some context on where the provenance standard sits right now.

The major hosted AI generation platforms have converged on C2PA for output marking. Adobe Firefly has embedded C2PA credentials since launch in 2023 - it is the reference implementation. OpenAI added C2PA to DALL-E 3 in 2023 and to Sora video in 2024/2025. Google Imagen uses both C2PA and SynthID, its invisible pixel-level watermark, as complementary layers. Midjourney has not implemented C2PA as of early 2026 and has not announced a timeline.

Stable Diffusion - the model family that powers most serious ComfyUI workflows - is partial. Stability AI added C2PA to its hosted Stable Image platform. The open-source model weights carry no C2PA data. If you run SDXL, Flux, or any other checkpoint locally through ComfyUI, your output has no C2PA manifest unless something in the pipeline adds it. Nothing in the default ComfyUI installation does.

That is the gap: the most technically sophisticated local AI creative work - ComfyUI with open-source checkpoints - leaves the graph with no C2PA credentials and no record outside the file.

What the Archibal node does

The Archibal Callback node sits at the end of the graph, wired to the final image or video output, in your local ComfyUI. When you hit Queue, ComfyUI runs your workflow exactly as it always has. The Archibal node fires once at the end and sends the render to Archibal - no UI blocking, no workflow changes, no interruption to your generation process.

Here is what arrives with each render from a workflow the node sits in:

The final file. The generated output itself, stored in Archibal as part of your record.

The full workflow JSON. The complete graph, preserved for reproducibility and for showing what pipeline produced this output.

The models in the pipeline, with attribution. Archibal reads which checkpoint, CLIP, VAE, LoRAs, ControlNet models, and any API-connected models took part in this output, and records each one with its node.

The prompts and the seed. Read from the workflow as it ran.

Reference inputs. Up to ten input images (LoadImage nodes, ControlNet inputs, IP-Adapter references) are stored with the render as its references. Where a reference is a near-identical copy of a file already in Archibal, the two are linked.

Project routing. Each node connection files its renders into the project you choose for it on the Capture page, or into the workspace Inbox, where you move them into a project later. You can change a connection's project any time without a new URL. Work you run through Claude is filed the same way: Claude asks which project to use, and anything logged without one waits in the Inbox.

Evidence grade. When the received file itself carries its workflow - ComfyUI PNGs do - Archibal grades the render Attested, the strongest of its four grades: the file holds a re-checkable record of how it was made. When the workflow arrives only with the node's request and not inside the file - a video, for example - the render is graded Studio-logged: recorded by your own pipeline, not re-checkable from the file. The grade travels into the provenance record (PDF) and the public verify page.

What the node does not do: it does not write C2PA into your files. The render arrives as it left ComfyUI. Archibal computes its fingerprint, reads it like any upload, and keeps it in your library. C2PA signing happens later, when you deliver: the delivered files are signed and the record is frozen.

The result: you see the render in your project or Inbox with its thumbnail, model attribution, prompt, seed and full workflow. Over a project, that becomes a production record that holds up when a client, a platform or a regulator asks how the work was made.

Setup takes about two minutes

  1. Install the Archibal node from ComfyUI Manager - search "Archibal", click Install, restart.
  2. In Archibal, open the Capture page, connect "ComfyUI (Archibal node)" and copy the URL it gives you into the node's webhook_url field. Leave api_key empty - the URL carries its own token.
  3. Drop the node at the end of your workflow and connect your final image or video to it.

That is the entire setup. No workflow restructuring. No export step. You still hit Queue; the record builds as you render. Comfy Cloud work is captured through the Claude connector instead.

What this means now that Article 50 applies

The EU AI Act's transparency obligations have applied since August 2, 2026. The machine-readable marking duty in Article 50(2) binds the providers of AI systems, not the studio running a workflow - but clients and platforms can ask the studios in between how the work was made, and "the PNG has the workflow JSON in it" is not an answer they can file.

There is a structural point worth being direct about: renders made before the node is in your graph have no record from it. Archibal cannot reconstruct a capture that did not happen. The record starts when the node is in the graph, not when you decide you want one - though uploads still read whatever the file carries, including an embedded ComfyUI workflow.

The broader principle

ComfyUI is a generation tool. It is phenomenally good at it. Keeping a production record is a different job, and asking a generation tool to do both is the mistake most teams are making right now.

The right architecture is a clear division: ComfyUI runs the creative workflow, and a single callback node at the end of the graph hands each render to a system built for provenance - fingerprinting, model attribution, review, C2PA signing at delivery, and the provenance record. No friction in the creative process, and every render from a workflow with the node in it arrives with its record.

That is the integration Archibal and ComfyUI are designed to be.

Running ComfyUI for client work? See how Archibal fits a creator's or agency's pipeline.