Comparison GuideEU and UK

EU DSA vs UK Online Safety Act platform duties compared

Use this comparison to separate EU intermediary and platform duties from UK online safety duties for user-to-user and search services.

The practical split is scope first, then regulator, risk assessment, illegal and harmful content duties, child protection, transparency, enforcement, and the team that owns implementation.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
4

Structured answer sets in this page tree.

Primary sources
8

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

The EU Digital Services Act and the UK Online Safety Act both regulate online services, but they do not use the same scope test or compliance model. The DSA starts from EU-facing intermediary services and adds duties by service tier, with the most demanding risk, audit, data-access, advertising, and recommender obligations for very large online platforms and search engines. The UK Online Safety Act starts from regulated user-to-user services, search services, and related service categories, with Ofcom supervising duties to assess and reduce illegal-content and child-safety risks.

Side-by-side comparison

EU Digital Services Act vs UK Online Safety Act

Use these rows to decide which regime applies, what each one requires, and where evidence can be reused without merging different legal duties.

Review all sources
First framework
EU Digital Services Act

EU regime for intermediary services offered to recipients in the Union, with layered duties for hosting services, online platforms, marketplaces, VLOPs, and VLOSEs.

Second framework
UK Online Safety Act

UK regime for regulated user-to-user services, search services, and related online services, supervised by Ofcom with duties focused on illegal content, children, transparency, and service accountability.

Comparison row 1

Scope boundary

EU Digital Services Act

Covers intermediary services with a substantial connection to the EU, including mere conduit, caching, hosting, online platforms, online marketplaces, and online search engines. Duties increase by service tier and by VLOP/VLOSE designation.

UK Online Safety Act

Covers regulated user-to-user services and search services, with additional structures for services likely to be accessed by children, categorised services, and services involving regulated provider pornographic content.

Operational implication

Classify the EU intermediary role and the UK regulated-service type separately before deciding whether the same product surface is in scope under both regimes.

Comparison row 2

Covered actors

EU Digital Services Act

National Digital Services Coordinators supervise many DSA providers, while the European Commission directly supervises and enforces the VLOP and VLOSE obligations.

UK Online Safety Act

Ofcom is the independent UK online-safety regulator and sets codes, guidance, transparency expectations, information requests, enforcement notices, and penalties.

Operational implication

Prepare regulator-response playbooks by authority: DSC and Commission for DSA; Ofcom for UK Online Safety Act.

Comparison row 3

Trigger

EU Digital Services Act

VLOPs and VLOSEs must assess systemic risks in the EU from service design, functioning, algorithmic systems, and use of the service, including illegal content, fundamental rights, civic discourse, public security, public health, minors, gender-based violence, and wellbeing.

UK Online Safety Act

Regulated services must work through illegal-content risk, children's access, children's risk, and Ofcom code or guidance expectations where relevant to the service.

Operational implication

Do not collapse DSA systemic-risk work into the UK illegal-content or child-safety assessment; keep the assessment scope, source, reviewer, and mitigation evidence labelled.

Comparison row 4

Core obligations

EU Digital Services Act

The DSA uses illegal content, terms-and-conditions enforcement, notice-and-action mechanisms, statements of reasons, complaint handling, trusted flaggers, out-of-court disputes, and content-moderation transparency.

UK Online Safety Act

The UK Act is organised around illegal content duties, child-safety duties, content harmful to children, provider pornographic content, reporting and complaints, and Ofcom codes of practice.

Operational implication

Moderation tooling can share queues and logs, but each action needs the correct legal basis, user notice, appeal path, and reporting category.

Comparison row 5

Evidence record

EU Digital Services Act

Typical DSA evidence owners include legal, compliance, trust and safety, marketplace operations, moderation, advertising, recommender systems, transparency reporting, research-access, audit, and regulator-response teams.

UK Online Safety Act

Typical UK evidence owners include legal, regulatory compliance, trust and safety, child safety, search, moderation, recommender systems, age assurance, complaints, transparency reporting, engineering, and policy teams.

Operational implication

Use a shared owner matrix only if each row has a DSA or UK label, a cited source, an accountable delivery team, and the evidence artifact that proves the control is operating.

Comparison row 6

Child protection and evidence split

EU Digital Services Act

Online platforms accessible to minors must use appropriate and proportionate privacy, safety, and security measures, and must not present profiling-based ads to minors when aware with reasonable certainty that the recipient is a minor.

UK Online Safety Act

In-scope services likely to be accessed by children must address child-safety duties, including measures to prevent children accessing the most harmful content and protect them from harmful or age-inappropriate content.

