EU AI Act: Labeling AI Product Images in 2026

Article 50 is now enforceable, and photorealistic AI product images sold into the EU sit squarely inside its scope.

|AI compliance e-commerce regulation AI product photography

On 2 August 2026, Article 50 of the EU AI Act became enforceable. If your store ships to the EU and you use AI-generated product images — virtual models, synthetic lifestyle scenes, fully generated product shots — you now have two distinct obligations: machine-readable marking of the output, and a clear disclosure to the shopper no later than their first exposure to the image.

The confusion in most merchant Slack channels right now is not whether to label. It is what counts. Article 50(2) carves out AI that performs an assistive editing function or does not substantially alter the input data or its meaning. That exemption is the whole ballgame: background cleanup and wrinkle removal generally fall outside the labeling duty, while a synthetic model wearing your garment does not.

This guide walks the line between those two cases with concrete examples, so you can classify your own catalog instead of blanket-labeling everything and eroding buyer confidence for no legal benefit.

What Article 50 actually requires

Two separate duties sit in Article 50, and they land on different parties.

Providers of generative AI systems must mark synthetic image, audio, and video outputs in a machine-readable format so they are detectable as artificially generated. In practice this means embedded provenance metadata — C2PA Content Credentials, invisible watermarking, or equivalent. This is the model vendor's job, not yours.

Deployers — that's you, the merchant publishing the image — must disclose that content is artificially generated or manipulated when it depicts real-looking people, objects, places, or events. The disclosure must be clear, distinguishable, and delivered no later than first exposure.

Penalties are not theoretical

Non-compliance with the transparency obligations carries fines of up to €15 million or 3% of global annual turnover, whichever is higher — plus exposure to unfair-competition claims from competitors in several member states.

Note what the regulation does not do: it does not mandate a specific badge, wording, or placement. There is no official EU logo. You choose the format; regulators judge whether an average shopper would notice and understand it.

The exemption that decides most of your catalog

Article 50(2) exempts AI systems performing "an assistive function for standard editing" or that do "not substantially alter the input data provided by the deployer or the semantics thereof." For product photography, that single sentence separates routine retouching from synthetic content.

Generally exempt (assistive editing)

  • Background removal or replacement with plain white
  • Colour correction and white balance to match the real product
  • Dust, lint, and sensor-spot cleanup
  • Wrinkle reduction on a garment you actually photographed
  • Upscaling, sharpening, cropping, format conversion
  • Shadow cleanup and reflection removal

Requires disclosure

  • A photorealistic AI model wearing your garment
  • Fully generated product shots with no source photograph
  • Synthetic lifestyle scenes that read as a real location
  • Swapping a real model's face, body, or ethnicity
  • Ghost-mannequin output that invents unseen garment interiors as a realistic scene
  • Generated colourways depicting a variant you never produced

The dividing question is semantic, not technical: does the finished image assert something to the shopper that the camera did not capture? A white background asserts nothing. A smiling person who does not exist asserts a great deal.

Pro Tip

Borderline cases — heavy AI background generation that reads as a real studio or location — should be labeled. The cost of an unnecessary label is small; the cost of a missing one is a regulatory finding.

Where to put the disclosure without killing conversions

The most common merchant fear is that a label depresses conversion. The evidence so far points the other way when the label is specific rather than ominous. Vague warnings read as risk; precise statements read as confidence.

PlacementCompliance strengthConversion impact
Caption directly under the imageStrongMinimal
Small corner badge on the image itselfStrongMinimal
Line in the product descriptionAdequate if above the foldNegligible
Sitewide policy page onlyInsufficientNone
Full-width interstitial before viewingStrongSignificant drop

Wording matters more than placement. Compare these two, both technically compliant:

  • Weak: "Warning: this image was created by artificial intelligence."
  • Strong: "Shown on an AI-generated model. The garment, colour, and fabric are photographed from the actual product."

The second discloses fully and reassures the shopper about the thing they actually care about — whether the product itself is real and accurately represented.

Machine-readable marking: what to check with your vendor

Even though the marking duty falls on the AI provider, you inherit the practical consequences. Platforms increasingly read provenance metadata automatically, and stripped metadata can trigger their own auto-labels — often less flattering than yours.

