EU AI Act Article 50 · deadline Aug 2, 2026

AI Disclosure Generator for Designers

Drop-in disclosure labels for Midjourney hero images, Firefly mockups, AI illustrations, and generative brand work. HTML credit blocks, image overlays, IPTC/XMP metadata, and JSON-LD schema — free, no signup, EU AI Act compliant.

Preview — AI credit on a portfolio shot

Identity / 2026 Studio
AI: Midjourney v7 + Firefly composite
AI-generated Hero shapes generated with Midjourney v7, color graded and composited with Adobe Firefly Generative Expand. Typography, layout, and final art direction by the studio.

Why designers in 2026 can't skip the AI credit

The AI image stack moved from novelty to default in eighteen months. By mid-2026 the majority of working brand designers ship at least one Firefly, Midjourney, or Recraft asset per project — usually as a hero, a moodboard kickoff, or a generative texture layered behind real type. The legal scaffolding caught up faster than most studios noticed. The EU AI Act Article 50 takes hold on August 2, 2026, and it doesn't care that your client is in New York or that you're a freelancer in Lisbon — if the deliverable ends up visible to anyone in the EU, the disclosure obligation attaches. That includes a Behance shot a procurement lead in Berlin scrolls past, a packaging mockup an EU retailer signs off on, and a campaign hero that lives on a brand's European microsite.

The penalty side is unusually steep for the design industry: up to €15 million or 3% of global turnover, applied at the entity making the content public. In practice that means the brand pays, then claws back from the studio under the AI-disclosure warranty clause that nearly every 2026 master services agreement now contains. The downstream effect: design buyers have started requiring AI provenance attestation at handoff, the same way they require font license confirmation. A credit block isn't paperwork. It's the new font license.

Five designer use cases the generator was built for

How the generator output plugs into a designer's actual workflow

The generator produces four parallel outputs from one input, because designers don't live in one tool. The HTML credit block goes on portfolio sites — Cargo, Semplice, Squarespace, Framer, or self-hosted Astro — in the project description or under the hero. The image overlay PNG (1080×1080 or 1920×1080) is a transparent corner badge you composite over the asset before upload to Behance, Dribbble, or Instagram so the credit travels with the file when it's reposted. The IPTC/XMP metadata string drops into Adobe Bridge, Photo Mechanic, or your Lightroom export preset for batch tagging the whole project folder. The JSON-LD CreativeWork schema goes in your portfolio site's page head where Google can read it and where the W3C's emerging C2PA provenance ecosystem can index it.

The end state is one project ID, one prompt-seed input, one generator run, four outputs, deployable across portfolio, social, file metadata, and structured data — in under thirty seconds. That's the bar designers asked for: compliance that doesn't cost a workflow.

What the generator does not do

It does not file your client's GPAI-deployer obligations under Article 53, which is a separate question that sits with the brand, not with you. It does not generate model-card disclosures for AI features you build into a client's product — that's a different artifact under Article 13. And it doesn't replace contract review: the AI-disclosure warranty clauses now standard in 2026 design contracts still need a lawyer's eyes the first time you see one. The AIGA professional guidelines and a number of EU-side practitioner write-ups offer template language that's become the de facto reference for studio contracts.