Operational implication

Use this row to separate the evidence pack: DSA minor-protection measures on one side, UK child-safety evidence on the other, and only mark controls as shared when both sources support the same artifact.

Comparison row 7

Enforcement

EU Digital Services Act

The Commission can investigate VLOPs and VLOSEs, request information and data or algorithm access, impose interim measures, and impose fines for DSA breaches up to 6% of global annual turnover, with separate procedural penalties available.

UK Online Safety Act

Ofcom can investigate non-compliance, issue enforcement action, and impose fines up to GBP 18 million or 10% of qualifying worldwide revenue, whichever is greater, according to GOV.UK's Online Safety Act overview.

Operational implication

Escalation records should name the correct authority, response deadline, source request, and penalty framework instead of using a generic platform-regulator risk label.

Comparison row 8

Overlap and reuse

EU Digital Services Act

DSA evidence includes terms-and-conditions explanations, content-moderation transparency reports, statement-of-reasons submissions, advertising disclosures, recommender-system parameters, VLOP/VLOSE ad repositories, and risk or audit reporting where applicable.

UK Online Safety Act

UK evidence includes risk-assessment records, terms enforcement, user reporting and complaints processes, transparency reporting for relevant services, Ofcom information responses, and records showing code or alternative-measure compliance.

Operational implication

Maintain one transparency inventory, but tag every disclosure or report by DSA article, UK duty, Ofcom code, or both.

Comparison row 9

Practical decision rule

EU Digital Services Act

If the product surface is an EU intermediary service, map the DSA tier and obligations first; if it is a VLOP or VLOSE, add the systemic-risk, audit, data-access, and recommender obligations on top.

UK Online Safety Act

If the product surface is a UK regulated user-to-user service or search service, map the Ofcom duty set first; if children are likely to access it, add the child-safety and age-assurance pack.

Operational implication

Do not treat the scope rows as the decision itself. Use them to choose the legal track, then attach the control pack that matches that track and its regulator.

Practical decision rule

How should teams decide whether one control can cover both regimes?

  • First classify the service separately under the DSA and the UK Online Safety Act.
  • Then map the duty: DSA intermediary or platform duty, VLOP/VLOSE systemic-risk duty, UK illegal-content duty, UK child-safety duty, transparency duty, or regulator-response duty.
  • Reuse evidence only when the artifact answers both cited duties without hiding different regulators, content categories, user notices, or assessment triggers.
  • Escalate when a product change adds user-to-user functionality, search functionality, marketplace trading, recommender ranking, targeted advertising, child access, or VLOP/VLOSE-scale exposure.
Section 1

Start with the service classification, not a shared online-safety label

A service can fall under the DSA because it is a mere conduit, caching, hosting, online platform, marketplace, online search engine, VLOP, or VLOSE offered to recipients in the EU. That analysis is not the same as the UK test for regulated user-to-user services, search services, or services involving regulated provider pornographic content.

For comparison work, keep two service inventories: one that classifies the EU intermediary role and one that classifies the UK service type. Reuse product facts such as user-generated content, search functionality, age access, recommender systems, advertising, and moderation flows, but do not copy the legal conclusion from one regime into the other.

  • DSA scoping asks whether the service is an intermediary service and which DSA tier applies.
  • UK Online Safety Act scoping asks whether the service is a regulated user-to-user service, search service, or related regulated service category.
  • Marketplace, app-store, social, search, forum, hosting, and messaging features may need separate classification if they are operated as distinct service surfaces.
Section 2

Risk work is different on each side

Under the DSA, all covered services need tier-appropriate governance, but the formal systemic-risk assessment regime is concentrated on VLOPs and VLOSEs. Those providers assess risks such as illegal content, fundamental-rights impacts, civic discourse, public security, public health, protection of minors, gender-based violence, and physical or mental wellbeing, then apply mitigation measures.

Under the UK Online Safety Act, risk work is tied to illegal content, child access, children's risk, provider pornography, service categorisation, and Ofcom codes and guidance. A UK implementation pack should therefore include age-access analysis and child-safety risk assessment where children are likely to access the service, not only a generic platform risk register.

  • Keep DSA VLOP/VLOSE systemic-risk evidence separate from UK illegal-content and children's-risk assessments.
  • For recommender, moderation, age-assurance, and advertising changes, record which regime created the control requirement.
  • Do not present a single global online-safety risk assessment as satisfying both regimes unless each required source, owner, and output is mapped.
Section 3

Child protection overlaps, but the compliance evidence is not identical

