← All posts

Labeling AI images from Midjourney, DALL·E and Firefly in WordPress

DALL·E, Firefly and Google models already embed a C2PA signature, Midjourney does not. In WordPress it's often lost anyway when the image sizes are generated.

Article 50 of the EU AI Act has applied since 2 August 2026: AI-generated images should be machine-readable as such, and deepfakes visibly so. How well that works depends on the generator. DALL·E, Firefly and Google models already embed a machine-readable signature (C2PA / Content Credentials); Midjourney does not, as of 2026. In WordPress a second problem is added: the signature is often lost when the image sizes are generated.

What the individual generators include

GeneratorMachine-readable signature on exportWhat that means for you
OpenAI DALL·E 3 / GPT imagesyes, C2PA manifestthe signature is present – it only has to be preserved
Adobe Fireflyyes, Content Credentials (C2PA)as above
Google Imagen / Geminiyes, C2PA metadata (plus invisible SynthID)as above
Midjourneyas of 2026, nono signature to preserve – the label has to be set actively

The WordPress problem

When WordPress generates the thumbnails and intermediate sizes on upload, it rewrites the image data – and C2PA manifests do not survive that in many configurations. The front end then usually serves one of those derived sizes, that is, precisely the file without the signature. Even a properly signed DALL·E image is then no longer recognisable as an AI image on the site.

What you should do in practice

  • For DALL·E, Firefly, Google: make sure the existing C2PA signature is carried into all image sizes.
  • For Midjourney: actively mark the image as AI-generated, because no generator marker exists – either by hand via the media library or via a detection that checks metadata patterns and image signals and presents the case to you for confirmation.
  • For deepfakes – realistic-looking depictions of people or events – also add a visible label.
  • For clearly recognisable illustrations and icons, a visible label is usually not required; the machine-readable mark should still be preserved.

Where IMG Performer fits in

IMG Performer works in two stages: it detects AI images on upload automatically from C2PA metadata and other signals, and lets you categorise borderline cases – such as Midjourney exports without a signature – manually. The machine-readable mark is then written back into every image size generated by WordPress, with a visible front-end label on request. Details: C2PA labeling in WordPress and Labeling AI images for the EU AI Act.

Disclaimer

Legal note: general context, not legal advice. The binding sources are the original text of Article 50 of the EU AI Act (Regulation (EU) 2024/1689, eur-lex.europa.eu/eli/reg/2024/1689/oj) and the guidance of the responsible authorities. Details on the generators may change. As of September 2026.

Frequently asked questions

Do I even have to label Midjourney images if they have no signature?

The missing generator signature does not change the transparency obligation. For deepfakes the visible label applies; for other AI images a machine-readable mark is intended – which you then have to set yourself.

Is it enough to state in the imprint that AI images are used?

A blanket notice does not replace labeling at the individual image, and in particular not the visible labeling of deepfakes.

What about images I generated before August 2026?

Images generated before 2 August 2026 are exempt. Voluntary retroactive labeling is recommended.