Issue Feature Under Review Quiet

#108953Introduction of a metadata flag and labeling for AI-generated images (EU AI Act compliance)

Stefan Froemken 02/12/26, 09:42 updated 09/30/26, 08:22

Description

With the upcoming EU AI Act (specifically Article 50), there will be a legal requirement to label AI-generated content, especially “deepfakes” or realistic-looking images. Starting August 2, 2026, providers and users must ensure transparency by marking such content in a machine-readable format to indicate its artificial origin.

To ensure TYPO3 remains compliant with these future regulations and to provide users with the necessary tools for transparency, we propose integrating a standardized way to manage and display AI-metadata within the File Abstraction Layer (FAL).

Proposed Requirements

  1. Metadata Field: Add a new field (e.g., is_ai_generated) to the sys_file_metadata table to store the origin of an image.
  2. Frontend Labeling: Provide a standardized way (or a helper/viewhelper) to display a visible “AI-generated” label or disclaimer on the website.
  3. FAL Integration: Allow editors to manually toggle this flag in the Filelist module and potentially detect existing AI-metadata during file indexing/upload.

Background & Deadlines

  1. Deadline: Mandatory by August 2, 2026.
  2. Legal Basis: EU AI Act (Art. 50) regarding transparency obligations for providers and users of AI systems.
  3. Goal: To prevent deception and ensure that users can distinguish between human-made and AI-generated realistic content.

Early implementation (e.g., in TYPO3 v14) is recommended to give agencies and developers enough time to adapt their projects before the legal deadline.

Reviews 2

Linked, but not in Forger: Change 95417

History 1419

  1. Frank Nägler commented and changed assigned to Frank Nägler <span data-processor="relativetime" data-value="2026-02-12T10:08:48+00:00" > 02/12/26, 10:08 </span>

    We will consult a lawyer and have the legal situation assessed.

  2. Georg Ringer commented and changed status New In Progress <span data-processor="relativetime" data-value="2026-02-13T20:52:51+00:00" > 02/13/26, 20:52 </span>

    I rejected #108632 a month ago with:

    > there are already fields like creator, creator_tool and source – aren’t those not enough?

    as long as TYPO3 itself does not create files automatically, it is up to the extension or editor to use it correctly.

    will leave this issue open to sort it out as IANAL

  3. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-02-13T21:06:44+00:00" > 02/13/26, 21:06 </span>

    Ideally images should receive EXIF meta tags to indicate the AI-origin IMO, not manual metadata.

    Otherwise “machine readable” will be hard to achieve. If TYPO3 makes it a caption or data attribute or so on output that would be quite custom.

    ($0.02 I hope “the industry” gets this sorted out and not have a fallout like with cookie banners instead of doing browser-side “DNT” integrations.)

  4. Frank Nägler commented <span data-processor="relativetime" data-value="2026-02-17T11:30:05+00:00" > 02/17/26, 11:30 </span>

    I had a lawyer review the situation. As a CMS product, we have no legal obligation to do this; however, users will have to label such content in the future. This potentially affects all CMS users who publish AI-generated content, even if it wasn’t created in or from TYPO3.

    Therefore, we would be doing our users a great service if TYPO3 supported this feature natively.

    So from my side a clear +1 for integrating suche a feaure.

  5. Frank Nägler commented <span data-processor="relativetime" data-value="2026-02-17T11:31:26+00:00" > 02/17/26, 11:31 </span>

    And by the way, I also opt for a backport, at least to version 13.

  6. Frank Nägler commented <span data-processor="relativetime" data-value="2026-03-18T08:12:34+00:00" > 03/18/26, 08:12 </span>

    @Georg, what kind of feedback do you need? I have added the lawyer’s feedback and my personal opinion on the backport for version 13. What is missing?

  7. Georg Ringer commented <span data-processor="relativetime" data-value="2026-08-07T11:27:53+00:00" > 08/07/26, 11:27 </span>

    @frank thx, nothing missing, can be built by anyone

  8. Gerrit Code Review pushed patch set 1 for main to change 95172 status In Progress Under Review <span data-processor="relativetime" data-value="2026-08-07T22:28:31+00:00" > 08/07/26, 22:28 </span>

  9. Dan Kleine (Untenzu) commented <span data-processor="relativetime" data-value="2026-09-30T07:16:26+00:00" > 09/30/26, 07:16 </span>

    Hey @neoblack ,

    I really welcome the fact that a solution is to be created here in TYPO3 Core for a problem that affects everyone anyway, rather than having every integrator reinvent the wheel for implementation. (I’m reminded of the effort and uncertainties involved with the GDPR tasks).

    The approach outlined in the patch sounds good, as does the plan to make it available for versions 13 and 14. Thanks for your work and pushes!

    Unfortunately, the patch has been pending for a month. And the mentioned deadline of August 2 has passed.
    Can you estimate when the patch will be reviewed? I’m afraid that otherwise, out of necessity, many small solutions will once again emerge in parallel, rendering the approach outlined in this ticket obsolete.

  10. Benni Mack commented <span data-processor="relativetime" data-value="2026-09-30T08:22:22+00:00" > 09/30/26, 08:22 </span>

    Hey @pbtypo3 ,

    I created this extension https://packagist.org/packages/b13/ai-label to also allow this in older versions, but we’re not 100% sure yet, what should be covered in core vs. should be added on top. I do agree that we need this in core somehow.