Loading...
Loading...
One export reads the full record behind an asset, strips the workflow details your studio keeps private, and injects the disclosure clients, regulators, and insurers expect. Ship deliveries that hold up in audit, without handing over your craft.
A working asset carries everything that made it: prompts, seeds, sampler settings, the full workflow graph. That record is what makes your library searchable and reproducible, and it is also your studio's craft. A client deliverable needs the opposite: none of that, plus the AI disclosure a working file never had. Numonic reads the full record and produces the right file for where it is going, so you never choose between protecting your process and meeting your obligations.
Every export sorts metadata into three categories, so you can prove AI origin without revealing your prompts or workflows.
Removed on export when you share externally.
Kept so the file stays technically usable.
Injected so disclosure travels with the file.
Deliveries go out as a Numonic portal. Comments come back in context, approval state is tracked, and the deliverable carries the IPTC 2025.1 AI disclosure metadata Numonic writes on export. No more chasing feedback across email threads, and no more wondering whether the version a client signed off on is the one that shipped.
Category A metadata: prompts and negative prompts, seeds, sampler, scheduler and denoise settings, model and LoRA names, the full workflow JSON, and GPS or personal metadata. Technical fields like dimensions and color profile (Category B) are preserved so the file stays usable.
Category C disclosure metadata: the IPTC 2025.1 AI fields (AISystemUsed, AISystemVersionUsed, AIPromptInformation, and AIPromptWriterName), a digital source type, and creator attribution. Numonic also records the export itself as an event in the file XMP history, so the handoff is documented. C2PA manifests are detected on ingest, never written on export.
Images today: PNG, JPEG, and WebP carry the IPTC 2025.1 and XMP disclosure fields, and GLB is supported for 3D. Stripping covers PNG, JPEG, audio, and GLB. Video (MP4, MOV, WebM, and MKV) passes through unchanged for now, with video stripping and injection on the roadmap. C2PA detection covers PNG and JPEG today.
The three standard presets apply the same rules on every export, so a repeat delivery is one choice rather than a checklist. A Custom export lets you set the strip and keep rules for that send when a client or jurisdiction needs something different. Saved, named profiles that persist across deliveries are on the roadmap.
Strip what's private, inject what's required, and deliver with provenance built in.
Start freeNo credit card to begin