Comparison GuideEU

DSA vs DMA content safety duties versus gatekeeper obligations

This comparison helps separate Digital Services Act duties for intermediary services, hosting, online platforms, marketplaces, VLOPs, and VLOSEs from Digital Markets Act duties for designated gatekeepers and their core platform services.

The DSA workstream is usually owned by trust and safety, marketplace operations, legal, policy, ads, recommender, and content-moderation teams. The DMA workstream is usually owned by competition counsel, platform product, engineering, data governance, developer relations, commercial operations, and compliance reporting teams.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

The Digital Services Act and Digital Markets Act can apply to the same service, but neither status implies the other. The DSA classifies EU-facing intermediary services and adds duties by service role and size. The DMA applies only to an undertaking designated as a and only for the core platform services listed in its designation decision. Run both tests when a large platform handles content or traders and also controls access, defaults, data, interoperability, or business-user terms.

Side-by-side comparison

DSA vs DMA: operational differences that matter

This table helps decide which law controls a product change, incident, disclosure, access request, regulator question, or evidence gap.

Review all sources
First framework
Digital Services Act

The DSA regulates intermediary-service accountability, especially content moderation, platform transparency, user redress, marketplace traceability, advertising and recommender transparency, and systemic-risk governance for VLOPs and VLOSEs.

Second framework
Digital Markets Act

The DMA regulates designated gatekeepers and listed core platform services to keep digital markets contestable and fair for business users and end users.

Scope boundary

Digital Services Act

Online intermediary accountability: illegal content handling, content-moderation transparency, platform redress, marketplace trader traceability, advertising and recommender transparency, protection of minors, and systemic risks.

Digital Markets Act

market power: conduct by large core platform services that can restrict contestability, user choice, interoperability, data access, switching, business-user reach, or fair access terms.

Operational implication

Frame DSA work as platform governance and safety operations. Frame DMA work as conduct, competition, access, and product-design compliance.

Covered actors

Digital Services Act

Mere conduit, caching, hosting, online platforms, online marketplaces, online search engines, VLOPs, and VLOSEs, with obligations increasing by service role and size.

Digital Markets Act

Designated gatekeepers and the core platform services listed in the designation decision, including categories such as online intermediation, search, social networking, video-sharing, number-independent messaging, operating systems, browsers, virtual assistants, cloud, and advertising services.

Operational implication

Classify DSA services by intermediary role; classify DMA services by designation and listed .

Trigger

Digital Services Act

status uses online platform or search engine average monthly active recipients in the EU equal to or higher than 45 million, followed by Commission designation; the enhanced duties apply four months after notification.

Digital Markets Act

designation uses significant-impact, gateway, and entrenched-position criteria. The quantitative presumption includes EUR 7.5 billion EU turnover in each of the last three financial years or EUR 75 billion average market capitalisation/equivalent fair market value in the last financial year, the same in at least three Member States, and in the last financial year at least 45 million monthly active EU end users and 10,000 yearly active EU business users. The user thresholds must have been met in each of the previous three financial years for the entrenched-position presumption.

Operational implication

Do not infer DMA status from DSA status, or the reverse. Run the tests separately, preserve the counting method, and use the Commission decision to identify the DMA-covered services. A listed generally has six months from designation to comply with .

Core obligations

Digital Services Act

Terms controls, points of contact, transparency reporting, hosting notice-and-action, statements of reasons, platform complaint handling, out-of-court dispute handling, trusted flagger priority, misuse controls, ad transparency, recommender transparency, minors safeguards, trader traceability, and risk management, audits, data access, compliance functions, and ad repositories.

Digital Markets Act

obligations for each listed include limits on personal-data combination without valid consent, freedom for business users to promote offers and conclude contracts with end users, access and interoperability duties, default-choice and uninstallability duties, fair access terms, and data portability or access duties. Separate DMA provisions govern anti-circumvention (Article 13), compliance reporting (Article 11), concentration notices (Article 14), and independently audited descriptions of consumer-profiling techniques (Article 15).

Operational implication

DSA implementation changes moderation, marketplace, ads, recommender, transparency, and risk systems. DMA implementation changes platform conduct, data flows, interoperability, defaults, ranking, access, commercial terms, and reporting evidence.

Evidence record

Digital Services Act

Service classification, AMAR methodology, notices, moderation decisions, statements of reasons, complaint outcomes, trusted-flagger handling, misuse suspensions, trader verification, ad labels, recommender parameter disclosures, transparency reports, risk assessments, mitigation records, audit reports, and researcher data-access logs.