The DSA requires online platforms accessible to minors to put in place appropriate and proportionate measures for privacy, safety, and security, and restricts profiling-based advertising to minors where the platform is aware with reasonable certainty that the recipient is a minor. For VLOPs and VLOSEs, minors also appear inside the systemic-risk and mitigation framework.

The UK Online Safety Act is more explicitly organised around child access and child-safety duties for regulated user-to-user and search services. Ofcom's child-safety codes and related guidance focus on governance, safer platform design, age understanding or age assurance, recommender and moderation measures, reporting, complaints, and tools for children and carers.

  • DSA evidence should show platform accessibility to minors, safety measures, advertising controls, recommender settings, and any VLOP/VLOSE risk treatment.
  • UK evidence should show children's access assessment, children's risk assessment, age-assurance approach, content reporting, complaints, and code-of-practice implementation choices.
  • A shared child-safety product control can serve both regimes only if the DSA article or Commission guidance and the UK Act, Ofcom code, or GOV.UK source are both cited.
Section 4

Implementation ownership should follow the duty, regulator, and product control

For the DSA, legal and compliance teams should classify the service, while trust and safety, marketplace operations, advertising, recommender-system, content-moderation, and data-access owners maintain the operational evidence. VLOP and VLOSE work also needs compliance-function, audit, research-access, and regulatory-response ownership.

For the UK Online Safety Act, Ofcom-facing accountability should sit with legal or regulatory compliance, but delivery depends on child-safety, trust and safety, search, recommender systems, moderation, age assurance, reporting and complaints, engineering, and policy teams. The same person should not be asked to certify both regimes without a source-linked split of duties.

  • Assign one owner for EU service-tier classification and one owner for UK regulated-service classification.
  • Name separate operational owners for notices, content moderation, complaints, transparency reporting, age assurance, advertising, recommender systems, and regulator requests.
  • Keep an evidence index that labels each artifact as DSA-only, UK-only, or reusable for both with cited support.
Recommended next step

Build one evidence index with two legal labels

Sorena can help turn this comparison into a service inventory, owner matrix, risk-assessment tracker, and evidence index that keeps DSA and UK Online Safety Act obligations distinct.

Primary sources

References and citations

gov.uk
Referenced sections
  • GOV.UK states the Online Safety Act fine cap as GBP 18 million or 10% of qualifying worldwide revenue, whichever is greater.
"10 percent"
legislation.gov.uk
Referenced sections
  • Primary source for the UK side of the decision rule: regulated-service categories, risk assessment areas, transparency duties, and Ofcom powers.
"regulated services"
Related guides

Explore more topics

DSA Ads and Recommender Systems: transparency duties, user choice, and evidence
A grounded DSA guide to ad labels, targeting restrictions, recommender parameter disclosure, non-profiling options for VLOPs and VLOSEs, ad repositories, and compliance evidence.
DSA Applicability Test: classify intermediary services, platforms, marketplaces, VLOPs and VLOSEs
A source-grounded EU Digital Services Act applicability test for classifying intermediary services, hosting services, online platforms, marketplaces, VLOPs and VLOSEs.
DSA Article 28 minors protection guide for online platforms
EU Digital Services Act guide to Article 28 minors protection: platform scope, child-safety measures, targeted ads limits, recommender controls, and grounded evidence.
DSA average monthly active recipients: what platforms must publish
A grounded 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 Complaint and Dispute Workflows for Online Platforms
Build DSA complaint, appeal, statement-of-reasons, and out-of-court dispute workflows for online platform moderation decisions.
DSA crisis response for VLOPs and VLOSEs
EU Digital Services Act crisis response guide for VLOPs and VLOSEs: Article 36 Commission decisions, Article 48 crisis protocols, mitigation, governance, requests for information, and records.
DSA Dark Patterns: interface design checks for online platforms
Article 25 DSA guidance for reviewing online platform interfaces for deceptive, manipulative, or choice-distorting design patterns.
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 illegal content notices: what must be included?
A grounded 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 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 grounded 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 grounded DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.
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 researcher data access for VLOPs and VLOSEs
Article 40 DSA guide to vetted researcher data access for VLOPs and VLOSEs: DSC requests, eligibility checks, amendment grounds, confidentiality, security, and evidence 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 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 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-grounded 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 grounded 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
Grounded 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 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.
DSA vs DMA Platform Rules
Compare the EU Digital Services Act and Digital Markets Act by scope, designation thresholds, obligations, enforcement, evidence, and practical team ownership.
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
A grounded 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 grounded 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: reporting, SoR database, AMAR updates
Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.