Flux Kontext Inpaint & Instagram Tags
August 18, 2026
Base clean ≠ composite clean
File
Why Instagram may still label
Camera / cleaned base
You are not uploading this after Kontext
Kontext / inpaint export
New provenance on the composite
Mask, depth, or preview PNG
Sidecars; easy to pick by mistake
Re-save in Photoshop after Kontext
May add Adobe C2PA on top
People strip the product hero, run Kontext to replace a label on the bottle, then upload the new PNG thinking “I already cleaned SKU_01.” SKU_01 is not the attach file anymore.
Hosted Kontext vs local graph
Hosted Flux / Kontext JPG: often XMP Software or C2PA on download. Local ComfyUI inpaint: workflow JSON in PNG chunks plus whatever the Save Image node writes. Inspect the composite , not last week’s txt2img sample.
Photoshop or Lightroom after Kontext: another hop. Clean last .
Inpaint then upscale (another node or hosted Enhance) is a third file. A cleaned composite that goes through an upscaler is dirty again. Name files SKU_kontext_v2.png vs SKU_kontext_v2_upscale.png so the carousel does not mix them.
If the mask PNG is sitting next to the composite in the same folder, Instagram’s last-used picker on desktop can grab the mask. Keep sidecars in Archive_masks ; only Social_Ready goes to the composer.
Workflow
- Finish the look in Kontext / inpaint. Export one flat composite.
- Folders: Archive_base (optional), Archive_kontext, Social_Ready.
- Inspect the composite in the AI metadata checker .
- Strip C2PA , XMP , PNG chunks if PNG.
- Instagram: attach Social_Ready. Do not run a second Kontext “tiny fix” on the cleaned file.
- Carousel: every inpainted slide. Mixing one Kontext hero with four camera details still flags the set if the hero is dirty.
Reels cover: the composite is a still upload even when the Reel is phone video.
What this page does not cover
- Flux txt2img + ComfyUI chunk dumps (sibling article).
- Turning off Instagram AI Info in Settings.
- Legal disclosure of edited products (file hygiene ≠ caption policy).
When the Kontext composite is the file you will post, strip it, then finish on the Flux upload hub . Browser-only; prep, not a pixel rewrite.
See Disclaimer .
Post a Flux Kontext composite on Instagram without leftover file tags
Finish the inpaint, export the composite, strip C2PA/XMP, upload that file.
- Export the composite - Save the final Kontext/inpaint raster - flattened, not a mask or sidecar.
- Inspect the composite - Optional: run the AI metadata checker (/ai-metadata-checker) on the composite. Ignore the pre-inpaint base you already cleaned.
- Strip C2PA and XMP - Clean the new export. Enable PNG chunk removal if the file is PNG.
- Upload the composite - Instagram feed, carousel, or Reels cover from Social_Ready only.
Frequently Asked Questions
Is Flux Kontext the same as a ComfyUI Flux PNG?
No. The Flux+ComfyUI article is workflow JSON in PNG text chunks from a graph save. This page is Kontext / inpaint: an edit pass on an existing image, then a new composite export.
I cleaned the base photo already. Do I clean again after inpaint?
Yes. The inpaint export is a new file. It can inherit credentials from the base and add tags from the edit pass. Strip the composite you will upload.
Does Kontext only matter for fully generated pictures?
No. A camera JPEG with a Kontext object swap or sky fill is still an upload of that composite. Instagram reads the file, not your intent.
Should I convert PNG to JPG to drop chunks?
Conversion is not a strip. Clean C2PA, XMP, and PNG chunks on the format you will actually attach. Remove AI Label Team