Digital Markets Act

Designation records, maps, obligation matrices, product and engineering change descriptions, data-use records, consent or choice flows, interoperability reference offers and request logs, business-user access terms, compliance-function records, Article 11 compliance reports, non-confidential summaries, annual updates, and consumer-profiling audit descriptions.

Operational implication

Keep a shared evidence register only if each record identifies the regime, article or obligation, owner, source, affected service, date, and next review trigger.

Enforcement bodies and fine ceilings

Digital Services Act

Digital Services Coordinators supervise providers established in their Member State, while the Commission has direct supervisory and enforcement powers for VLOPs and VLOSEs. Commission fines for infringement can reach 6% of total worldwide annual turnover in the preceding financial year.

Digital Markets Act

The Commission is the sole DMA enforcer, supported by cooperation with national authorities. Fines can reach 10% of total worldwide turnover in the preceding financial year, or 20% for the same or similar Article 5 to 7 infringement for the same after a non-compliance decision in the preceding eight years.

Operational implication

Regulator engagement should follow the regime. DSA escalation may involve a Digital Services Coordinator or the Commission for VLOPs/VLOSEs; DMA escalation is Commission-centered and tied to non-compliance.

Implementation owners

Digital Services Act

Trust and safety, moderation operations, marketplace operations, advertising product, recommender-system owners, policy, legal, risk, compliance, audit, and researcher-access teams.

Digital Markets Act

Competition counsel, platform product, engineering, data governance, privacy, interoperability owners, developer relations, commercial operations, compliance function, and regulatory reporting teams.

Operational implication

A combined EU digital-regulation group can coordinate dependencies, but the accountable owners should remain tied to the system they can actually change.

Overlap and reuse

Digital Services Act

The same product change can touch DSA and DMA at once when it affects content moderation, trader verification, ad labels, recommender disclosures, or risk work on one side and data access, interoperability, defaults, , or business-user terms on the other.

Digital Markets Act

Reuse is possible only after the team separates the legal question: the DSA asks whether the service is handling intermediary-service duties, while the DMA asks whether a designated is changing conduct for a listed .

Operational implication

Check whether one change creates two obligations. If yes, keep one evidence file, but tag each artifact with the DSA or DMA rule it supports before you send it to legal, product, or regulators.

Practical decision rule

Digital Services Act

Start with DSA if the question is about illegal content, moderation, notice handling, transparency reporting, trader traceability, trusted flaggers, complaints, or systemic-risk mitigation for a platform or search service.

Digital Markets Act

Start with DMA if the question is about a designated 's , especially defaults, access, data combination, interoperability, , , , or business-user terms.

Operational implication

If both regimes apply, assign two findings and two owners. Then decide which parts of the product spec, log set, or report can be shared without collapsing the DSA service-tier analysis into the DMA analysis.

Practical decision rule

How to decide which workstream controls a change

  • If the issue is illegal content, moderation, notice handling, user redress, advertising disclosure, recommender transparency, trader traceability, minors protection, or systemic risk, start with the DSA.
  • If the issue is a designated 's , user choice, data combination, access, interoperability, business-user terms, anti-, , defaults, , or Article 11 reporting on compliance with , start with the DMA.
  • If both apply, write two findings: one DSA service-tier finding and one DMA /core-platform-service finding.
  • Assign one operational owner per finding, then decide which logs, product specs, reports, or regulator submissions can be reused without changing their legal label.
Section 1

The shortest useful distinction

Use the DSA when the fact pattern is about an intermediary service made available in the EU: mere conduit, caching, hosting, online platform, online marketplace, online search engine, VLOP, or VLOSE. DSA evidence normally starts with service classification and then moves into notice-and-action, statements of reasons, complaint handling, trusted flagger priority, transparency reporting, advertising and recommender disclosures, trader traceability, or systemic-risk files.

Use the DMA when the fact pattern is about a designated and a listed . DMA evidence normally starts with the designation decision, the core platform service map, the obligation matrix, product and data-flow changes, interoperability or access requests, anti-circumvention review, and the Article 11 compliance report.

  • A marketplace can have DSA duties even if it is not a DMA .
  • A can have DMA duties for a even where the disputed issue is not a DSA content-moderation issue.
  • When the same service is both an online platform under the DSA and a under the DMA, keep the source, owner, evidence, and regulator route separate.
Section 2

Thresholds and designation are not interchangeable

