Capture One Export & Instagram C2PA
August 18, 2026
Recipes, not “the Capture One look”
Output
Keep tags?
Action
Print / archive TIFF or high-bit
Often yes (color, IPTC)
Do not overwrite with a strip
Social recipe JPG
No, for Meta upload
Strip this folder
Proofing JPEG for client gallery
Policy-dependent
Don’t mix with IG_Ready
PSD round-trip then C1
Stacked credentials
Clean last export
Tokens and subfolders ( Output/Web , Output/IG ) fail when the intern uploads Output/Web before strip, or uploads the proof JPEG Capture One generated for a session gallery.
C1 is not “safe because it isn’t Lightroom.” Inspect the recipe JPG .
A Process Recipe checkbox that drops EXIF/IPTC is not a C2PA off-switch. Content Credentials can still sit in a JUMBF block after “exclude metadata.” Spot-check one hero per recipe version after you change Tokens, sharpening, or an AI tool.
Clients who WeTransfer Output/Web the night of delivery often skip Social_Ready. Put the strip in the same job ticket as “export social recipe” - not a Slack reminder after they already posted.
Workflow (studio)
- Lock a Social process recipe (sRGB, quality, long edge). Separate from print.
- Process the selects into Output/Social_Uncleaned .
- Spot-check one hero in the AI metadata checker .
- Strip C2PA/XMP → Output/Social_Ready (batches of 30).
- Clients get Social_Ready for Instagram. Print stays in the print recipe.
- New recipe run after a Photoshop round-trip = new batch. Do not assume yesterday’s strip.
HEIC from tethered extras: convert then strip if those files sneak into the IG folder.
What this page does not cover
- Lightroom Denoise (sibling).
- DxO as last export (same idea; not this slug).
- Turning off Instagram AI Info in Settings.
When the Capture One social JPG is the attach file, strip C2PA/XMP, then finish on the Lightroom / photo upload hub . Same browser strip; Capture One is the editor. Prep only.
See Disclaimer .
Deliver Capture One social JPGs without leftover file tags
Process a social recipe, inspect one JPG, strip C2PA/XMP, post that folder.
- Process the social recipe - Export sRGB JPGs from Capture One at social long-edge - a recipe separate from print.
- Inspect one file - Run the AI metadata checker (/ai-metadata-checker) on a hero from that recipe batch, not a preview from the viewer.
- Strip C2PA and XMP - Batch-clean the social folder (up to 30 per session). Leave print/archive untouched.
- Post or deliver - Instagram from Social_Ready only. Client delivery: that folder, not the session RAW.
Frequently Asked Questions
Is Capture One the same as Lightroom AI Denoise?
No. The Lightroom article is Adobe Denoise/C2PA on LR exports. This page is Capture One recipe/process exports (Sessions or Catalog) before Instagram.
Lightroom’s FAQ already mentions Capture One. Why a separate page?
That FAQ is one sentence: same clean-before-upload idea. Here the path is C1-specific: recipes, Tokens, Process Recipe, and session folders.
Does every C1 export write C2PA?
No. Inspect your recipe output. AI tools, round-trips to Photoshop, or vendor credentials on some versions can still tag the JPG.
Print recipe vs social recipe?
Keep a print/archive recipe with full metadata if you need it. Social_Ready is a separate recipe output you strip - do not overwrite the print TIFF. Remove AI Label Team