Transparency

DSA transparency report: template, deadline and contents

Since July 2025, the transparency report under Art. 15 DSA follows fixed templates set by the Commission. This guide covers who has to report, when the 2026 report is due, and which numbers to start collecting now.

  • Status: October 2026
  • Updated
  • 6 min read

Most app teams notice the transparency report in February, when it is already due. Yet its format has been fixed since 2025: with Implementing Regulation (EU) 2024/2835 the Commission standardised the templates, the reporting period and the deadlines. If you know now which numbers you need, you will not have to reconstruct them later.

Who has to report

The duty is in Art. 15 DSA and applies to every provider of an intermediary service. That includes any app that stores content from its users: comments, profile photos, listings, posts. Providers publish “at least once a year” clear, easily comprehensible reports on their content moderation, in a machine-readable format and in an easily accessible manner.

Exempt are micro and small enterprises as defined in Recommendation 2003/361/EC, unless they are a very large online platform (Art. 15(2)). The thresholds:

Staff Annual turnover or balance sheet total
Micro enterprise fewer than 10 up to EUR 2 million
Small enterprise fewer than 50 up to EUR 10 million

Partner and linked enterprises count. A studio owned by a large group is therefore rarely “small”. Unlike the platform duties (Art. 19), Art. 15(2) has no 12-month grace period once you grow past the threshold. The guide on exemptions for micro and small enterprises covers the classification in detail.

What goes into the report depends on the type of service:

  • All intermediary services: orders from authorities, own-initiative moderation, complaints, use of automated means.
  • Hosting services also: notices under Art. 16.
  • Online platforms also, under Art. 24(1): disputes before out-of-court dispute settlement bodies and suspensions under Art. 23.

Reporting period and deadline

The Implementing Regulation sets a fixed cycle for every provider except very large platforms:

  • Reporting period: 1 January to 31 December (Art. 2(1)).
  • Publication: at the latest two months after the end of the period (Art. 2(3)).
  • Templates: mandatory since 1 July 2025 (Art. 2(4)).
  • Retention: at least five years after publication, publicly available throughout, including every published version (Art. 3).

Deadline for 2026

The report covering calendar year 2026 must be publicly available by 28 February 2027 at the latest. Plan January for pulling the numbers together and February for the text and sign-off.

Very large online platforms report every six months (Art. 2(2) of the Implementing Regulation, Art. 42 DSA). For app teams below 45 million users in the EU, that does not matter.

The Commission’s templates

Art. 1 of the Implementing Regulation requires the CSV or XLSX version of the templates in Annex I. The Commission publishes the files on its page The DSA brings transparency. Annex II contains the filling instructions and requires one report per service offered.

There are two templates.

The quantitative template has eight sections:

Section Contents Who fills it in
1.1 Report identification: provider, period, publication date all
1.2 Member State orders (Art. 15(1)(a)) all
1.3 Notices under Art. 16 (Art. 15(1)(b)) hosting services
1.4 Own-initiative content moderation (Art. 15(1)(c)) all
1.5 Complaints, dispute settlement, suspensions (Art. 15(1)(d), Art. 24(1)) all, parts for platforms only
1.6 Automated means and accuracy (Art. 15(1)(b), (c), (e)) all
1.7 Human resources for moderation (Art. 42) very large platforms only
1.8 Average monthly active recipients per Member State (Art. 42) very large platforms only

The qualitative template is free text: a summary of own-initiative moderation, a description of the automated means, their purposes, indicators of accuracy and possible error rate, and the safeguards applied.

What goes in

The contents follow from Art. 15(1)(a) to (e) and Art. 24(1):

  1. Orders from authorities under Art. 9 and 10, by type of illegal content and issuing Member State, with the median time to confirm receipt and to give effect to the order.
  2. Notices under Art. 16, by category, how many came from trusted flaggers, the action taken (split by law or terms and conditions), how many were processed by automated means, and the median time to act.
  3. Own-initiative moderation: number and type of measures (removal, disabling, demotion, age restriction and so on), by category and detection method, plus training and support for moderators.
  4. Complaints through the internal complaint-handling system: grounds, decisions, median time and how often decisions were reversed. The template separates upheld, partially reversed and reversed decisions.
  5. Automated means: a qualitative description, the precise purposes, accuracy and possible error rate, safeguards. This covers word filters and AI pre-checks too.
  6. Online platforms only: the number of disputes before dispute settlement bodies under Art. 21 with outcome, median duration and the share of decisions implemented, and the number of suspensions under Art. 23, split into manifestly illegal content, manifestly unfounded notices and manifestly unfounded complaints.