The DSA's very large online platform and very large online search engine layer applies to online platforms and search engines with average monthly active recipients in the Union equal to or higher than 45 million, after Commission designation. Those services then face enhanced systemic-risk, audit, data-access, recommender, advertising, compliance-function, and reporting duties.

The DMA presumption uses a different test: significant internal-market impact, a that is an important gateway for business users to reach end users, and an entrenched and durable position. The quantitative presumption includes EUR 7.5 billion annual Union turnover in each of the last three financial years or EUR 75 billion average market capitalisation or equivalent fair market value in the last financial year, the same core platform service in at least three Member States, and in the last financial year at least 45 million monthly active EU end users and 10,000 yearly active EU business users. The user thresholds must have been met in each of the previous three financial years for the entrenched-and-durable-position presumption.

Thresholds create presumptions, not the final legal status. The Commission can designate an undertaking that meets the qualitative Article 3 criteria without meeting every quantitative threshold, and an undertaking meeting the thresholds may submit sufficiently substantiated arguments that call the presumption into question. The designation decision identifies the covered core platform services; the then has six months to comply with for those listed services.

  • Do not treat the shared 45 million user figure as the same legal test; the DSA uses average monthly active recipients for designation, while the DMA uses monthly active end users plus yearly active business users for core platform services.
  • Do not apply DMA because a service is large under the DSA or merely crosses the DMA thresholds; the duties follow a Commission designation and its list of core platform services.
  • Keep methodology notes for user counts, business-user counts, and service boundaries because both regimes let the Commission examine or request supporting information.
Section 3

Practical ownership split

DSA ownership should sit with teams that can change platform governance and user-facing safety systems: trust and safety for notices, moderation, complaints, trusted flaggers, and misuse; marketplace operations for trader traceability; ads and recommender teams for disclosures and user controls; legal and policy for terms, transparency reports, and regulator responses; and risk or compliance teams for assessments, mitigation, audits, and researcher data access.

DMA ownership should sit with teams that can change conduct: competition counsel for interpretation and Commission engagement; product and engineering for defaults, interoperability, , access, and ranking changes; data governance and privacy for data-combination, portability, and access obligations; developer relations and commercial teams for business-user terms; and compliance reporting for Article 11 evidence and annual updates.

  • Use one coordinator only for dependency management; assign separate accountable owners for DSA content-safety controls and DMA contestability controls.
  • Route launch reviews differently: DSA review asks whether a feature changes platform safety, ads, recommender, marketplace, or VLOP risk duties; DMA review asks whether a 's changes access, interoperability, data, , , , defaults, or business-user conditions.
  • Label shared artifacts by obligation. For example, a recommender-system change may support DSA transparency or systemic-risk mitigation, while a ranking or access change may support DMA non-discrimination or business-user fairness.
Section 4

Evidence that should not be merged

For DSA, keep evidence that explains the service tier and the user-safety workflow: terms-and-conditions controls, notice intake fields, moderation decision records, statement-of-reasons submissions, complaint and out-of-court dispute outcomes, trusted-flagger handling, misuse suspensions, ad and recommender disclosures, trader verification files, transparency-report data, average monthly active recipient (AMAR) calculations, systemic-risk assessments, mitigation decisions, independent audit materials, and researcher-access responses.

For DMA, keep evidence that explains the 's conduct for each listed : designation and review records, Article 5 to 7 obligation-by-obligation matrices, pre-change and post-change product descriptions, technical and engineering specifications, user-choice flows, data-use policies, interoperability reference offers and request logs, business-user access terms, compliance-function records, consumer-profiling audit descriptions, Article 11 compliance reports, non-confidential summaries, indicators, and redlines against earlier reports.

  • Shared logs are acceptable only when each log entry says whether it supports DSA, DMA, or both.
  • Do not cite a DMA compliance report as proof that DSA notice-and-action or transparency-database duties are met.
  • Do not cite a DSA transparency report as proof that a DMA has demonstrated effective compliance with .
Primary sources

References and citations

eur-lex.europa.eu10 citations
Referenced sections
  • Primary DMA legal text for gatekeeper designation, core platform services, Articles 5 to 7 obligations, compliance reports, and fines.
  • Primary DMA text for gatekeeper designation, core platform services, Articles 5 to 7 obligations, compliance reports, and penalties.
  • DMA Article 3 source for gatekeeper criteria, quantitative presumptions, notification, designation, and review.