Ask any AI imaging vendor three questions:

  1. Does the output carry C2PA Content Credentials or an equivalent machine-readable marker? Get the answer in writing; it is your evidence of upstream compliance.
  2. Does the marker survive your pipeline? Most CDN resize and re-encode steps strip metadata by default. Test an end-to-end round trip from generation to live product page.
  3. Is there an audit trail per image? When a regulator or marketplace asks which images were AI-generated, a per-asset record beats reconstructing history from memory.
Pipeline reality check

Run one generated image all the way to your live PDP, then inspect it with a Content Credentials verifier. If the provenance is gone, your image-optimisation step is stripping it — configure the CDN to preserve metadata for AI-generated assets, or keep your own database record as the fallback audit trail.

Platforms like Retouchable that maintain a per-asset generation record make this considerably easier than reconstructing provenance from a folder of exported files.

A practical compliance workflow

Blanket-labeling every image is the wrong response — it dilutes the signal and misrepresents genuinely photographed products. Classify instead.

Typical apparel catalog after classification
Camera + assistive edits (exempt)
62%
AI model / synthetic scene (label)
29%
Borderline — label to be safe
9%

Illustrative distribution for a mid-size apparel brand using AI models for secondary gallery shots. Your split will differ; the point is that most catalogs are majority-exempt.

  1. Inventory. Tag every image in your DAM as camera-original, assistively edited, or synthetic.
  2. Classify against Article 50(2). Apply the semantic test: does it assert something the camera did not capture?
  3. Template the disclosure. One approved caption per image type, so nobody improvises wording per listing.
  4. Automate the join. Bind the label to the image record, not the listing, so the disclosure follows the asset into every channel — feed, marketplace, email, ad.
  5. Verify metadata survives. Re-check after any CDN or theme change.
  6. Keep the record. Retain generation logs; they are your defence if the classification is challenged.
15MMax fine in euros
3%Or global turnover
2 Aug 2026Rules in force

What this means outside the EU

The AI Act applies where output is placed on the EU market, regardless of where you are established. A US brand shipping to Germany is in scope for those listings.

Practically, most brands converge on one global standard rather than maintaining EU-only image variants. Maintaining two catalogs — one labeled, one not — multiplies asset management overhead and creates the exact inconsistency that draws scrutiny.

The wider direction of travel supports that choice. Major marketplaces already require AI-content declarations, ad platforms auto-detect and label synthetic media, and several non-EU jurisdictions have transparency bills in progress. Building the labeling discipline once, against the strictest standard in force, is cheaper than retrofitting it per market.

Treat disclosure as product information rather than legal boilerplate, and it stops being a tax. Shoppers who know the model is generated but the fabric photograph is real return fewer items than shoppers who feel misled after delivery.

Frequently Asked Questions

Does background removal count as AI-generated content under the EU AI Act?

Generally no. Article 50(2) exempts AI performing an assistive editing function that does not substantially alter the input data or its meaning. Removing a background, correcting colour, or cleaning dust preserves what the camera captured, so it typically falls outside the disclosure obligation.

Do I need to label images made with an AI model wearing my real clothing?

Yes. A photorealistic synthetic person is content depicting a person who does not exist, which triggers the disclosure duty. The recommended approach is a caption that both discloses the AI model and clarifies that the garment itself was photographed from the real product.

What format does the disclosure have to take?

The AI Act does not prescribe a format, logo, or wording. It requires the disclosure to be clear, distinguishable, and provided no later than the first exposure to the content. A caption below the image or a small on-image badge both satisfy this; burying it in a sitewide policy page does not.

Does the EU AI Act apply to my US or UK store?

It applies wherever the output is placed on the EU market. If you ship to EU customers and show them AI-generated product imagery, those listings are in scope regardless of where your business is registered. Most brands adopt one global labeling standard rather than maintaining split catalogs.

Who is responsible for the machine-readable watermark?

The provider of the generative AI system must mark outputs in a machine-readable, detectable format. As the merchant deploying the images, your duty is the visible disclosure — but you should verify with your vendor that provenance metadata exists and that your CDN or image pipeline does not strip it during optimisation.

Generate compliant AI product imagery with a full audit trail

Retouchable keeps a per-asset generation record for every image, so classifying and disclosing your AI-generated visuals takes minutes instead of a catalog-wide archaeology project.

Try Retouchable Free No credit card required