Freelance photographer AI metadata delivery

Pre-upload checklist for Product Photo Delivery

• Finalize your export - no extra apps after cleaning.
• Spot-check one hero image in the AI Metadata Checker .
• Strip metadata with Remove AI Label - 30 images per batch.
• Upload before posting to Instagram, Facebook, or Pinterest.
• Deliver a Social_Ready folder so clients never re-upload RAW files with C2PA.

One master JPG is enough

Keep a master JPG after Lightroom or Photoshop. Remove C2PA and XMP once , then reuse for feed, Story, ads, and marketplace listings - as long as you do not send the file through Canva or mobile AI apps again. Each extra app can re-attach provenance markers.

Common mistakes with Product Photo Delivery

• Mixed carousel slides - half cleaned, half not; AI Info returns on the next flagged frame.
• Re-export after cleaning - Canva and Adobe Express re-attach provenance.
• Screenshots instead of exports - do not reliably fix metadata.
• Fixing live posts - Instagram does not strip C2PA from stored files; export the original, clean, republish.

Cross-posting and live posts

Same JPG for Instagram, Pinterest, and TikTok? Remove metadata once before every channel. Meta and Pinterest scan C2PA and XMP . To fix a live post, download your original export, clean in the browser, upload again - see Instagram guide .

Reduce support tickets

Email clients: "If you see AI Info, it is almost always edit metadata - use Social_Ready." Link AI label false positives in onboarding PDFs.

EXIF vs C2PA

Need camera EXIF for archive or print? Strip only C2PA and XMP , keep standard EXIF when your workflow allows. The checker shows which blocks are present before you clean.

Workflow summary

Inspect one file → batch-clean with Remove AI Label → upload cleaned JPG → deliver Social_Ready copies. Browser-based processing keeps files on your device - useful for client galleries and listing photos.

*Use on files you own. Follow platform and regional AI Info rules where they apply - see our [disclaimer]

Why product photography deliveries trigger AI labels for clients

Brand marketing teams upload your JPGs to:

• Instagram feed, Stories, and Shopping tags
• Facebook catalog and Meta ads
• Shopify , Amazon, or wholesale portals
• Pinterest and TikTok Shop creatives

Any step in your pipeline that invokes Adobe or cloud AI can write provenance data or XMP into the export:

• AI background removal on white seamless heroes
• Generative Fill for label straightening or dust cleanup
• AI Denoise on splash and motion shots
• Photoroom-style cutouts when clients request quick variants
• Batch actions synced across fifty SKUs - one preset, every file flagged

The brand did not generate the product in Midjourney. Your hidden metadata did the talking at upload time.

Delivery type

Common AI edit

Client upload surface

White-background hero

BG remove, Generative Fill

Instagram Shopping, Amazon

Lifestyle scene

AI Denoise, sky swap

Meta ads, brand feed

Detail macro

Dust removal AI

PDP zoom, email campaigns

Flat lay composite

Generative elements

Pinterest, TikTok

Uncleaned camera RAW export

Lower risk

Still inspect if LR sync used

Client delivery standards - two folders, zero confusion

Professional handoffs should separate:

• Print / archive masters - full EXIF if the client needs it for DAM or print proofing
• Social_Ready / Meta_Ready - provenance data and XMP stripped , sized for Instagram and ad specs

Brief clients in one line on the invoice: "Social_Ready folder is pre-cleaned for Meta upload - use those for Instagram and ads."

Cross-link e-commerce teams to Shopify Product Photos when the same files hit storefront admin.

How I confirmed it was hidden metadata (not the client "switching to AI")

I ran the flagged hero through the AI Metadata Checker . provenance data and XMP from my Photoshop export chain - pixels matched the approved proof. metadata-driven label, not a visual detection failure on the product itself.

If the checker is clean but a live ad still shows AI Info, cleaning helps the next campaign upload, not retroactive fixes on Meta's side.

My delivery workflow now (~30 seconds per image)

Step 1 - Export final retouch JPGs

sRGB, client dimensions, embedded profile as spec requires. Finish all AI-assisted steps before export.

Step 2 - Inspect one hero SKU

Pick the main image the client will use for launch hero and ads. Run through the checker.

Step 3 - Batch-clean the delivery set

Process campaign folders through Remove AI Label with provenance data and editing tags removal in the browser. Batch: up to 30 images per pass - repeat for full SKU ranges.

Step 4 - Deliver Social_Ready + upload guide

Zip Social_Ready separately from print masters. Point social managers to Instagram guide for upload order and carousel tips.

For 20-image lookbooks, batch-clean the entire set before the WeTransfer link goes out. One uncleaned lifestyle frame can flag a whole carousel.

Tips for commercial product photographers

• Line item hidden metadata prep on quotes - same as retouching, clients pay for upload-ready deliverables.
• Reshoot vs relabel: Cleaning is faster than a client panic thread about AI Info on launch day.
• Amazon and marketplace sellers: See Amazon Seller Guide when clients sell on multiple channels.
• Influencer seeding kits: Brands often repost your lifestyle frames - cleaned delivery protects their creators too.

For in-house brand photographers

If you are both shooter and uploader, build checker → clean → upload into DAM publish steps. Same before upload rule as agency delivery - no separate "social team will fix it" assumption.

Folder name

Contents

Who uses it

_MASTER

Full retouch, EXIF intact

Print, archive, DAM

_SOCIAL_READY

provenance data/editing tags stripped

Meta, Meta ads

_WEB

Sized derivatives

PDP, email (clean if AI-edited)

Rush same-day selects for brand social teams

Clients sometimes need same-day selects for a product launch while retouching continues. Deliver low-res cleaned selects for Stories only, with a note that final high-res masters follow after the full hidden metadata pass - avoids labeled launch posts.

Photoshop . Every hero gets AI background removal , Generative Fill on dust spots, Lightroom AI Denoise on high-ISO splash frames.

The client loved the delivery. Two weeks later: Slack message - their Meta Shopping carousel shows AI Info under a SKU we shot on a real set.

Commercial product photographers are learning what wedding studios already know: clients do not read editing tags . They read AI Info on a launch post and assume something went wrong with the campaign. Usually it is hidden metadata from your retouch stack - a false positive fixable before upload if you deliver social-ready files upfront.

Document which SKUs used background removal or Generative Fill so account teams know the label is metadata, not a product reshoot.

See Disclaimer .

See Disclaimer .

Deliver product photography to clients without AI metadata

Finalize retouch exports, batch-remove C2PA and XMP, hand off social-ready JPGs for brand upload.

• Export final retouch JPGs - Complete white-background heroes, lifestyle scenes, and detail macros in Photoshop or Capture One at client-specified dimensions.
• Inspect one hero SKU - Run a sample main image through the AI metadata checker before batch processing the delivery.
• Batch-clean the delivery set - Strip C2PA and XMP in the browser - files in batches of 30 - label folders by SKU or campaign.
• Deliver Social_Ready to client - Include metadata-cleaned copies for Instagram, Meta ads, and e-commerce upload; keep print masters separate.

Keep reading

• Remove AI Label vs DeleteFootprints
• Remove AI Label vs ExifReader
• Remove AI Label vs AI Metadata Cleaner
• AI Image Check Before Instagram Upload
• Remove AI Content from Instagram - Guide
• Instagram AI Content Label - Explained