Show 6 more
  • Primary DMA text for gatekeeper conduct and contestability obligations.
  • Defines core platform services and gatekeeper designation mechanics.
  • DMA Article 3 source for gatekeeper quantitative presumptions.
  • Primary source for DMA Articles 5 to 7 obligations, anti-circumvention, reporting, concentration notice, and profiling-audit duties.
  • Primary DMA text for Commission enforcement and 10% or 20% fine ceilings.
  • Primary DMA source for classifying gatekeeper and core platform service obligations.
"gatekeeper"
More quoted passages
"core platform services"
"at least 45 million monthly active end users"
"contestable and fair"
"core platform service"
"10 000 yearly active business users"
"Articles 5, 6 and 7"
"10 % of its total worldwide turnover"
eur-lex.europa.eu10 citations
Referenced sections
  • Primary DSA legal text for scope, tiered intermediary obligations, VLOP/VLOSE designation, enhanced duties, and Commission penalties.
  • Primary DSA text for intermediary-service scope, platform duties, VLOP/VLOSE obligations, and enforcement powers.
  • Supports DSA operational ownership across content moderation, complaint, advertising, recommender, marketplace, VLOP/VLOSE, and compliance-function duties.
Show 6 more
  • Primary DSA text for intermediary-service and platform-governance duties.
  • Defines and structures DSA intermediary service categories.
  • Primary source for DSA tiered duties and VLOP/VLOSE obligations.
  • Primary DSA text for Digital Services Coordinator and Commission enforcement powers, including the 6% fine ceiling for VLOPs/VLOSEs.
  • Supports DSA ownership across operational platform duties and VLOP/VLOSE compliance functions.
  • Primary DSA source for classifying platform-safety and intermediary-service obligations.
"intermediary services"
More quoted passages
"content moderation"
"illegal content"
"online platform"
"statement of reasons"
"6 % of its total worldwide annual turnover"
"compliance function"
"online platforms"
digital-markets-act.ec.europa.eu5 citations
Referenced sections
  • Commission template source for DMA compliance-report content, core platform service mapping, implemented measures, indicators, and annual updates.
  • Commission template source for DMA compliance-report evidence, responsible individuals, core platform service mapping, technical changes, indicators, and annual updates.
  • Commission template source for the minimum information expected in DMA Article 11 compliance reports.
Show 2 more
  • Commission template source for DMA Article 11 evidence and compliance-report structure.
  • Commission template source for DMA compliance-function and measure-description evidence.
"Compliance Report"
More quoted passages
"detailed and transparent manner"
"supporting data and internal documents"
"compliance function"
digital-strategy.ec.europa.eu3 citations
Referenced sections
  • Commission overview for the 45 million DSA VLOP/VLOSE threshold and enhanced obligations after designation.
  • Commission source for the DSA VLOP/VLOSE threshold and enhanced obligation layer.
  • Commission source for the DSA 45 million VLOP/VLOSE threshold.
"over 45 million users in the EU"
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission source for statement-of-reasons submission and DSA Transparency Database workflow context.
  • Commission source for DSA statement-of-reasons database context.
"statements of reasons"
Show all related guides (35)

DSA Enforcement and Penalties in the EU

How Digital Services Act enforcement works: Commission and Digital Services Coordinator roles, VLOP and VLOSE investigations, fines, periodic penalty payments, and evidence readiness.

DSA Marketplace Trader Traceability Guide

EU Digital Services Act guide for online marketplaces collecting, checking, displaying, storing, and evidencing trader traceability information.

DSA notice and action plus statements of reasons guide

A source-cited Digital Services Act guide for notice intake, moderation decisions, statements of reasons, DSA Transparency Database submission, complaints, appeals, trusted flaggers, and records.

DSA Notice and Action Workflow for Hosting Services and Online Platforms

A source-cited DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.

DSA researcher data access for VLOPs and VLOSEs

Article 40 DSA guide to vetted researcher access for VLOPs and VLOSEs under Regulation (EU) 2025/2050: requests, data catalogues, security, deadlines, and records.

DSA service tier classifier for platforms, marketplaces, VLOPs and VLOSEs

Classify a digital service under the EU Digital Services Act as intermediary, hosting, online platform, marketplace, VLOP or VLOSE, with EU recipient-count evidence and obligation outputs.

DSA statement of reasons log workflow for online platforms

Build a DSA statement of reasons log for moderation decisions, Transparency Database submission, complaint links, retention, and QA controls.

DSA transparency report template fields and cadence

A source-cited template outline for Digital Services Act transparency reports, covering applicable service tiers, reporting periods, CSV/XLSX format, retention, statement-of-reasons links, and required evidence tables.

DSA Transparency Reporting Obligations by Provider Tier

