EU AI Act 2026: what agencies need to know
If your agency creates or publishes AI-generated images for clients — product photography, ads, social creative, pitch decks — you have two jobs from 2 August 2026: keep your own portfolio compliant, and help your clients understand that the disclosure duty usually sits with them, not you.
That distinction is the single most useful thing to understand before you brief a single client. Here's the rest, in plain English.
Not legal advice. This guide supports transparency workflows for deployers; confirm obligations with counsel for each client's specific facts.
The rule in one paragraph
Article 50 of the EU AI Act requires deployers — the business publishing AI-generated or AI-manipulated content under its own name — to show a clear, visible disclosure the first time someone sees that content. It applies to photorealistic AI scenes, synthetic people, and material image changes that could mislead a viewer. It does not require every AI-touched pixel to be labeled — minor retouching, cropping, and color correction are typically out of scope.
For the full plain-English breakdown of the law itself, see EU AI Act 2026, explained in plain English →
Who's the deployer: you or your client?
This is the question every account team will get asked. The answer depends on who publishes, not who created the file:
| Situation | Typical deployer |
|---|---|
| Client sends the email, runs the ad, or publishes the landing page | The client |
| Your agency publishes under its own name — portfolio, case studies, agency newsletter | Your agency |
| A freelancer produces the asset, the client publishes it | The client |
The four things to tell every client:
- The brand or store publishing the material is usually the deployer — and holds the legal responsibility.
- Your agency is the deployer for its own portfolio, case studies, and newsletter.
- The disclosure notice must be visible on or next to the image at the user's first exposure — not buried in a footer or a separate compliance page.
- Backend signals (metadata, C2PA, provider watermarks) do not replace a visible label.
Put plainly: your client doesn't get to point at your work and say "the agency should have handled disclosure." If they're the ones hitting publish under their own brand, the duty is theirs — but a good agency builds the labeling step into the workflow anyway, because it protects the relationship.
Channel-by-channel: how the labeling approach changes
Where the content lives changes how you apply the disclosure. This is the cheat sheet worth pinning in your creative team's Slack:
| Channel | Label type | Placement |
|---|---|---|
| Web (store / site) | Overlay | On the product photo |
| Burned-in | In the hero image | |
| Ad (social / paid) | Burned-in | In the creative itself |
| PDF (deck / one-pager) | Burned-in | On in-scope images |
The reason for the split: on a website, an overlay rendered by the platform is enough because the label lives with the page. Everywhere else — inbox, feed, downloaded file — the label needs to travel with the pixels, because you don't control what happens to the file once it leaves your CMS.
When this actually matters (and when it doesn't)
High priority — label these:
- Photorealistic product renders and AI studio shots
- Synthetic models or lifestyle scenes presented as real
- Ads or landing pages with realistic synthetic people, places, or results
- Case studies presenting AI-generated work as real client photography
Lower priority — usually skip:
- Minor retouch, color grading, cropping
- Clearly stylized illustrations or abstract graphics
- Decorative blog art that no reasonable viewer would mistake for a photo
If a client asks "do we really need to label every AI image," the honest answer is no — focus on the content that could be mistaken for something real, especially where it influences a purchase decision or a portfolio claim.
Matching the right tool to the right client
Not every client needs the same setup. Here's how the toolkit maps to common agency scenarios:
| Client situation | Tool | Why |
|---|---|---|
| Shopify or WordPress store with AI product photos | EU AI Label | Visible overlays, bulk tagging, Compliance Hub, and an audit log — no theme code edits |
| Any website you don't want to touch page-by-page | AI Act Icon | Scans the site, classifies images, deploys one badge script |
| Email sends, social creative, decks, marketplace listings | EU AI Icon | Burns a visible label directly into image pixels before export |
| You manage multiple client tools/stores and want one overview | aiact.solutions | The full toolkit hub, one place to brief a client from |
Pricing reference for client conversations:
- EU AI Label — Free, or from €7/mo (Shopify · WordPress · WooCommerce)
- AI Act Icon — Free, or Starter €29/mo (any website)
- EU AI Icon — 10 free downloads/day, or from €2 per credit pack
The partner program
Agencies that bring clients onto the toolkit get 40% of client subscription revenue for 12 months — extended to 24 months once the agency has published a post about the solution (like this one).
Roadmap to know before you pitch a client:
| Milestone | Date |
|---|---|
| EU AI Label — WordPress free tier | Live now |
| AI Act Icon | Live now |
| EU AI Label — Shopify private install (partners) | 30 July 2026 |
| Article 50 applicability | 2 August 2026 |
| EU AI Label — Shopify App Store listing | ~mid August 2026 |
Private Shopify installs happen ahead of the App Store listing during review — client settings migrate automatically when the public app goes live, so there's no reason to wait to start client conversations now.
Ready to brief a client or join as a partner? Book a partnership call → or explore the full toolkit at aiact.solutions.
FAQ
Is my agency responsible for every client's AI images?
No. The client is usually the deployer when they publish under their own brand. You're the deployer for your own portfolio, case studies, and newsletter — and you should hold your own work to the same standard you recommend to clients.
Does provider metadata (Midjourney, Firefly watermarks) cover our clients?
No. Metadata and machine-readable marks are mostly a provider-side signal and are often stripped by CMS or CDN pipelines anyway. Clients still need a visible, human-readable label at first exposure.
What should be in a client handoff pack?
A short AI-use note, a link to the client's compliance hub (if using one), channel-specific labeling instructions, and a pre-flight checklist before campaigns launch. See the full agency partner guide for a template structure.
Which tool should we recommend for a Shopify client vs a custom website client?
Shopify/WordPress product catalogs → EU AI Label. Custom or agency-built websites where you don't want to touch every template → AI Act Icon. Either way, off-site creative (email, social, decks) should use EU AI Icon.
How much can our agency earn from referrals?
40% of client subscription revenue for 12 months, extendable to 24 months after publishing about the solution. Book a partnership call to get exact terms for your agency.
Get started
See the full toolkit and partner terms at aiact.solutions, brief your team using the channel cheat sheet above, and book a partnership call when you're ready to bring clients on.
EU AI Label, EU AI Icon, and AI Act Icon support transparency workflows under Regulation (EU) 2024/1689 Article 50. They are not legal advice and do not guarantee compliance. Confirm obligations with counsel for each client's facts.