How to describe automated means properly is covered in the guide on AI and automated moderation.

Data to start collecting now

The report is only as good as your data. If you store these values per case from today, February becomes bookkeeping instead of archaeology:

  • Every notice received, with a timestamp, the category from your reporting menu and whether it came from a trusted flagger.
  • The decision, with a timestamp, the measure (remove, restrict visibility, suspend account) and the ground: law or terms and conditions.
  • Detection: user notice, own review or automated filter. And whether the decision itself was automated.
  • Complaints against decisions, with the outcome (upheld, partially reversed, reversed) and duration.
  • Suspensions under Art. 23, with the reason.
  • Orders from authorities, which tend to arrive by email or letter and never reach a ticket system. Keep a separate log.

The median values follow from the timestamps. Map your reporting categories to the template’s categories now, or you will be re-sorting thousands of cases in February.

Tip: zero is a number

If you had no orders or no dispute settlement cases, enter zero. An empty section looks like a forgotten one.

Example: Germany

The German Digital Services Coordinator at the Bundesnetzagentur collects transparency reports through a form on its provider portal. Under section 33(5) no. 7 of the Digitale-Dienste-Gesetz, a report that is missing, incomplete or late can be fined up to EUR 100,000. Other Member States have their own coordinators; the Commission keeps a list of Digital Services Coordinators.

Transparency report vs. Transparency Database

The two are often confused:

Transparency report Transparency Database
Legal basis Art. 15, 24(1) DSA Art. 24(5) DSA
Who all intermediary services except micro and small enterprises online platforms except micro and small enterprises
What aggregated figures and descriptions every single statement of reasons under Art. 17
When once a year, by the end of February without undue delay after each decision
Where public, for example on your website the Commission’s database

The guide on the DSA Transparency Database explains how submission works.

How to do this with Limenia

Limenia counts reports, decisions and appeals itself and drafts the report in the format of Implementing Regulation (EU) 2024/2835. Data Limenia cannot know, such as orders from authorities, you add in the export. More on the DSA notice and action page.

Sources

  1. Regulation (EU) 2022/2065 (Digital Services Act), Art. 15, 19 and 24, EUR-Lexeur-lex.europa.eu
  2. Commission Implementing Regulation (EU) 2024/2835 (transparency report templates), EUR-Lexeur-lex.europa.eu
  3. European Commission: The DSA brings transparency (CSV and XLSX templates)digital-strategy.ec.europa.eu
  4. Commission Recommendation 2003/361/EC (definition of micro and small enterprises), EUR-Lexeur-lex.europa.eu
  5. European Commission: Digital Services Coordinatorsdigital-strategy.ec.europa.eu
  6. German Digital Services Coordinator: information for providers (German)dsc.bund.de
  7. Section 33 Digitale-Dienste-Gesetz (German fines, German)gesetze-im-internet.de

Frequently asked questions

Your question is not here? Write to us, a person will answer.

Go to the contact form

Do I have to file the transparency report with an authority?

Art. 15 DSA requires you to make the report publicly available, for example on your website. Some Digital Services Coordinators also collect reports; the German one, for instance, has a form on its provider portal. Check what your coordinator expects.

Do I need one report per app?

Annex II of Implementing Regulation (EU) 2024/2835 requires one report per service offered. If you run several apps as separate services, you will usually publish one report for each. Check what counts as a single service in your case.

What do I enter if there were no orders from authorities?

The fields stay in the template. Enter zero rather than dropping the section, so it is clear you checked.

Is my small team really exempt?

If your company has fewer than 50 staff and a turnover or balance sheet total of no more than EUR 10 million, usually yes (Art. 15(2) DSA). Partner and linked enterprises count towards the thresholds. Art. 16 and 17 still apply.

What happens if the report is missing?

Penalties are set by each Member State under Art. 52 DSA. In Germany, a missing, incomplete or late report can lead to a fine of up to EUR 100,000, or up to 1 % of total turnover for companies above EUR 10 million (section 33 DDG).

Ready for your notice and action process?

Start your trial in a few minutes. If you would rather talk first, we show you Limenia in a demo.

Or write to us using the contact form