A source-cited guide to EU Digital Services Act transparency reports, active-recipient publication, statements-of-reasons submissions, VLOP/VLOSE reports, templates, cadence, and evidence.

DSA VLOP and VLOSE Risk Assessments and Mitigation Guide

A source-cited guide to Digital Services Act systemic risk assessments, mitigation measures, audits, transparency reports, data access, and governance evidence for VLOPs and VLOSEs.

DSA VLOP Audit Pack Workflow: Risk, Mitigation, Audit, and Transparency Records

Build a DSA VLOP or VLOSE audit pack covering Article 34 risk assessments, Article 35 mitigations, independent-audit evidence, transparency reports, data access, and compliance governance.

DSA vs GDPR: online-platform governance and personal-data obligations

Compare the EU Digital Services Act and EU GDPR by scope, ads, recommenders, minors, transparency, complaints, enforcement, and evidence.

DSA vs P2B Regulation: EU platform obligations compared

Compare the EU Digital Services Act with the Platform-to-Business Regulation for platform scope, business-user terms, content moderation, ranking transparency, complaints, enforcement, and evidence.

DSA vs Terrorist Content Online Regulation: notice-and-action vs removal orders

Compare DSA content-governance duties with the EU Terrorist Content Online Regulation removal-order workflow for scope, timing, evidence, authorities, and team ownership.

EU Digital Services Act checklist for platforms and hosting services

An official source DSA checklist for classifying service tiers, notice-and-action, statements of reasons, complaints, transparency reports, ads, recommenders, trader traceability, VLOP/VLOSE duties, and evidence records.

EU Digital Services Act Compliance Guide

DSA compliance guide for intermediary services, hosting providers, online platforms, marketplaces, and VLOP/VLOSE teams: obligations, controls, and evidence to keep.

EU Digital Services Act FAQ: DSA scope, platform duties, VLOPs, reports, and penalties

Concise EU Digital Services Act FAQ covering intermediary-service scope, active-recipient thresholds, illegal-content notices, statements of reasons, trader traceability, recommender transparency, systemic-risk duties, reporting, penalties, and complaints.

EU Digital Services Act penalties and fines: caps and enforcement roles

DSA penalty caps and enforcement roles: Member State fines, Commission fines for VLOPs and VLOSEs, 1% procedural fines, and 5% periodic penalty payments.

EU Digital Services Act requirements by service tier

Overview of DSA obligations for intermediary services, hosting providers, online platforms, marketplaces, VLOPs and VLOSEs, including notices, complaints, ads, transparency reports, audits, data access and enforcement.

EU Digital Services Act service types and scope

Classify DSA service scope across mere conduit, caching, hosting, online platforms, marketplaces, online search engines, and VLOP/VLOSE threshold duties.

EU DSA deadlines and compliance calendar: application dates, reporting cycles, and VLOP clocks

Calendar view of cited EU Digital Services Act dates: full application, user-number publication, VLOP/VLOSE designation clocks, statements of reasons, and transparency reporting cycles.

EU DSA Transparency Calendar: reports, statements of reasons and user counts

Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.

EU DSA vs UK Online Safety Act: scope, duties, regulator, and evidence

Compare the EU Digital Services Act and UK Online Safety Act for platform scope, risk assessments, child protection, transparency, regulators, enforcement, and owners.

DSA average monthly active recipients: what platforms must publish

An official source FAQ on average monthly active recipients under the EU Digital Services Act, including publication, EU recipient scope, the 45 million VLOP/VLOSE threshold, and evidence records.

DSA illegal content notices: what must be included?

An official source FAQ on EU Digital Services Act illegal-content notices: Article 16 notice elements, acknowledgement, decision notices, trusted flagger priority, statements of reasons, and records.

DSA Marketplace Trader Traceability FAQ

Answer to what EU Digital Services Act Article 30 requires online marketplaces to collect, verify, display, retain, and evidence for trader traceability.

DSA recommender transparency FAQ: Article 27 and VLOP options

What EU Digital Services Act recommender transparency requires: main parameters, user options, VLOP/VLOSE non-profiling choices, and evidence to keep.

DSA statement of reasons FAQ

When DSA statements of reasons are required, what they must contain, when online platforms submit them to the DSA Transparency Database, and what appeal records to keep.

DSA VLOP Risk Assessment FAQ: Article 34, Mitigation, Audits

What VLOPs and VLOSEs must assess under the EU Digital Services Act, when to reassess, how Article 35 mitigation and annual audit evidence fit together, and what records to keep.